Hi All, I'm starting to look at the built in Config Mgmt with templates for situations where cfengine/puppet cannot (for whatever reasons) be used.
I guess the first thing that came to mind is to have a default location for templates so that it would be available via variables to cobbler. Seems like: /var/lib/cobbler/templates might be a good choice, any thoughts? We do things (maybe a bit) different so I don't know if something as generic as webserver.template might work... but we could certainly take a standard httpd.conf file and replace all of the things you'd normally fill in with variables defined via ksopts (or some other mechanism). I'm trying to come up with some real world examples and would appreciate any ideas you might have. In cfengine, we do simply things like replace "#ServerName www.example.com:80" with "ServerName www.my.tld:80". Perhaps this works, perhaps it doesn't. As a small scale config-mgmt system I think it would work for us, but would it work for anyone else? We'd also use func, and func-inventory to trac changes over time... func-inventory creates a file-tracker directory in each system repo so I'm guessing that we can use it to at least allow for browsing of changes. Also, if your backup system is a large as our's then you realize it can sometimes take a long time to pull stuff off of the backup server and compare. Using a file tracker would allow us to check the repo 1st and then move on to the backup tapes afterward. I'd appreciate any thoughts, criticisms, suggestions that you might have. I also would love to see some real world examples that ppl might have. I'm happy to share ours, in a personally redacted way. Cheers, Harry _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
