[katello-devel] Deployable and System Template Portability

[Bryan Kearney]

On 08/14/2012 05:26 AM, Dmitri Dolguikh wrote:
> On 13/08/12 07:30 PM, James Labocki wrote:
>> Sorry for posting across both lists, but this involves both aeolus and katello.
>>
>> Last week a few of us were discussing the ability to import/export deployables within aeolus for sharing between differing implementations.
>>
>> The attached photo 1.JPG provides a high level diagram of some of the problems we believe exist in achieving this today. Please note that I used enterprise nomenclature, so I think that:
>>
>> - System Engine     = Katello
>> - Component Outline = Assembly
>> - Blueprint         = Deployable
>> - AppForm           = Deployment

With Foreman Integration, the goal is to kill templates and model 
component outlines off of Foreman Host Groups.

>>
>> We found the following areas differ between implementations and would need to be accounted for. Note this this was not an exhaustive exercise and I'm sure we missed some areas.
>>
>> - Providers paths are different in katello
>> - Certificates are different in system templates
>> - Repositories are different in system templates
>> - Deployables and their services are tightly coupled (not shareable)
>> - Clouds, Cloud Resource Zones, and Catalogs are different in aeolus
>>

Can you give examples of these issues? I would assume the TDL we are 
generating is valid.


-- bk