With all due respect to my esteemed colleagues, as someone who as also played and/or worked with a small variety of config mgmt systems: They're all, basically, the same.
Oh, don't get me wrong, they all have different syntaxes, layouts and systems. But in the end, here are your collections, here's how you get it on your systems, here's your config files, film at 11. I'm sure I'll get lambasted by various converts, if not the people who write these systems, if not tossed on the BBQ and roasted for these words. (please use a spicy sauce, people.) What you need from people here isn't "I like XYZ" it's "Can XYZ do this?" However you will probably need to get some of the more major ones and at the very very least look at the documentation, if not do a test setup and see what works best. Do you want a push or pull configuration? Do you want the client to be able to have editable config file locally or should everything be on the master server? Do you care if the backend is written in C or a scripting language? Do you want fries with that? With all seriousness you really are going to have to try things out yourself. I believe the most common software packages are cfengine, bfcg, puppet and, maybe, radmind. I'm sure proponents of others will speak up. Remember the lesser known ones may have less support, but there's an argument for 5 dedicated coders over 50 squabbling shmoes. Good luck, and remember, if all else fails, nuke everything from orbit. It's the only way to be sure. Moose _______________________________________________ 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/
