https://pulp.plan.io/https://pulp.plan.io/favicon.ico2016-10-05T17:25:06ZPulpPulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=149122016-10-05T17:25:06Zsemyerssean.myers@redhat.com
<ul></ul><p>I added some checklist items. One, "Come up with an upgrade policy" is a little ambiguous, but I'm not sure how to phrase it more accurately. It refers to the upgrade policy of the Pulp installation being used to distribute Pulp, and whether we want to always keep it up to date with the latest release, or only update it as-needed. It <em>doesn't</em> refer to how we update the versions of pulp being distributed, that's a separate checklist item.</p> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=157352016-11-11T19:40:40Zdkliban@redhat.com
<ul><li><strong>Blocks</strong> <i><a class="issue tracker-1 status-8 priority-6 priority-default closed" href="/issues/2414">Issue #2414</a>: `ImproperlyConfigured` exception in for detail list view endpoint</i> added</li></ul> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=157372016-11-11T19:40:55Zdkliban@redhat.com
<ul><li><strong>Blocks</strong> deleted (<i><a class="issue tracker-1 status-8 priority-6 priority-default closed" href="/issues/2414">Issue #2414</a>: `ImproperlyConfigured` exception in for detail list view endpoint</i>)</li></ul> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=157392016-11-11T19:41:48Zdkliban@redhat.com
<ul><li><strong>Blocks</strong> <i><a class="issue tracker-2 status-9 priority-6 priority-default closed" href="/issues/2145">Task #2145</a>: Ansible playbooks need to pull from Pulp</i> added</li></ul> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=218462017-09-11T15:39:22Zbmbouterbmbouter@redhat.com
<ul></ul><p>I think OS1 has been shutdown or nearly shutdown at this point. Open Source and Standards (OSAS) has offered some hosting for upstream Pulp's needs, like maybe hosting this environment. I'm emailing them to get some more details about hosting a Pulp inside the OSAS infrastructure.</p> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=219742017-09-21T14:59:51Zmhrivnakmhrivnak@redhat.com
<ul><li><strong>Sprint/Milestone</strong> set to <i>45</i></li></ul><p>This is in-progress and will get groomed ASAP.</p> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=219812017-09-21T19:51:52Zbmbouterbmbouter@redhat.com
<ul></ul><p>We will use an OSAS environment that they provide an EL7 box that we can manage and deploy Pulp onto it. I believe <a class="user active" href="https://pulp.plan.io/users/46">pcreech</a> or <a class="user active" href="https://pulp.plan.io/users/383">bizhang</a> have access to that.</p> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=219882017-09-22T14:46:40Zbizhangbizhang@redhat.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/21988/diff?detail_id=22502">diff</a>)</li></ul> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=219962017-09-22T15:12:28Zbmbouterbmbouter@redhat.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/21996/diff?detail_id=22510">diff</a>)</li></ul><p>I added that the broker should be configured to only listen locally.</p>
<p>I don't understand the middle bullet point.</p>
<p>Also will this be the url that users consumer directly from or are we distributing the bits elsewhere somehow?</p> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=219982017-09-22T15:50:58Zbizhangbizhang@redhat.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/21998/diff?detail_id=22513">diff</a>)</li></ul><p><a class="user active" href="https://pulp.plan.io/users/1">bmbouter</a>, since this is public facing people should be using it to consume our bits. I don't think we'll be distributing out the pulp3 bits to fedorapeople, but can be convinced otherwise.</p>
<p>As far as SNI goes <a class="user active" href="https://pulp.plan.io/users/46">pcreech</a> mentioned hosting multiple https sites from the same IP, but I think that can (and should) be taken off, since this story only deals with getting pulp up and running.</p> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=220312017-09-25T13:19:10Zmhrivnakmhrivnak@redhat.com
<ul></ul><p>Can I assume that "Pulp should be ran on a non default port" is referring to the REST API service?</p>
<p>What is the goal of running it on a non-default port?</p> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=221022017-09-27T14:08:13Zpcreechpcreech@redhat.com
<ul></ul><p>The intent behind moving the REST api to a different port is that doing such would allow us to have more access control at the firewall level. This machine has a public IP, and therefore anything we set to listen will listen on the public IP. Having our web service listen at the same ip:port endpoint as our content will allow anyone coming in to attempt to access our rest api as well.</p>
<p>Moving to a separate port will allow us to implement stricter access controls on the rest api that we interface with, therefore helping reduce our attack surface.</p>
<p>The other option would be to have the rest api listen to local only, therefore necessitating that all interaction with pulp happens solely on that machine.</p> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=222872017-10-06T15:54:54Zbmbouterbmbouter@redhat.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/22287/diff?detail_id=22759">diff</a>)</li></ul><p>I clarified in the description about the ports saying that the rest API will be on one non-standard port and that content will be served via 80 and 443. Is that right?</p> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=224312017-10-18T15:28:20Zjortel@redhat.comjortel@redhat.com
<ul><li><strong>Sprint/Milestone</strong> changed from <i>45</i> to <i>46</i></li></ul> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=224482017-10-18T15:35:11Zbizhangbizhang@redhat.com
<ul></ul><p><a class="user active" href="https://pulp.plan.io/users/1">bmbouter</a> that sounds correct to me.</p> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=224492017-10-18T15:37:32Zbmbouterbmbouter@redhat.com
<ul><li><strong>Groomed</strong> changed from <i>No</i> to <i>Yes</i></li></ul><p>Thanks <a class="user active" href="https://pulp.plan.io/users/383">bizhang</a>!</p> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=227452017-11-06T13:10:55Zmhrivnakmhrivnak@redhat.com
<ul><li><strong>Sprint/Milestone</strong> changed from <i>46</i> to <i>47</i></li></ul> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=227942017-11-07T19:40:28Zbizhangbizhang@redhat.com
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>ASSIGNED</i></li><li><strong>Assignee</strong> set to <i>bizhang</i></li></ul> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=230902017-11-30T20:59:04Zrchan
<ul><li><strong>Sprint/Milestone</strong> changed from <i>47</i> to <i>48</i></li></ul> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=235042017-12-19T16:17:59Zrchan
<ul><li><strong>Sprint/Milestone</strong> changed from <i>48</i> to <i>52</i></li></ul> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=237492018-01-08T21:27:06Zrchan
<ul><li><strong>Sprint/Milestone</strong> changed from <i>52</i> to <i>53</i></li></ul> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=242972018-01-30T14:16:06Zjortel@redhat.comjortel@redhat.com
<ul><li><strong>Sprint/Milestone</strong> changed from <i>53</i> to <i>54</i></li></ul> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=246872018-02-22T16:22:35Zrchan
<ul><li><strong>Sprint/Milestone</strong> changed from <i>54</i> to <i>56</i></li></ul> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=265102018-03-08T23:35:47Zbmbouterbmbouter@redhat.com
<ul><li><strong>Sprint</strong> set to <i>Sprint 33</i></li></ul> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=265312018-03-08T23:36:16Zbmbouterbmbouter@redhat.com
<ul><li><strong>Sprint/Milestone</strong> deleted (<del><i>56</i></del>)</li></ul> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=266272018-03-12T13:37:44Zjortel@redhat.comjortel@redhat.com
<ul><li><strong>Sprint</strong> changed from <i>Sprint 33</i> to <i>Sprint 34</i></li></ul> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=267932018-03-15T16:04:41Zbmbouterbmbouter@redhat.com
<ul><li><strong>Sprint</strong> deleted (<del><i>Sprint 34</i></del>)</li></ul><p>Removing from sprint through email list discussion: <a href="https://www.redhat.com/archives/pulp-dev/2018-March/msg00080.html" class="external">https://www.redhat.com/archives/pulp-dev/2018-March/msg00080.html</a></p> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=302672018-08-24T13:22:52Zbizhangbizhang@redhat.com
<ul><li><strong>Assignee</strong> deleted (<del><i>bizhang</i></del>)</li></ul> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=322402018-11-28T20:06:28Zamacdona@redhat.comaustin@redhat.com
<ul><li><strong>Status</strong> changed from <i>ASSIGNED</i> to <i>NEW</i></li></ul> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=323232018-11-29T12:41:48Zbmbouterbmbouter@redhat.com
<ul></ul><p>I think we're moving away from self-distribution and towards container distribution in registries we don't operate and also PyPI delivery. Does doing this effort still make sense?</p>
<p>Note that the infra wiki shows this initative also: <a href="https://pulp.plan.io/projects/pulp/wiki/Infrastructure_&_Hosting#Distribute-Pulp-with-Pulp" class="external">https://pulp.plan.io/projects/pulp/wiki/Infrastructure_&_Hosting#Distribute-Pulp-with-Pulp</a></p>
<p>Also AIUI the OSCI group has provisioned a machine in the community data center for this purpose. Since we're not using it, and if we decide to not go forward with it, we should ask them to deprovisioning it.</p>
<p>What do you all think?</p> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=327562018-12-12T21:25:08Zbmbouterbmbouter@redhat.com
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>CLOSED - WONTFIX</i></li></ul><p>In pulp-dev mailing list discusison <a href="https://www.redhat.com/archives/pulp-dev/2018-November/msg00056.html" class="external">on this thread</a> we are going to use PyPI and existing container registries to distribute Pulp. OSCI has deprovisioned this machine, and I removed its entry from the infra wiki.</p> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=417382019-04-25T16:47:07Zdaviddavis
<ul><li><strong>Sprint/Milestone</strong> set to <i>3.0.0</i></li></ul> Pulp - Task #2325: Distribute Pulp with Pulphttps://pulp.plan.io/issues/2325?journal_id=430442019-04-26T20:39:26Zbmbouterbmbouter@redhat.com
<ul><li><strong>Tags</strong> deleted (<del><i>Pulp 3</i></del>)</li></ul>