On 07/17/2012 09:36 AM, Ivan Nečas wrote:
On 07/17/2012 02:57 PM, Chris Alfonso wrote:
> On 17/07/12 08:15 -0400, Bryan Kearney wrote:
> --snip--
>> 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?
>>
> Image Factory hands the TDL off to Oz. Ditching TDL would mean Image
> Factory ditches Oz, and I think the scope of work would quickly
> increase. I recommend we do not ditch TDL and instead translate the
> ks from foreman into a valid TDL.
>
https://github.com/clalancette/oz/blob/master/docs/tdl.rng
>
The difference between TDL and Foreman kickstart is, that in TDL there
might be packages, that in Foreman are not part of the kickstart, but
handled after the first boot by Puppet. Therefore the information about
packages to be installed is hidden inside used puppet modules.
So, somewhere in the kickstart file template is an @base or equivilant.
That is what needs to be in the TYL
So, as Ohad suggested we would need either:
1. extract the list of packages from the Puppet modules (is it doable
by puppet?)
2. run selected puppet modules against the the image before
deployment (is this doable?), not sure if Oz supports this kind of stuff
nor that we would be able to always run the puppet manifests without
knowing some specifics about the system (some variables in puppet
manifests can be loaded directly from Foreman, which is not available on
image-build time)
the option 3 is to install the listed packages without puppet when
provisioning using Foreman, directly in kickstart (not sure if it's
possible to use entitlements certs there). But it's some kind of
duplicate information, since it should be part of the Puppet manifests
as well.
No.. need to get the filelist from the ks file.
-- b k