Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2020-10-01T18:17:29ZPulp
Planio Pulp - Issue #7641 (NEW): pulp_installer role READMEs should not tell users to set ansible_python...https://pulp.plan.io/issues/76412020-10-01T18:17:29Zmdepaulo@redhat.com
<p>Multiple roles' README.md files list under variables:</p>
<pre><code>ansible_python_interpreter`: **Required**. Path to the Python interpreter.
</code></pre>
<p>It definitely isn't required to be set, since the default behavior is auto_legacy in Ansible 2.8 through 2.11, and auto in 2.12 (planned.)</p>
<p>Furthermore, we probably shouldn't even list it. It is a common built-in Ansible variable that. There are many others, and there seems to be nothing special about it. Perhaps we should list it in case users are running Fedora 30.</p> Pulp - Story #7100 (NEW): As an admin I want to be able to ratelimit access to the api endpointshttps://pulp.plan.io/issues/71002020-07-07T14:09:57Zmdellweg
<p>In the most simple way, this can be added solely by adjusting the settings.
We should test this and document it with the installer.</p>
<p><a href="https://www.django-rest-framework.org/api-guide/throttling/" class="external">https://www.django-rest-framework.org/api-guide/throttling/</a></p> Pulp - Task #6942 (NEW): Update galaxy_ng docs for the pulp_installer install-from-rpm supporthttps://pulp.plan.io/issues/69422020-06-09T15:45:37Zmdepaulo@redhat.com
<p>Its docs should show the example variables for doing this.</p> Pulp - Issue #6696 (ASSIGNED): pulp_installer fails to run "Collect static content" task when pul...https://pulp.plan.io/issues/66962020-05-08T19:25:22Zironfroggy
<p>Either needs to be a documented incompatibility and issue an error, or needs to run the correct steps when galaxy_ng is installed and the UI must be part of the installation.</p>
<p>This is not a problem for most uses but will be an issue if we need to test unreleased changes in pulpcore for QA purposes.</p>
<p>Working:</p>
<pre><code class="yaml syntaxhl" data-language="yaml"><span class="pi">-</span> <span class="na">hosts</span><span class="pi">:</span> <span class="s">all</span>
<span class="na">vars</span><span class="pi">:</span>
<span class="na">pulp_settings</span><span class="pi">:</span>
<span class="na">secret_key</span><span class="pi">:</span> <span class="s">secret</span>
<span class="na">content_origin</span><span class="pi">:</span> <span class="s2">"</span><span class="s">http://{{</span><span class="nv"> </span><span class="s">ansible_fqdn</span><span class="nv"> </span><span class="s">}}"</span>
<span class="na">pulp_default_admin_password</span><span class="pi">:</span> <span class="s">password</span>
<span class="na">pulp_install_plugins</span><span class="pi">:</span>
<span class="na">pulp-ansible</span><span class="pi">:</span> <span class="pi">{}</span>
<span class="na">galaxy-ng</span><span class="pi">:</span> <span class="pi">{}</span>
<span class="na">pulp-container</span><span class="pi">:</span> <span class="pi">{}</span>
<span class="na">roles</span><span class="pi">:</span>
<span class="pi">-</span> <span class="s">pulp-database</span>
<span class="pi">-</span> <span class="s">pulp-workers</span>
<span class="pi">-</span> <span class="s">pulp-resource-manager</span>
<span class="pi">-</span> <span class="s">pulp-webserver</span>
<span class="pi">-</span> <span class="s">pulp-content</span>
<span class="na">environment</span><span class="pi">:</span>
<span class="na">DJANGO_SETTINGS_MODULE</span><span class="pi">:</span> <span class="s">pulpcore.app.settings</span>
</code></pre>
<p>Not Working:</p>
<pre><code class="yaml syntaxhl" data-language="yaml"><span class="pi">-</span> <span class="na">hosts</span><span class="pi">:</span> <span class="s">all</span>
<span class="na">vars</span><span class="pi">:</span>
<span class="na">pulp_settings</span><span class="pi">:</span>
<span class="na">secret_key</span><span class="pi">:</span> <span class="s">secret</span>
<span class="na">content_origin</span><span class="pi">:</span> <span class="s2">"</span><span class="s">http://{{</span><span class="nv"> </span><span class="s">ansible_fqdn</span><span class="nv"> </span><span class="s">}}"</span>
<span class="na">pulp_default_admin_password</span><span class="pi">:</span> <span class="s">password</span>
<span class="na">pulp_install_plugins</span><span class="pi">:</span>
<span class="na">pulp-ansible</span><span class="pi">:</span> <span class="pi">{}</span>
<span class="na">galaxy-ng</span><span class="pi">:</span> <span class="pi">{}</span>
<span class="na">pulp-container</span><span class="pi">:</span> <span class="pi">{}</span>
<span class="na">pulp_source_dir</span><span class="pi">:</span> <span class="s2">"</span><span class="s">git+https://github.com/pulp/pulpcore.git@3.3.0#egg=pulpcore"</span>
<span class="na">roles</span><span class="pi">:</span>
<span class="pi">-</span> <span class="s">pulp-database</span>
<span class="pi">-</span> <span class="s">pulp-workers</span>
<span class="pi">-</span> <span class="s">pulp-resource-manager</span>
<span class="pi">-</span> <span class="s">pulp-webserver</span>
<span class="pi">-</span> <span class="s">pulp-content</span>
<span class="na">environment</span><span class="pi">:</span>
<span class="na">DJANGO_SETTINGS_MODULE</span><span class="pi">:</span> <span class="s">pulpcore.app.settings</span>
</code></pre> Pulp - Issue #6658 (NEW): Pain points when trying Pulp3 for the first timehttps://pulp.plan.io/issues/66582020-05-05T16:28:58Zxenlo
<a name="Intro"></a>
<h3 >Intro<a href="#Intro" class="wiki-anchor">¶</a></h3>
<p>@dkliban asked me some feedback (pain points) about trying to put Pulp3 in place.</p>
<a name="Background-on-my-use-case"></a>
<h3 >Background on my use case<a href="#Background-on-my-use-case" class="wiki-anchor">¶</a></h3>
<p>In the company I work for, we use ansible in our automation process. And in our automated deployment we provision infrastructure with Debian, OpenSuse and SLES. So for now we manage a server that mirror repos for all those distro. This is a collection of different tools apt-mirror, createrepo, RMT, wget and rsync glued with shell scripts and published with half thousand(for now) of soft links.</p>
<p>So I was interested to put in place Pulp3 with deb, rpm and file plugin on a Debian 10 host, installed with Ansible playbook <code>pulp_installer</code>.</p>
<a name="Pain-Point-List"></a>
<h3 >Pain Point List<a href="#Pain-Point-List" class="wiki-anchor">¶</a></h3>
<p>I think that most of all my expectations was something more mature, closer to 'Production ready' tool.</p>
<ul>
<li>I expected some CLI as user interface, as I think that a big part of public for this tool is SysAdmin.
Even API is a great interface, it's not comfortable for SysAdmin to manager repos (even more true we it needs to discover how it works)</li>
<li>The lack of external doc, like "tuto: How I mirror Centos and Debian with Pulp"…</li>
<li>Some confusion if the doc/tool is for Pulp2 or Pulp3</li>
<li>Yet another issue tracker to rise issues
(I didn't try really hard but my attempt to auth with github failed…)</li>
<li>The doc to install doc tells you that the prefered method is with Ansible but don't explain you how. Just redirect you to a git repo where you have to found the corresponding doc, which is not easy to find and which is not in line with the latest version on the repo (already explaned that point)</li>
<li>The pulp_installer don't list the system prereq. That's sad because, at least on a fresh installed Debian 10, the playbook fails. I had to add some packages and force the ansible_python_interpreter get the work done.</li>
<li>On the project page you tells that Pulp can manage plainty of repo type, but in fact if you take a fresh version only few plugins are working. Is there at least a compatibility/status matrix explaining that?</li>
</ul>
<a name="Thanks"></a>
<h3 >Thanks<a href="#Thanks" class="wiki-anchor">¶</a></h3>
<p>Nevertheless, I wanted to close on a more positive point, the IRC channel is highly responsive, and people hanging out there are full of goodwill.
Thanks for that!</p> Pulp - Task #6625 (NEW): document the OSes the installer supportshttps://pulp.plan.io/issues/66252020-04-30T16:27:24Zfao89Pulp - Task #5889 (NEW): Add upgrade information to the docshttps://pulp.plan.io/issues/58892019-12-16T21:06:09Zbmbouterbmbouter@redhat.com
<p>The installer supports upgrading (see <a href="https://pulp.plan.io/issues/5884" class="external">https://pulp.plan.io/issues/5884</a> ) we just need to document it for the user.</p> Pulp - Task #4969 (NEW): Improve documentation on the nginx and apache deployment offered by the ...https://pulp.plan.io/issues/49692019-06-13T19:07:45Zbmbouterbmbouter@redhat.com
<p>These docs should be in the pulp docs, not the ansible installer docs. It should clarify with a diagram the reverse proxy deployment provided by:</p>
<p><a href="https://pulp.plan.io/issues/4966" class="external">https://pulp.plan.io/issues/4966</a><br>
<a href="https://pulp.plan.io/issues/4967" class="external">https://pulp.plan.io/issues/4967</a></p>