[Pulp-dev] pulp 3 distributor use cases

[Dennis Kliban]

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.

The names are very similar, but perform different function. Perhaps
Distributors should be called Exporters instead.

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?
>
>
> Thanks,
> Eric
>
> 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[0].
>> 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.
>>
>> [0] https://pulp.plan.io/projects/pulp/wiki/Pulp_3_Minimum_Viabl
>> e_Product/diff?utf8=%E2%9C%93&version=143&version_from=142&
>> commit=View+differences
>>
>> Thanks,
>> Dennis
>>
>> _______________________________________________
>> 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/20180201/2541f13c/attachment.htm>