[katello-devel] Deployable and System Template Portability

[Bryan Kearney]

On 08/14/2012 09:03 AM, James Labocki wrote:
>
>
> ----- Original Message -----
>> From: "Ivan Nečas" <inecas at redhat.com>
>> To: "James Labocki" <jlabocki at redhat.com>
>> Cc: "aeolus-devel" <aeolus-devel at fedorahosted.org>, "katello-devel" <katello-devel at redhat.com>, "Steven Reichard"
>> <sreichar at redhat.com>, "Francesco Vollero" <fvollero at redhat.com>
>> Sent: Tuesday, August 14, 2012 2:14:48 AM
>> Subject: Re: [katello-devel] Deployable and System Template Portability
>>
>> On 08/13/2012 08:30 PM, James Labocki wrote:
>>>
>>> Last week a few of us were discussing the ability to import/export
>>> deployables within aeolus for sharing between differing
>>> implementations.
>>>
>> What does "differing implementations" mean in this context?
>
> Customer A installs System Engine and creates Custom ProviderX with ProductY and RepoZ
> Customer B installs System Engine and creates Custom ProviderA with ProductB and RepoC
>
> Customer A creates system template which references RepoZ, hands system template to Customer B.
> Customer B takes system template and imports it into his/her cloud engine. The custom provider is does not exist in his system engine (assuming he changes the path the system engine host in the template) and the certs don't match.
>
> That is what I mean by differing implementations. Does that help?
>


yes, but I do not see this as a bug. What is the real use case for 
crossing customers like this?

-- bk