I'm using Cobbler to configure PXE boot for host installation.
What are the cobbler components I should keep under version control so that I can review the specifics of a host installation? Changes to snippets, kickstart files, profiles, repositories all could obscure what happened in the past.
How does/should version control interact with the Web interface?
Myself and one other indivdual will be taking over some of the daily firewall management duties soon and I'm looking for a way to track changes on our firewall configurations for auditing purposes and need some ideas on a good way to track changes the changes that are made.
I don't have a lot of specific criteria but here are some of the basic things I would like to be able to do:
I'm wondering if some sort of revision control software would work here as a way to track the the changes? Or if some other approach would work better for managing the change control in this situation.
I'm open to any and all suggestions at this point.
EDIT:
We are using a Checkpoint pair, one passive one active configuration. I will update again with specific model numbers when I get a chance.
How can I see a list of the last n commits to a CVS repository?
Thanks!
We have a homegrown config management system and we'd like to add config file versioning to it in a simple way. My first thought was svn (or similiar), but I'm concerned with creating a repo in one location, just to check it out in another location on the same system. In this case we have no use for remote or even multiple checkouts. Is there a software versioning system that lives in one location (metadata+working copy) and will store only deltas? Some of our configuration nodes have large tarballs and binary installers.
I keep most of my home directory's dot files under revision control, so that I can easily move changes between any of the five or so desktop machines and dozens of servers that I use. Unfortunately, my ~/.gconf directory is a bit of a pain when it comes to this, because gconfd seems to really like making arbitrary whitespace changes and, worse yet, updating the mtime="..." attributes on entries that it hasn't changed.
Has anybody any thoughts on good ways to deal with this? I would prefer never to have to commit whitespace changes or time changes when a value hasn't changed, so that I can easily track my diffs over time.