On Thu, Jun 28, 2012 at 9:52 AM, Brian Mathis < [email protected]> wrote:
> > > These days, a "proper" kickstart solution should be considered: > Kickstart does your OS install and gets a puppet agent installed. > Everything after that should be done by puppet. There shouldn't be > much in the %post script doing config changes beyond what you need to > get puppet working. > Exactly correct :-) Kickstart's job is to get the base, minimal OS installed. The OS's entire purpose in life is to run Puppet :-) Any user applications are just an incidental usage beyond that :-) The San Diego Supercomputer Center has been running this way since about 1995, although with cfengine. Separating the configuration (cfengine, Puppet, chef, etc) from the base OS install makes it easier to use per-OS installation systems, too. Whether it is kickstart for Linux, jumpstart for Solaris, or PXE of a minimal image, that separates all the OS-specific installation stuff from the "site configuration" layer which is less OS-specific.
_______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
