[Pulp-dev] pulp 3 distributor use cases
ehelms at redhat.com
Thu Feb 1 23:38:52 UTC 2018
On Thu, Feb 1, 2018 at 10:30 AM, Dennis Kliban <dkliban at redhat.com> wrote:
> Distributors are only used for exporting Publications out of Pulp.
> Distributions make Publications available to consume via http(s) at
> /content/relative/path/of/distribution/. Each Publication can be
> associated with any number of Distributions.
You lost me a bit here getting into distributions. I think I want to be
able to export the same repository to two separate published locations.
Say I have a repository A. I want to make repository A available at the
Is that possible in the design?
> The names are very similar, but perform different function. Perhaps
> Distributors should be called Exporters instead.
For me, either naming scheme works though perhaps for most exporters might
> On Thu, Feb 1, 2018 at 2:35 PM, Eric Helms <ehelms at redhat.com> wrote:
>> Will Pulp 3 support multiple distributors on a single repository? Could
>> I, for example, attach the yum distributor multiple times but with a
>> different output path to publish the same repository at different locations?
>> On Thu, Feb 1, 2018 at 6:54 AM, Dennis Kliban <dkliban at redhat.com> wrote:
>>> I've updated the MVP use cases for the Distributors. The diff is
>>> here. I removed the use case of a distributor exporting a Repository
>>> Version. The idea is to give users a single way to export repository
>>> versions. Users will first create a publication and then use a distributor
>>> to export that publication.
>>> Please reply to this thread with any suggestions for the use cases
>>> related to Distributors.
>>> I'd like to write up stories for these use cases early next week, so the
>>> work can be merged by Feb 15th.
>>>  https://pulp.plan.io/projects/pulp/wiki/Pulp_3_Minimum_Viabl
>>> Pulp-dev mailing list
>>> Pulp-dev at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev