[katello-internal] Cloud Engine - System Engine V2 integration

Bryan Kearney bkearney at redhat.com
Tue Jul 17 12:15:48 UTC 2012


On 07/17/2012 03:21 AM, Ohad Levy wrote:
> On 07/16/2012 07:27 PM, Ivan Nečas wrote:
>> With funzo, we're trying to figure out how the Cloud Engine/System
>> Engine integration should look like, compared to V1.
>>
>> The templates in SE are going to be replaced with component outlines. In
>> discussion about Foreman integration, it was not mentioned, that the
>> Compontent Outline will contain the list of packages (System Template
>> like we know it today has it). This is not required by Foreman (Foreman
>> solves it with Puppet), but Cloud Engine is able to take the list of
>> packages and install it into the built image, if I understand it
>> correctly. Was it meant to be this way, or we just skipped it when
>> talking about Foreman. It seems quite valuable Cloud Engine feature to
>> me.
>
> We could easily use a foreman smart var / variable to store any
> arbitrary data, such as a package list.
>
> alternatively, we could consider extracting that data from puppet or
> running the puppet agent on the image once (with some sort of a image
> cleanup methods afterwards like windows sysprep or scripts that runs on
> public amis).

This data would be in the kickstart tempaltes.. yes? I assume if we go 
with TDL, we will need a way to translate the ks file which foreman 
generates into TDL. Or, could we:

1) have an alternate TDL tempalte
2) ditch TDL and have image factory get the kickstart from foreman directly?

-- bk



More information about the aeolus-devel mailing list