Sure, I use cfengine... but it's a chicken and egg game and you have to start somewhere.
The setup I describe is when there are no other machines and I'm walking in to build something from the ground up.
Cheers, Harry
On 10/19/2011 09:28 AM, James Cammarata wrote:
On Wed, Oct 19, 2011 at 8:21 AM, Harry Hoffman hhoffman@ip-solutions.net wrote:
While maybe not "clonable" when building a brand new cobbler server I use root's .bash_history to guide me through what I've done.
For every config file I edit I always issue the command "cp $file $file-`date -I`" so I have the original to diff against to know exactly what changes were made.
Once done building the new cobbler server I take the history file, remove all of the things that are uneccesary (ls; pwd; etc) and put full paths on file and commands I've used the write all of this out to our wiki.
It works pretty well even when you don't get to document for days or weeks after you've finished the build.
I'd recommend looking into a configuration management system like puppet. You can lay down a consistent configuration very quickly using that. _______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler