Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2020-10-28T13:33:40ZPulp
Planio Pulp - Story #7762 (CLOSED - WONTFIX): Need synchronous REST endpoint for (RPM) distribution updatehttps://pulp.plan.io/issues/77622020-10-28T13:33:40ZAnonymous
<p>In a typical RHUI setup with 400+ repos and similar number of pending repository sync tasks,
it would be of a great help to have ability to "publish" (ie. update their distribution with a publication
that is already available) those repos that already have the latest
metadata compiled without waiting for the sync task queue to drain. Alternatively, a way to "push"
newly created distribution update onto the start of the task queue. In my understanding, updating a
distribution looks like a lightweight task compared to sync or metadata generation tasks.</p> Pulp - Story #5662 (CLOSED - CURRENTRELEASE): Manage Pulp via Ansible moduleshttps://pulp.plan.io/issues/56622019-11-04T16:15:21ZAnonymous
<p>I've been testing ansible modules to manage Pulp.</p>
<p><a href="https://github.com/ansible/ansible/pull/64388" class="external">https://github.com/ansible/ansible/pull/64388</a></p>
<p>Please let me know what you think.</p> Nectar - Story #1915 (CLOSED - WONTFIX): expose connect_timeout and read_timeout via configurationhttps://pulp.plan.io/issues/19152016-05-12T15:48:00ZAnonymous
<p>My pulp installation was having issues completing synchronization of certain external repos due to timeouts. Following discussions on this thread[0], I found that I was able to resolve this timeout by increasing the values found in /usr/lib/python2.6/site-packages/nectar/config.py:22.</p>
<p>I'm hoping that these timeout values can be made available from a configuration file.</p>
<p>My patch diff (rpm python-nectar-1.5.1-1.el6.noarch):</p>
<pre><code class="c syntaxhl" data-language="c"><span class="mi">22</span><span class="n">c22</span>
<span class="o"><</span> <span class="n">connect_timeout</span><span class="o">=</span><span class="mi">9</span><span class="p">.</span><span class="mo">05</span><span class="p">,</span> <span class="n">read_timeout</span><span class="o">=</span><span class="mi">57</span><span class="p">,</span> <span class="n">working_dir</span><span class="o">=</span><span class="s">"/tmp"</span><span class="p">)</span><span class="o">:</span>
<span class="o">---</span>
<span class="o">></span> <span class="n">connect_timeout</span><span class="o">=</span><span class="mi">6</span><span class="p">.</span><span class="mo">05</span><span class="p">,</span> <span class="n">read_timeout</span><span class="o">=</span><span class="mi">27</span><span class="p">,</span> <span class="n">working_dir</span><span class="o">=</span><span class="s">"/tmp"</span><span class="p">)</span><span class="o">:</span>
</code></pre>
<p>[0] <a href="https://groups.google.com/forum/#!topic/foreman-users/J8xvzGHbz9w" class="external">https://groups.google.com/forum/#!topic/foreman-users/J8xvzGHbz9w</a></p> Pulp - Task #1804 (CLOSED - WONTFIX): Create monthly view for community statisticshttps://pulp.plan.io/issues/18042016-03-31T14:55:28ZAnonymous
<p>Collect data from IRC, website, and github. Compose into an ongoing monthly report.</p> Pulp - Task #1803 (CLOSED - CURRENTRELEASE): Plan replacement of mongodb with postgreshttps://pulp.plan.io/issues/18032016-03-31T14:53:39ZAnonymousPulp - Refactor #78 (CLOSED - WONTFIX): Convert pulp.server.db.connection to manage the database ...https://pulp.plan.io/issues/782014-12-18T16:12:43ZAnonymous
<p>This Task is designed to solve two problems. (1) To remove the use of globals and replace it with a class based design and (2) to consolidate the database getter methods onto the class managing the database singleton.</p>
<p>I generally avoid the use of globals because they casually share state and promote a non object oriented paradigm. Using a class to store any globals requires developers to be more explicit, and access functions can be getter methods instead of module level functions.</p>
<p>The specifics:<br>
1) Introduce a new class in pulp.server.db.connection and move the initialize method into it as a @classmethod. Refactor all calls to the old pulp.server.db.connection.initialize method to use the new class method. The @classmethod initialize should store the _CONNECTION and _DATABASE objects as class attributes.</p>
<p>2) Move the get_collection(), get_database(), and get_connection() methods to be @classmethods on the new class introduced in (1). Refactor the usages of these 3 functions to use them as classmethods.</p>
<p>3) Ensure that get_collection(), get_database(), and get_connection() raise a consistent Exception if initialize() has not already been called.</p>
<p>4) Update the associated tests</p> Pulp - Refactor #77 (CLOSED - WONTFIX): Reduce bind complexityhttps://pulp.plan.io/issues/772014-12-18T16:12:43ZAnonymous
<p>In early 2.x our bind model and flows was augmented to include tracking consumer (agent) confirmation. The proposal here is to do away with this tracking in both the bind model and the bind/unbind flows. If we still think this information is useful, we can discuss having the agent periodically report the bindings and store them separately like package profile.</p> Pulp - Task #76 (CLOSED - WONTFIX): Automatically run repoclosure for all arches/dists after buil...https://pulp.plan.io/issues/762014-12-18T16:12:43ZAnonymous
<p>This task is related to build stuff, not Pulp itself:)</p>
<p>RPM dependences are occasionally missed during a build, especially for platforms we do not commonly use like el5. This occurs about once every two or three weeks for Pulp repos; QE will find that an RPM is missing while doing an install.</p>
<p>One way to find such issues quickly is to run repoclosure on each repos before publishing. This is typically done as one command per repo; an example is at <a href="https://fedoraproject.org/wiki/QA:Testcase_Mediakit_Repoclosure" class="external">https://fedoraproject.org/wiki/QA:Testcase_Mediakit_Repoclosure</a>.</p>
<p>This step is typically done during the build/release process before QE handoff, but could also be done by QE. Ideally this could be run as part of the new build process.</p>
<p>This should be done in the nightly Jenkins build repos job. This should be done using Docker if possible because it needs to be run on each arch and dist.</p> Pulp - Task #75 (CLOSED - WONTFIX): As a user, I can trust that Pulp's versions are correct with ...https://pulp.plan.io/issues/752014-12-18T16:12:43ZAnonymous
<p>Err:509</p> Nectar - Story #67 (CLOSED - WONTFIX): As a developer, nectar's threaded downloader can process s...https://pulp.plan.io/issues/672014-12-18T16:12:42ZAnonymous
<p>We have a little bit of code duplication and redundancy in the _add_proxy function of threaded downloader. This was required as python-requests 2.0.0 had a bug which was not passing the proxy authentication information correctly. Now that we have moved to 2.2.1, it seems to have certain bugfixes, which might let us remove this extra code and rely on session.proxies for auth information completely. We do need to make sure that this handles situations with proxy with and without auth, with and without ssl etc. properly.</p> Nectar - Story #29 (CLOSED - WONTFIX): As a developer using nectar, I have documentation of the A...https://pulp.plan.io/issues/292014-12-18T16:12:37ZAnonymous
<p>Deliverables: nectar API documentation any additional documentation of what contract a developer must honor</p> Docker Support - Story #13 (CLOSED - WONTFIX): As a user I can install the pulp-docker-registry a...https://pulp.plan.io/issues/132014-12-18T16:12:35ZAnonymous
<p>As a user I can install the pulp-docker-registry app onto OpenShiftPerform whatever additional packaging must be done after this app is packaged as an RPM in order to make it available via OpenShift</p> Nectar - Story #11 (CLOSED - WONTFIX): Nectar: Add concept of download retries and timeouthttps://pulp.plan.io/issues/112014-12-18T16:12:35ZAnonymousDocker Support - Story #8 (CLOSED - WONTFIX): As a user, I can serve docker images with entitleme...https://pulp.plan.io/issues/82014-12-18T16:12:34ZAnonymous
<p>On 10/6/14, bkearney stated during a phone meeting that for satellite 6.1, doing entitlement enforcement via crane only is sufficient. We do not need to do enforcement when serving the image files via pulp.</p> Docker Support - Story #6 (CLOSED - WONTFIX): As pulp_docker, I recognize when an upload's file i...https://pulp.plan.io/issues/62014-12-18T16:12:34ZAnonymous
<p>Deliverables:When initiating an upload, and the file being uploaded has been uploaded before, pulp recognizes this and does not re-upload the file.</p>