Feature #378
closed
Multiple Kickstart Files/Profiles
Added by Jon Fautley over 14 years ago.
Updated about 14 years ago.
Category:
Unattended installations
|
|
Description
It would be exceptionally useful to have the ability to tie a specific kickstart file to an individual host group.
We deploy a variety of systems based on RHEL and CentOS, and have to have different kickstarts for each, for example for additional repos required for Cobbler installations vs. RHEL installations.
This is also useful where we have 'dev' systems which have a much larger package set than 'prod' systems. Managing this sort of thing through kickstart is significantly faster/easier than doing the same through Puppet. (cf. Puppet RFEs/bugs with the speed of the Yum package provider).
(This RFE was raised after speaking with Ohad on IRC, let me know if you'd like any further details/justification)
would you like the ks files to be as simple files (some where on the file system) or rather editable via the gui?
- Target version set to 0.2
ok, my thoughts on this one for now.
- Each host group can be associated with a kickstart template
- New templates can be added into the database, not the file system.
- Each template needs to be associated with a os family (e.g. a template can work for both Fedora and RedHat)
- The default kickstart view will be rendered only if no other kickstarts are associated with the system.
open questions
- can individual hosts be associated with a kickstart template as well (e.g. from a drop down), imho its missing the whole point.. but ymmv.
- how much of an editor do we need to put it (syntax highlight, ks validation etc)
- how do we migrate from the existing setup to the new layout?
Best if we chat about this over irc?
- Branch set to 378-multi-templates
updated work in progress patch at my github branch 378-multi-templates
- Status changed from New to Ready For Testing
- % Done changed from 0 to 100
- Status changed from Ready For Testing to Closed
Also available in: Atom
PDF
Updated by