Idan Shinberg wrote:
Hello
I'm a heavy user of post Installation Code in the kickstart File.
Due to multiple profiles requirements , I've decided to devide my post
installation code into various cobbler SNIPPETS. [...]
My reply isn't about the detail, but rather about the principles.
It is tempting to try to get kickstart to do a lot of system
configuration. But I question that. My preference is to look at things
differently.
Just for the moment, forget about installation (I'll return to it
later). In the lifetime of the installed system, there will be ongoing
maintenance and configuration issues that need addressing. These, in
their own right, need some sort of management over that lifetime; that
is where configuration products such as cfengine or puppet etc. come
into play, to manage configuration changes.
Returning to installation: Consider using one of those configuration
products over the lifetime of the system. Then regard the immediate
post-install things, which you may currently be doing in your kickstart
"post", not as the final stage of the install, but rather as the first
stage of subsequent configuration, and get cfengine, puppet, etc. to do
them. Keep the kickstart post-install to a bare minimum; just enough to
get cfengine, puppet, etc. started. I understand that cobbler already
includes hooks to handle puppet in this way. (We use cfengine and do a
little post-install snippet work to bootstrap that.)
Just a thought...
--
: David Lee
: ECMWF (Data Handling System)
: Shinfield Park
: Reading RG2 9AX
: Berkshire
:
: tel: +44-118-9499 362
: email: david.lee(a)ecmwf.int