[Pulp-dev] pulp-3 mock API for use with foreman prep

David Davis daviddavis at redhat.com
Sat Mar 10 22:08:46 UTC 2018

To give some background, Katello has been involved in helping create the
user stories for our Pulp 3.0/MVP release. Also, we’re not targeting
integration with Katello until some future 3.x release.

As you suggest, I think it would be wise to design our integration with
Katello before our 3.0/MVP release and get Katello/foreman to sign off on
it because our API will be semantically versioned at 3.0. This means we
can’t change the Pulp 3.0 API (only add to it) once we’ve released 3.0.


On Sat, Mar 10, 2018 at 4:30 PM, Tom McKay <thomasmckay at redhat.com> wrote:

> Is there collaboration already between pulp and foreman devs in
> preparation for pulp-3 changes?
> I would feel more comfortable if as the pulp-3 api is developed a working
> mock api that foreman devs could code against. This would expose gaps in
> data, models, patterns, etc. I know foreman has a wrapper library called
> runcible[1] that would be the main point of changes and tests.
> In my opinion it would be a mistake to wait until production releases of
> pulp-3 to begin integration.
> Thoughts?
> [1] https://github.com/Katello/runcible
> _______________________________________________
> Pulp-dev mailing list
> Pulp-dev at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20180310/0f6dfeb8/attachment.htm>

More information about the Pulp-dev mailing list