Re: [Pulp-dev] Pulp 3 release quality

Thanks for the suggestion Dana! David and I have added daily cron jobs to Travis that run the same tests that are run for each PR. The latest status of the build for pulp repository is displayed at the top of the README[0]. The unit test coverage report status is also displayed in the same location

Re: [Pulp-dev] Pulp 3 Release Process Questions

One of the requirements for Pulp 3 is to be able to run on a wide range of Linux distributions. Being a Python application, that means we can achieve that goal by following good Python development practices. Part of those good practices is releasing packages via the Python Package Index (PyPI). Pu

Re: [Pulp-dev] Tracking GA issues

On Wed, Apr 18, 2018 at 3:23 PM, Austin Macdonald wrote: > +1 a little late :) > > For clarity I'll state how I assume this will work: > >- Milestone of 3.0 blocks GA release >- Milestone of 3.1 blocks 3.1 >- Pulp 3 Tag indicates that the issue is Pulp 3+, no blocking >relationshi

Re: [Pulp-dev] Tracking GA issues

+1 a little late :) For clarity I'll state how I assume this will work: - Milestone of 3.0 blocks GA release - Milestone of 3.1 blocks 3.1 - Pulp 3 Tag indicates that the issue is Pulp 3+, no blocking relationship (aka, not Pulp 2) - Pulp 3 MVP will only be used for historical reas

Re: [Pulp-dev] Pulp 3 MVP Issue Cleanup

I added two categories: 'CLI' and 'Migration Tool' to the core project in Redmine On Tue, Apr 10, 2018 at 4:42 PM, Dennis Kliban wrote: > I still think the CLI should have it's own project if we are going to > version it separately from Pulp. I hope we do version it separately from > pulpcore. >

Re: [Pulp-dev] Pulp 3 Release Process Questions

Since this is a change from Pulp 2, I think it would be helpful to outline the reasoning behind such a change and ask that spell those out here for transparency. In addition, are there any concerns we think others may have or new problems that such a change brings about that we need to work to answ

Re: [Pulp-dev] Tracking GA issues

I added a milestone for 3.0 and 3.1 to the Pulp project. Redmine items tagged with that milestone will show up on the roadmap pages below: https://pulp.plan.io/versions/57 https://pulp.plan.io/versions/58 https://pulp.plan.io/projects/pulp/roadmap On Wed, Apr 18, 2018 at 2:11 PM, Robin Chan w

Re: [Pulp-dev] Tracking GA issues

+1 to both of those proposals (3.0 and 3.1) On Wed, Apr 18, 2018 at 1:43 PM, Daniel Alley wrote: > +1 > > On Wed, Apr 18, 2018 at 12:11 PM, Dana Walker wrote: > >> +1 >> >> I like this idea for tracking purposes so that things do not fall by the >> wayside and for organization of future aims. >

Re: [Pulp-dev] Tracking GA issues

+1 On Wed, Apr 18, 2018 at 12:11 PM, Dana Walker wrote: > +1 > > I like this idea for tracking purposes so that things do not fall by the > wayside and for organization of future aims. > > --Dana > > Dana Walker > > Associate Software Engineer > > Red Hat > > >

[Pulp-dev] Next Sprint

As we approach our next Sprint planning on Friday, here are what I believe to be our priorities. I welcome any feedback/questions/concerns. 1. Remaining Pulp 3.0 Core Beta items Note - does include items not in Core Do we have python plugin beta items? 2. Pulp 2 work - Commitments to stake holders

Re: [Pulp-dev] Pulp 3 content import

Thank you Austin and David for correcting me. It sounds like each plugin will implement how to handle creating SomeContent from 0 or more artifacts. This will include having the server inspect the Artifacts and generate required metadata. In this case the client will be able to import content into

Re: [Pulp-dev] Pulp 3 content import

On Wed, Apr 18, 2018 at 12:03 PM, Dennis Kliban wrote: > On Wed, Apr 18, 2018 at 11:02 AM, Simon Baatz wrote: > >> I am looking at Pulp 3 for the first time and have a question on >> creating/importing content units. >> >> In the file plugin, a file content unit can be created using >> POST@.../

Re: [Pulp-dev] Pulp 3 content import

I actually wrote this code[0] in Pulp 2 for the puppet plugin so maybe I can chime in. > As you pointed out, it requires the REST API client to know all the metadata required to create a piece of Content from an Artifact. This not quite true. The pulp_file plugin currently extracts metadata (ie d

Re: [Pulp-dev] Tracking GA issues

On Wed, Apr 18, 2018 at 12:04 PM, David Davis wrote: > We’ve been removing the Pulp 3 MVP tag from pulpcore issues in redmine > that we’re not going to complete for the Beta next week but some of these > issues we may want for the 3.0 GA. > > I’d like to propose we create a Pulp 3.0 milestone in

Re: [Pulp-dev] Tracking GA issues

+1 I like this idea for tracking purposes so that things do not fall by the wayside and for organization of future aims. --Dana Dana Walker Associate Software Engineer Red Hat On Wed, Apr 18, 2018 at 12:04 PM, David Davis wrote: > We’ve been re

[Pulp-dev] Tracking GA issues

We’ve been removing the Pulp 3 MVP tag from pulpcore issues in redmine that we’re not going to complete for the Beta next week but some of these issues we may want for the 3.0 GA. I’d like to propose we create a Pulp 3.0 milestone in redmine for the Pulp project and start adding issues to it. I wa

Re: [Pulp-dev] Pulp 3 content import

On Wed, Apr 18, 2018 at 11:02 AM, Simon Baatz wrote: > I am looking at Pulp 3 for the first time and have a question on > creating/importing content units. > > In the file plugin, a file content unit can be created using > POST@.../content/file/ by passing the meta-data ('relative_path') and the

[Pulp-dev] Pulp 3 content import

I am looking at Pulp 3 for the first time and have a question on creating/importing content units. In the file plugin, a file content unit can be created using POST@.../content/file/ by passing the meta-data ('relative_path') and the artifact (from which 'digest' is obtained as additional meta-dat

[Pulp-dev] Call for Presenters: Community Demo, Wednesday April 25

Have you contributed to Pulp or the Pulp community in some way since the last community demo? Show the community what you've done! The next community demo is scheduled for Wednesday, April 25 at 14:00 UTC [0]. All demos should be pre-recorded; here are some docs on how to do that [1]. Once you ha

Re: [Pulp-dev] Pulp 3 REST API Challenges

I believe option 1 is a better fit as I think a new repository version is a side-effect of a (plug-in specific) action on a repository. Cheers, milan On Mon, Apr 16, 2018 at 10:31 PM, Dennis Kliban wrote: > On Fri, Apr 13, 2018 at 3:55 PM, Jeff Ortel wrote: >> >> >> >> On 04/12/2018 04:49 PM, D