[Pulp-dev] Proposal to remove 'notes' fields from the Pulp 3 RC

2018-12-03 Thread Daniel Alley
*Background:* "Notes" are a generic key value store where data can be attached to repositories and content and publications and so forth. The eventual plan is to use this to enable adding tags to those sorts of objects, which is important for Katello. Most of the code for this is located in pulp

Re: [Pulp-dev] Proposal: merge the content-app & streamer

2018-12-03 Thread Dennis Kliban
It was pointed out on IRC that plugins that have to supply their own content app (such as docker) currently need to supply 2 implementations of it in order to support on-demand use cases. One using django and another using aiohttp. We should not burden plugin writers in such a way. We really have

Re: [Pulp-dev] Proposal: merge the content-app & streamer

2018-12-03 Thread Dana Walker
In light of the efficiency gains and lack of significant drawbacks, I'm +1 on this proposal. --Dana Dana Walker Associate Software Engineer Red Hat On Mon, Dec 3, 2018 at 2:40 PM Dennis Kliban wrote: > I like the idea of combining the two appl

Re: [Pulp-dev] Possible Pulp3 RC Blocker issues from backlog

2018-12-03 Thread David Davis
Thanks for digging through older issues to find potential RC blockers. 2889 - +1 to making it an RC blocker 2635 - +1 here as well 2850 - I spent some time working on this and didn’t get far. I think we should just require the db to be running. I vote to close it out. 2989 - +1 to RC blocker 3044

[Pulp-dev] Possible Pulp3 RC Blocker issues from backlog

2018-12-03 Thread Austin Macdonald
To be on the safe side, I'd like to highlight issues that *might* need to be RC blockers. Please reply directly onto the issue, I'll update this thread periodically if necessary. REST API, backwards incompatible changes: - Add Task Names: - https://pulp.plan.io/issues/2889 - IMO: W

Re: [Pulp-dev] Proposal: merge the content-app & streamer

2018-12-03 Thread Dennis Kliban
I like the idea of combining the two applications for all the reasons already outlined on this thread. The user experience is going to be simplified by this change. However, I want to point out that it will also alter the plugin writer experience. Plugin writers that want to have their own content

Re: [Pulp-dev] Distributing Pulp3 Plans

2018-12-03 Thread Daniel Alley
No objection On Mon, Dec 3, 2018 at 11:52 AM Jeff Ortel wrote: > +1 > > On 12/1/18 6:01 AM, David Davis wrote: > > +1 from me. > > David > > > On Fri, Nov 30, 2018 at 10:26 AM Dennis Kliban wrote: > >> No objections from me. >> >> On Thu, Nov 29, 2018 at 7:50 AM Brian Bouterse >> wrote: >> >>>

Re: [Pulp-dev] Distributing Pulp3 Plans

2018-12-03 Thread Jeff Ortel
+1 On 12/1/18 6:01 AM, David Davis wrote: +1 from me. David On Fri, Nov 30, 2018 at 10:26 AM Dennis Kliban > wrote: No objections from me. On Thu, Nov 29, 2018 at 7:50 AM Brian Bouterse mailto:bbout...@redhat.com>> wrote: The plan about 12-24