[Gllug] Change Management tools

[Tethys]

Bruce Richardson writes:

>That's not enough even for change tracking, let alone change management.
>Using a revision control system to track /etc, for example, allows
>sysadmins a) to check whether the machine they are working on is in a
>consitent, approved state, b) to roll back to a previous state if
>they've messed something up and c) having made successful changes, to
>check in the new consistent state, adding in comments to explain what
>has been done.

We use AIDE to verify that the machine is in a consistent, approved
state. Any changes are detected, and a simple web front end lets us
add annotations to explain the reasons for the change (which should
tie in to a change request number, although they don't always do so
yet). As for who's made the change, you'd need process accounting or
something like systrace/dtrace to be able to see that sort of information,
which starts getting pretty invasive and potentially harms performance.

Tet
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug