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
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.
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>
Unsupported bullets from Katello side are currently:
- package grops
- files
- commands
--
Later,
Lukas "lzap" Zapletal