Auditing and Roll-Back for NimBUS configuration changes?

Discussion created by claus.langhans on Apr 21, 2009
Latest reply on May 20, 2010 by ntimm

On of the things I am missing in NimBUS is the ability to audit who did what and when and the ability to roll back changes. I know that the controller can write an audit log, if the key "audit" is set to yes (raw config). I can use this to see that something has changed but not what, which means I can not roll it back either.

I was wondering if it would be possible to use the logmon probe to tail the controller_audit.txt file and issue a command to the NAS to retrieve the configuration of the changed probe to a central location and check it in into a source control system like Subversion, Perforce or even CVS.

Has someone done something towards this direction? I am also intersted in other solutions to the audit and roll-back problem