version controlling our configurations

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just like I would be nervous without backup, I'm nervous that our configuration files are not (yet) under version control. I'd prefer that we use e.g. Puppet or Chef (I'd like to try Puppet because of the knowledge around me, but am flexible if you are a Chef du jour), but until we get to that, I had a quick-fix idea. Because /etc contains a few passwords, I don't want to put this on any open systems, and we don't have that many systems (yet) to have a dedicated backup/config cluster (or whatever is the solution there.) What if we use a local git repo on linode01.ovirt.org, then do a checkout on each of the other hosts so root can locally update the repository and push to the master on linode01? Trusted admins can have a clone of the repository locally (on their encrypted partitions, natch.) Good? Bad? Have a better solution for now? - - Karsten - -- name: Karsten 'quaid' Wade, Sr. Community Architect team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41