Thanks for the clarity. That explanation definitely helped me wrap my head
around it.

On Mon, Feb 5, 2018 at 5:47 AM, Dennis Kliban <[email protected]> wrote:

> I update issue 2894[0] with the new name, Exporter. Can someone please
> groom this ticket?
>
> [0]https://pulp.plan.io/issues/2894
>
>
> Thanks,
> Dennis
>
> On Fri, Feb 2, 2018 at 5:28 PM, Daniel Alley <[email protected]> wrote:
>
>> +1 rename
>>
>> On Fri, Feb 2, 2018 at 10:51 AM, Austin Macdonald <[email protected]>
>> wrote:
>>
>>> +1 rename to Exporter.
>>>
>>> On Fri, Feb 2, 2018 at 10:13 AM, Brian Bouterse <[email protected]>
>>> wrote:
>>>
>>>> +1 to renaming a Pulp3 'Distributor' to be 'Exporter'. The name of a
>>>> 'Distribution' (when Pulp serves bits using its webserver) would stay the
>>>> same. Currently the names Distributor and Distribution sound so similar
>>>> that its very confusing. A Distribution and an Exporter would be clearer
>>>> names I think.
>>>>
>>>> On Thu, Feb 1, 2018 at 10:30 AM, Dennis Kliban <[email protected]>
>>>> 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.
>>>>>
>>>>> 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 <[email protected]> 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 <[email protected]>
>>>>>> 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
>>>>>>> [email protected]
>>>>>>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Pulp-dev mailing list
>>>>> [email protected]
>>>>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Pulp-dev mailing list
>>>> [email protected]
>>>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Pulp-dev mailing list
>>> [email protected]
>>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>>
>>>
>>
>> _______________________________________________
>> Pulp-dev mailing list
>> [email protected]
>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>
>>
>
> _______________________________________________
> Pulp-dev mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
>
_______________________________________________
Pulp-dev mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/pulp-dev

Reply via email to