The end result will be a decision on which configuration management utility we will be using to replace our current "Deploy configuration using RPMs" method, which admittedly is a 1000 times better than doing everything manually, but does lack both full automation of deployments and scalability. The primary limitation of the RPM method is that it is push by design rather than pull.
Things to do
- Setup KVM with dnsmasq to spin up multiple VMs (One puppet/cfengine server, one NFS server and one NFS client)
- Setup Cobbler to provision the VMs using CentOS 5.5
- Boot strap cfengine, then puppet into the build of above mentioned VMs
- Perform all configuration through both cfengine and puppet
- Which solution is best for adding mounts, packages and making configuration changes to files
- Which solution will best fit the needs of my business aligned team and the operations team, most of whom have never used configuration management
- Which solution can best automate our patching procedure.
- Which solution has the best documentation and the best bang for the buck in terms of the team learning it.