Re: [Pulp-dev] Lazy for Pulp3

Thanks Justin! +1 to consider this use case, I can confirm that many users asked for that. Tanya On Wed, May 16, 2018 at 8:52 PM, Justin Sherrill wrote: > > > On 05/16/2018 01:02 PM, Brian Bouterse wrote: > > A mini-team of @jortel, @ttereshc, @ipanova, @dkliban, and @bmbouter met > today to d

Re: [Pulp-dev] Pulp 3.0.0b3 released

pulp-ansible 0.1.0b2 has been published to PyPI: https://pypi.org/project/pulp-ansible Changes include support for rq+redis. David On Wed, May 16, 2018 at 7:22 PM, Dennis Kliban wrote: > The following packages are now available on PyPI: >

[Pulp-dev] Content types which are not compatible with the normal pulp workflow

Some content types are not going to be compatible with the normal sync/publish/distribute Pulp workflows, and will need to be live API-only. To what degree should Pulp accomodate these use cases? Example: Pulp makes the assumptions that A) the metadata for a repository can be generated in its en

Re: [Pulp-dev] Pulp CLI MVP User Stories

The use cases we outlined earlier provide very little value over using httpie to interact with the REST API directly. I'd like to propose 5 new use cases: - As a CLI user, I can create a repository, a remote, a publisher, and a distribution with a single command. - As a CLI user, I can cr

Re: [Pulp-dev] Pulp CLI MVP User Stories

> > > The CLI will need to make some assumptions for the user: publisher name, > distribution name, auto publish, auto distribute, and maybe others. Are most of our users comfortable with these assumptions being made? The goal for the CLI should be to reduce this to a single step. +1 to this g

Re: [Pulp-dev] Pulp 3.0.0b3 released

pulp-python 3.0.0b2 has also been released with support for rq+redis https://pypi.org/project/pulp-python/3.0.0b2/#description On Thu, May 17, 2018 at 8:43 AM, David Davis wrote: > pulp-ansible 0.1.0b2 has been published to PyPI: > > https://pypi.org/project/pulp-ansible >

Re: [Pulp-dev] Pulp CLI MVP User Stories

Overall, I am hesitant to start with complex CLI commands. Instead I had hoped to start with basic, auto-generated CLI commands which we could then build off to add more complex commands in the future. Questions/responses inline though. On Thu, May 17, 2018 at 11:52 AM, Dennis Kliban wrote: > T

Re: [Pulp-dev] Pulp 3 plugin for Chef cookbooks

On Wed, May 16, 2018 at 04:14:33PM -0400, David Davis wrote: >This is great. I had a chance to look at your plugin and am really >excited by having chef support in Pulp. >Some responses below. >On Tue, May 15, 2018 at 2:31 PM, Simon Baatz <[1]gmbno...@gmail.com> >wrote: > >

[Pulp-dev] Integrating Katello with Pulp3 Recap

Today @dkliban, @daviddavis, and I met with two Katello developers, @jsherrill and @paji, to talk through some of the integration of Katello and Pulp3. Here is a recap of what we discussed, a goal we identified, and next steps. # What we discussed We went through Katello's UI and learned about:

Re: [Pulp-dev] Integrating Katello with Pulp3 Recap

+1 to the schedule - we have folks who will likely head up different efforts and we will want them to participate. On Thu, May 17, 2018 at 3:32 PM, Brian Bouterse wrote: > Today @dkliban, @daviddavis, and I met with two Katello developers, > @jsherrill and @paji, to talk through some of the inte

Re: [Pulp-dev] Pulp api seemingly incompatible with generated bindings

I have been able modify the default behavior of swagger-codegen to produce bindings that use relative URLs to identify resources. The required changes can be seen here[0]. The compiled jar is available for download here[1]. The following command can be used to generate python bindings. Replace 'py

Re: [Pulp-dev] Pulp 3 plugin for Chef cookbooks

On Thu, May 17, 2018 at 3:01 PM, Simon Baatz wrote: > On Wed, May 16, 2018 at 04:14:33PM -0400, David Davis wrote: > >This is great. I had a chance to look at your plugin and am really > >excited by having chef support in Pulp. > >Some responses below. > >On Tue, May 15, 2018 at 2