On Tue, May 04, 2010 at 04:45:15PM -0500, Matt Lawrence spake thusly: > that are used to install most of the systems. The one I am looking at > right now is 1648 lines long, with about 1600 of them in the %post clause.
Wow! > I am of the opinion this is a bad idea, a kickstart shouldn't do much more > than get a system up, running and able to talk to a configuration > management system. Naturally, there is no configuration management system > and systems are left as initially installed for years. Correct. Kickstart should just get the basics (partitioning, basic software installed, network connectivity of some sort configured). Then I suggest puppet (my favorite) or cfengine/chef/bcfg or whatever to handly everything from then on. The biggest problem with their current setup being that %post only runs once and that is at install time. After that you can never make configuration changes again in an automated way without something like puppet etc. > So, I'm looking for references to best practices that I can take to my > boss and other management on the preferred way of doing RHEL kickstarts > and configuration management. Any suggestions? TAL? Don't forget to check the current kickstart into version control if that hasn't been done already so you can keep track of where you have been config-wise. -- Tracy Reed http://tracyreed.org
pgpFFJl7IT03D.pgp
Description: PGP signature
_______________________________________________ Tech mailing list [email protected] http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
