Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2021-10-11T14:56:13ZPulp
Planio Pulp - Task #9499 (MODIFIED): As a developer, I have azurite on dev environmenthttps://pulp.plan.io/issues/94992021-10-11T14:56:13Zfao89Pulp - Story #8702 (NEW): As a user, the example-use playbook is not cluttered with object storag...https://pulp.plan.io/issues/87022021-05-05T13:31:24Zmdepaulo@redhat.com
<p>We should move the object storage checks from the the example-use playbook to the pulp_common role to solve this.</p>
<p>It will provide a better user experience. (Making the example playbook as small as possible.)</p>
<p>It will also enforce the checks for users that do not use the example-use playbook.</p>
<p><a href="https://github.com/pulp/pulp_installer/blob/master/playbooks/example-use/playbook.yml" class="external">https://github.com/pulp/pulp_installer/blob/master/playbooks/example-use/playbook.yml</a></p>
<p><a href="https://github.com/pulp/pulp_installer/blob/master/roles/pulp_common/tasks/main.yml#L16" class="external">https://github.com/pulp/pulp_installer/blob/master/roles/pulp_common/tasks/main.yml#L16</a></p> Pulp - Story #8701 (NEW): As a pulp_installer user, I can use the full logic to add repos to the ...https://pulp.plan.io/issues/87012021-05-05T12:59:40Zmdepaulo@redhat.com
<p>As mentioned in <a class="issue tracker-1 status-11 priority-6 priority-default closed" title="Issue: pulp_installer fails to install redis due to no EPEL7 (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/7773">#7773</a> , we should refactor our logic to add repos to the system (in a robust & configurable manner) into another role like <code>pulp_repos</code>.</p>
<p>I propose the following design:</p>
<ol>
<li>This is a dependency role. pulp_common, pulp_redis, pulp_database, will all depend on it.</li>
<li>When a role like pulp_common depends on it, it passes variables like <code>__pulp_repos_epel: true</code> to denote which repos the role needs. It passes variables via roles/pulp_common/meta/main.yml : <code>dependencies:</code>
</li>
<li>If a user wants to disable the logic to add the repo (if they added it manually), they'll pass a variable like <code>pulp_repos_epel: false</code> to disable it.</li>
<li>Existing variables for configuring how we add the repos to the system, like <code>epel_release_packages</code>, should still used.</li>
</ol>
<p>This logic is found in:</p>
<ul>
<li>roles/pulp_common/tasks/ambiguously-named-repo.yml</li>
<li>roles/pulp_common/tasks/repos.yml</li>
</ul> Pulp - Task #7642 (NEW): Update pulp_installer's list of supported Fedora releaseshttps://pulp.plan.io/issues/76422020-10-01T18:18:58Zmdepaulo@redhat.com
<p>Fedora 32 is supported; pulplift CI tests it. Fedora 30 will probably be dropped in the task that blocks this.</p>
<p>Note that this list is in roles/*/meta/main.yml</p> Pulp - Task #7638 (NEW): Fix ansible_python_interpreter issues in pulp_installerhttps://pulp.plan.io/issues/76382020-10-01T18:03:57Zmdepaulo@redhat.com
<p>There are 3 minor / potential issues pertaining to this.</p> Pulp - Task #6798 (NEW): Document the new guidelines for plugin installation logichttps://pulp.plan.io/issues/67982020-05-21T18:47:54Zmdepaulo@redhat.com
<p>There are 3 places they could be:</p>
<ol>
<li>A role in a separate git repo and on galaxy.</li>
<li>A separate role in the pulp_installer repo (pulp_rpm will be this.)</li>
<li>Conditional logic within the pulp_installer's other roles.</li>
</ol> Pulp - Story #6797 (ASSIGNED): [epic] As a user, I can consume all the plugin prereq roles in the...https://pulp.plan.io/issues/67972020-05-21T18:45:22Zmdepaulo@redhat.com
<p>pulp_rpm_prerequisites exists because the installer has had a plugin neutral policy.</p>
<p>This policy was for very long misunderstood: It's not about avoiding favoritism to any plugins, it's about not tying the installer (which is tied to pulpcore releases) to plugin releases. So that say pulpcore 3.3 logic would be in pulp_installer 3.3 release, and so that pulp_cardboardbox 0.7 logic would be in the pulp_cardboardbox_prerequisites 0.7 role.</p>
<p>The team now agrees that this policy is counter-productive because:</p>
<ol>
<li>Having a role in a separate repo (not part of the pulp_installer collection) is extra work for developers, and for users.</li>
<li>The only plugin that currently needs a prereq role, pulp_rpm, has version numbers and releases that correspond to pulpcore releases. pulp_rpm 3.3.z needs pulpcore 3.3.z, etc. So the pulp_rpm specific installation logic can be safely bundled in pulp_installer 99% of the time.</li>
</ol> OSTree Support - Task #4642 (MODIFIED): Delete the 'master' branch and make 2-master to main branchhttps://pulp.plan.io/issues/46422019-04-05T13:40:27Zbmbouterbmbouter@redhat.com
<a name="Problem"></a>
<h2 >Problem<a href="#Problem" class="wiki-anchor">¶</a></h2>
<p>The OStree repository is confusing users because the master branch shows 'this is the Pulp3 plugin for OSTree....". This is really just a stub and the plugin is in no way functional.</p>
<a name="Solution"></a>
<h2 >Solution<a href="#Solution" class="wiki-anchor">¶</a></h2>
<p>Delete the 'master' branch and make the default branch '2-master'. This is similar to what was done to the pulp/pulp repository which is also a Pulp2 only repository.</p> Puppet Support - Task #4641 (MODIFIED): Delete the 'master' branch and make 2-master to main branchhttps://pulp.plan.io/issues/46412019-04-05T13:40:24Zbmbouterbmbouter@redhat.com
<a name="Problem"></a>
<h2 >Problem<a href="#Problem" class="wiki-anchor">¶</a></h2>
<p>The Puppet repository is confusing users because the master branch shows 'this is the Pulp3 plugin for Puppet....". This is really just a stub and the plugin is in no way functional.</p>
<a name="Solution"></a>
<h2 >Solution<a href="#Solution" class="wiki-anchor">¶</a></h2>
<p>Delete the 'master' branch and make the default branch '2-master'. This is similar to what was done to the pulp/pulp repository which is also a Pulp2 only repository.</p> Python Support - Story #4396 (MODIFIED): Add one-shot upload supporthttps://pulp.plan.io/issues/43962019-02-07T16:42:44Zdalleydalley@redhat.com
<p>The model viewset is not really intended to be used the way we're using it. Instead of allowing a "create" action on /content/python/python/, we should instead create a separate API endpoint for uploading new content, and get rid of what we currently have.</p>
<p>Example:<br>
<a href="https://github.com/pulp/pulp_rpm/pull/1246" class="external">https://github.com/pulp/pulp_rpm/pull/1246</a></p> Python Support - Story #3626 (MODIFIED): Python Viewset Filtershttps://pulp.plan.io/issues/36262018-04-29T18:10:09Zdalleydalley@redhat.com
<p>PythonPackageContent<br>
------------------------------------</p>
<ul>
<li>Inherit from the base Content (currently just "type" which isn't very helpful)</li>
<li>name (exact, in)</li>
<li>author (exact, in)</li>
<li>packagetype (exact, in)</li>
<li>filename (exact, in)</li>
</ul>
<p>PythonRemote<br>
----------------------</p>
<ul>
<li>Inherit from the base Remote - currently (name, last_updated)</li>
<li>Projects (exact, in) - see which remotes are set to download certain projects</li>
</ul>
<p>PythonPublisher<br>
-------------------------</p>
<ul>
<li>No extra filters, just the ones on base Publisher - currently (name, last_updated)</li>
</ul> Packaging - Task #3533 (MODIFIED): Prepare for pypi pulp3 beta releasehttps://pulp.plan.io/issues/35332018-03-28T17:43:28Zbizhangbizhang@redhat.com
<p>There's some pypi packaging related work necessary for the pulp3 beta release. There's bits and pieces of this work filed under multiple redmine issues, but they all should be done before beta. This is the master issue to do those and some other necessary updates in order to release the beta.</p>
<a name="Dependecies"></a>
<h2 >Dependecies<a href="#Dependecies" class="wiki-anchor">¶</a></h2>
<ul>
<li>We should switch our psycopg2 dependency to psycopg2-binary. There is a task for that filed here: <a href="https://pulp.plan.io/issues/3375" class="external">https://pulp.plan.io/issues/3375</a>
</li>
</ul>
<ul>
<li>Django should be >=1.11<br>
There is also an issue filed that we should revisit before pulp3 rc is released. <a href="https://pulp.plan.io/issues/2896" class="external">https://pulp.plan.io/issues/2896</a>
</li>
</ul>
<ul>
<li>celery should be >=4</li>
</ul>
<a name="Versions"></a>
<h2 >Versions<a href="#Versions" class="wiki-anchor">¶</a></h2>
<p>versions for pulpcore[0] and pulpcore-common [1] and pulp_python should be set to 3.0.0b1<br>
versions for pulpcore-plugin [2] , pulp_file, and should be set to 0.0.0b1</p>
<p>[0] <a href="https://github.com/pulp/pulp/blob/3.0-dev/pulpcore/setup.py" class="external">https://github.com/pulp/pulp/blob/3.0-dev/pulpcore/setup.py</a><br>
[1] <a href="https://github.com/pulp/pulp/blob/3.0-dev/common/setup.py" class="external">https://github.com/pulp/pulp/blob/3.0-dev/common/setup.py</a><br>
[2] <a href="https://github.com/pulp/pulp/blob/3.0-dev/plugin/setup.py" class="external">https://github.com/pulp/pulp/blob/3.0-dev/plugin/setup.py</a><br>
[3] <a href="https://setuptools.readthedocs.io/en/latest/setuptools.html#declaring-extras-optional-features-with-their-own-dependencies" class="external">https://setuptools.readthedocs.io/en/latest/setuptools.html#declaring-extras-optional-features-with-their-own-dependencies</a></p> Python Support - Task #2936 (MODIFIED): Add pep8speakshttps://pulp.plan.io/issues/29362017-07-24T13:42:09ZdaviddavisPython Support - Task #2883 (MODIFIED): Create model(s) for Python's Releaseshttps://pulp.plan.io/issues/28832017-07-10T21:44:08Zamacdona@redhat.comaustin@redhat.com
<p>A content model, content serializer and content viewset have been already created by <a href="https://pulp.plan.io/issues/2882" class="external">https://pulp.plan.io/issues/2882</a></p>
<p>This task is to finish those classes, adding any Python specific fields.</p>
<p>This task will be complete when a django shell user can CRUD full representations of Python Package "releases". A REST API user should be able to read a list of all Python units `/v3/content/python/` as well as retrieve data on a specific unit (url is not yet decided).</p>
<p>All unit metadata is provided by the shell user at this point. It is not expected that the plugin extract the metadata from a package or scrape it from upstream.</p>
<p>After discussion we will go with the Python "distribution package" as content unit model.</p>
<p>The PythonPackageContent (because it's not really a PythonContent, and DistributionContent would overload the term 'distribution' too much) would contain the following fields:</p>
<a name="Pulp-related"></a>
<h4 >Pulp-related<a href="#Pulp-related" class="wiki-anchor">¶</a></h4>
<table>
<thead>
<tr>
<th></th>
</tr>
</thead>
<tbody>
<tr>
<td>packagetype</td>
</tr>
<tr>
<td>path</td>
</tr>
<tr>
<td>filename (primary key)</td>
</tr>
</tbody>
</table>
<a name="Python-related"></a>
<h4 >Python-related<a href="#Python-related" class="wiki-anchor">¶</a></h4>
<table>
<thead>
<tr>
<th></th>
</tr>
</thead>
<tbody>
<tr>
<td>name</td>
</tr>
<tr>
<td>version</td>
</tr>
<tr>
<td>metadata_version</td>
</tr>
<tr>
<td>summary</td>
</tr>
<tr>
<td>description</td>
</tr>
<tr>
<td>keywords</td>
</tr>
<tr>
<td>home_page</td>
</tr>
<tr>
<td>download_url</td>
</tr>
<tr>
<td>author</td>
</tr>
<tr>
<td>author_email</td>
</tr>
<tr>
<td>maintainer</td>
</tr>
<tr>
<td>maintainer_email</td>
</tr>
<tr>
<td>license</td>
</tr>
<tr>
<td>classifier</td>
</tr>
<tr>
<td>requires_python</td>
</tr>
<tr>
<td>project_url</td>
</tr>
<tr>
<td>platform</td>
</tr>
<tr>
<td>supported_platform</td>
</tr>
<tr>
<td>requires_dist</td>
</tr>
<tr>
<td>provides_dist</td>
</tr>
<tr>
<td>obsoletes_dist</td>
</tr>
<tr>
<td>requires_external</td>
</tr>
</tbody>
</table>
<p>This is they way Pulp2 is modeled currently. Each content unit would contain one artifact corresponding to the filename distribution package on PyPI.</p>
<a name="Disadvantages"></a>
<h3 >Disadvantages<a href="#Disadvantages" class="wiki-anchor">¶</a></h3>
<p>The disadvantage of modeling a Python distribution package as a content unit is that this is something the user would not care as much about. We would have multiple content units for the same release, but for different systems:<br>
eg.<br>
scipy-0.9.0-cp26-cp26mu-manylinux1_x86_64.whl<br>
scipy-0.9.0-cp27-cp27m-manylinux1_x86_64.whl<br>
scipy-0.9.0-cp27-cp27mu-manylinux1_x86_64.whl<br>
scipy-0.9.0.tar.gz<br>
scipy-0.9.0.zip</p>
<p>As a user I do not want to view all these distribution packages when I query a repository. The only thing I would care about is the release, and I will let pip take care of which distribution package to install. PyPI in particular makes the release a first class citizen instead of the distribution packages.</p>
<p>Metadata that belongs to a release (i.e. additional metadata) would be repeated across content units. PyPI stores these metadata fields as a part of the release [0], and these fields could be updated in PyPI outside of a release. The metadata we store would be the metadata in a distribution package, which is immutable, so if a user updates metadata in PyPI, we would not sync the metadata updates.</p>
<a name="Glossary"></a>
<h3 >Glossary<a href="#Glossary" class="wiki-anchor">¶</a></h3>
<p><span><strong>Release</strong></span><br>
A snapshot of a Project at a particular point in time, denoted by a version identifier.<br>
Making a release may entail the publishing of multiple "distribution packages". For example, if version 1.0 of a project was released, it could be available in both a source distribution format and a Windows installer distribution format.</p>
<p><span><strong>Distribution Package</strong></span><br>
A versioned archive file that contains Python packages, modules, and other resource files that are used to distribute a Release. The archive file is what an end-user will download from the internet and install. A project may contain many releases, and releases may contain many distribution packages. Can be type sdist, bdist, etc. "Distribution package" is used instead of "package" to avoid confusion with "import packages" or linux "distributions".</p>
<p>[0] <a href="https://warehouse.pypa.io/api-reference/xml-rpc/" class="external">https://warehouse.pypa.io/api-reference/xml-rpc/</a></p> Python Support - Task #2882 (MODIFIED): bootstrap pulp_python for Pulp 3https://pulp.plan.io/issues/28822017-07-10T21:37:16Zamacdona@redhat.comaustin@redhat.com
<p>This task is to create the basic plugin structure for the python plugin. This task is complete when:</p>
<p>1. The plugin is discoverable by Pulp<br>
2. CRUD for ContentUnits, Importers, Publishers (vanilla, without python specific fields)<br>
3. sync/publish remain NotImplemented</p>