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 #3624 (MODIFIED): As a user, I can as for only a reduced set of fields for...https://pulp.plan.io/issues/36242018-04-27T21:10:24Zdalleydalley@redhat.com
<p>When retreiving a list of PythonPackageContent from /content/python/packages/, the user should not be subjected to the full details of every content unit.</p>
<p>Which fields should we show? I propose</p>
<ul>
<li>filename</li>
<li>name</li>
<li>packagetype</li>
<li>version</li>
</ul>
<p>In addition to the fields</p>
<ul>
<li>_href</li>
<li>created</li>
<li>notes</li>
<li>artifacts</li>
</ul>
<p>Which get pulled in by the base Content serializer which we inherit from.</p>
<p>This looks like the following</p>
<pre><code>{
"_href": "http://localhost:8000/pulp/api/v3/content/python/packages/0d2f11f5-a8f6-44c9-9053-d1f3047adf3c/",
"artifacts": {
"shelf-reader-0.1.tar.gz": "http://localhost:8000/pulp/api/v3/artifacts/e6d61484-0d16-4296-9f80-5f6559dcbc2f/"
},
"created": "2018-04-27T21:27:06.925524Z",
"filename": "shelf-reader-0.1.tar.gz",
"name": "shelf-reader",
"notes": {},
"packagetype": "sdist",
"type": "python",
"version": "0.1"
}
</code></pre> Python Support - Task #2936 (MODIFIED): Add pep8speakshttps://pulp.plan.io/issues/29362017-07-24T13:42:09ZdaviddavisPython Support - Story #2885 (MODIFIED): As a User I can Publish Python packages in a way that is...https://pulp.plan.io/issues/28852017-07-10T21:50:50Zamacdona@redhat.comaustin@redhat.com
<p>This story is to extend the Publisher model and serializer with all Python specific fields and to implement publish.</p>
<p>Publisher.publish() should only be concerned with implementing the the simple API (which is consumed by pip). When this story is complete, the user will be able to create a Publisher, use it to publish a Repository with PythonPackageContent in it, creating a Publication. The user will be able to associate that Publication to a Distribution, and then pip will be able to install packages from the distribution.base_path.</p>
<p><a href="https://wiki.python.org/moin/PyPISimple" class="external">https://wiki.python.org/moin/PyPISimple</a><br>
<a href="https://www.python.org/dev/peps/pep-0301/" class="external">https://www.python.org/dev/peps/pep-0301/</a></p>
<p>For every unique project in a repository pulp should distribute a HTML page located at: { distribution.base_path.}/simple/{project-name}/</p>
<p>This HTML page should contain every distribution package that shares the same project name and should look like:</p>
<pre><code><!DOCTYPE html>
<html>
<head>
<title>Links for pulpcore</title>
</head>
<body><h1>Links for pulpcore</h1>
<a href="{link-to-content}#md5={md5_hash}" rel="internal">{PythonPackageContentUnit.filename}</a><br/>
<a href="../../packages/02/ee/3ceee60a9694b9462c62eee3df0d2b3e525be82750bc3f9e8b4d21a0cfb7/pulpcore-3.0.0a1.dev5-py3-none-any.whl#md5=16f188762c54527815557af8a7067234" rel="internal">pulpcore-3.0.0a1.dev5-py3-none-any.whl</a><br/>
<a href="../../packages/03/6c/e48eb03fa930a36838b3ff92e4367d901bb09e725859e0030b3bb40dff77/pulpcore-3.0.0a1.dev4-py3-none-any.whl#md5=3c8c966327231e8a3f48b70866f3c56a" rel="internal">pulpcore-3.0.0a1.dev4-py3-none-any.whl</a><br/>
</body></html>
</code></pre>
<p>The json API (which would be consumed by other Pulps) is <strong>not</strong> a part of this story, and will be implemented in <a href="https://pulp.plan.io/issues/2886" class="external">https://pulp.plan.io/issues/2886</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> Python Support - Story #1884 (MODIFIED): As a user, I can lazily sync python packageshttps://pulp.plan.io/issues/18842016-04-29T21:55:04Zamacdona@redhat.comaustin@redhat.com
<p>With the previous work done in for python packages, it is now possible to create objects using only the metadata provided by the json API of PyPI. This metadata is also now provided by pulp publish.</p>
<p>Completion of this story should allow the user to set the download policy to on_demand and background.</p>