[Pulp-dev] pulp 3 distributor use cases

[Dennis Kliban]

On Fri, Feb 2, 2018 at 12:38 AM, Eric Helms <ehelms at redhat.com> wrote:

>
>
> 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
> following paths:
>
> https://myserver/pulp/repos/Acme/Dev/Version_2/
> https://myserver/pulp/repos/Acme/Test/Version_2/
>
> Is that possible in the design?
>
>

Yes it is possible. A Distribution defines a relative path at which a
Publication is made available. In Pulp 3, 'pulp/repos' portion of the path
has been replaced with 'content'. The rest of the URL is defined by the
relative path of a Distribution. Your example would actually be

https://myserver/content/Acme/Dev/Version_2/
https://myserver/content/Acme/Test/Version_2/

'Acme/Dev/Version_2' would be the relative path of one Distribution.
'Acme/Test/Version_2' would be the relative path of the other Distribution.

I foresee Katello only using Distributions and not Distributors.
Distributors are needed for use cases where users want to continue using
symlinks for their published content. A good example would be to export a
Publication to the CDN which does not have access to the Pulp database. A
Distributor would generate symlinks and rsync them and the artifacts they
point to to the CDN. Then content can be consumed from the CDN without Pulp
being installed there.

As long as content is being served from a web server that has access to the
Pulp database, a Distribution should be all that is necessary.



>
>> 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
> click easier.
>
>
>>
>> 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&c
>>>> ommit=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/20180202/58c4e1df/attachment.htm>