On Apr 21, 2013, at 8:05 PM, Edward Ned Harvey (lopser) <lop...@nedharvey.com> wrote: > Yes, of course, the plan is to build a new standard, including all the > documentation, and replace the existing servers. But if you seriously have > only 1-3 servers to maintain, it's not worth building another server to be > the config management server.
Many CM tools support applying locally stored configuration, if creating a CM server is a problem. I use a local Puppet manifest to manage a server of mine; no puppetmaster needed. If Puppet isn't your thing, hosted Chef is free for less than 5 servers. I imagine there are others, but that's what I know. > (How do you manage the config of the config management server anyway?) In one environment, I have a kickstart manifest that will get the machine to a point where i can install Puppet, run 'git pull' on the appropriate modules/manifests/hieradata, and my CM setup is back in business. For that environment the loss of a CM server will not impact production, so a documented process is acceptable. -pc _______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
