[Gllug] Change Management tools

[Bruce Richardson]

On Wed, Jun 08, 2005 at 12:20:18PM +0100, Huw wrote:
> 
> linux package management tools (e.g. deb and rpm) track that kind of
> info. It wouldn't be very difficult to poll the package DBs on each host
> and dump the pertinent info into a central database.

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.  In a production environment, you might make the changes
to a test system, check the changes in and then use the rcs tool to pull
them down to the live servers.

It is also possible to integrate change management tools like cfengine
with a revision control system.

-- 
Bruce

What would Edward Woodward do?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 261 bytes
Desc: Digital signature
URL: <http://mailman.lug.org.uk/pipermail/gllug/attachments/20050608/d98cd785/attachment.pgp>
-------------- next part --------------
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug