On Tue, 4 May 2010, Tracy Reed wrote: > 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.
*I* know this, I'm trying to find serious references citing "best practices" so I can go chat with management. >> 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. I have a rant about old time Solaris admins constantly wanting to do things the hard way that I will not post here, so lets just say these folks have probably never even heard of using version control related to systems administration. Also some of their security practices are terrifying and not just because I recently passed my CISSP exam. I hope that (big A) auditors never ask me anything. -- Matt It's not what I know that counts. It's what I can remember in time to use. _______________________________________________ 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/
