On 08/26/11 - 09:51:25AM, Lukas Zapletal wrote:
Hello,
thanks for explanation of all the terms. It's much more clear for me now.
> Where did you get this TDL? It is not valid, and will not work with the
> current imagefactory. I just want to know so that we can rectify whatever
> documentation you are looking at.
http://aeolusproject.org/wiki/uploads/7/76/ImageFactoryArch.odt
Thanks, I'll fix that up. In my mail yesterday, I forgot to point out where
the current documentation is. First, there are some basic examples on
aeolusproject.org:
http://aeolusproject.org/oz-examples.html
In the Oz git repository, there is also a relaxng schema for the TDL:
https://github.com/clalancette/oz/blob/master/docs/tdl.rng
There is also an XSD schema for the TDL in the imagefactory repository:
https://github.com/aeolusproject/imagefactory/blob/master/Documentation/T...
> Right, so this is a pretty good match. We have discussed adding package
> groups in the past. So far I've resisted adding it because it is necessarily a
> Linux-centric concept, and we want the TDL to be useful for Windows as well.
> You could argue that it would be optional and Windows would just not use it,
> and I might agree with you, but nobody has convinced me yet.
Frankly I like the package groups concept and we will eventually support
them in Katello I guess.
Sure. We don't have to hash this one out yet. It is a nice-to-have, and we
can examine adding it in the future.
> Also note that the TDL supports additional things above and beyond what you
> have above. In particular, the TDL allows you to inject arbitrary files into
> the image (a<files> section of the XML), and allows you to execute arbitrary
> commands at the end of the install process (similar to %post in kickstart,
> but done slightly differently). I'm not sure if either of those concepts map
> onto Katello concepts, but it is food for thought.
So I think I am only missing <files> and <commands> tag mapping. There
is no such feature of injecting files or submitting commands. Katello is
going to have concept of Remote Actions when you schedule remote
command(s) to be run on running machines via agent, but this is
different case.
Correct me if I am wrong, here is the complete TDL structure:
<template>
<name>{1,1}</name>
<os>{1,1}</os>
<description>{0,1}</description>
<packages>{0,1}</packages>
<files>{0,1}</files>
<commands>{0,1}</commands>
<repositories>{0,1}</repositories>
</template>
Right, that is the general idea. There are a few nuances with the exact XML
that you'll have to worry about, but hopefully the documentation above will
help with that.
Unsupported bullets from Katello side are currently:
- package grops
- files
- commands
Yes. I think <files> will be an important one to model, but for a first cut
you can always simulate <files> by creating an RPM. <commands> is similar.
Let us know if you have more questions.
--
Chris Lalancette