Differences between revisions 1 and 8 (spanning 7 versions)
Revision 1 as of 2006-12-03 11:56:19
Size: 133
Editor: tjyang
Comment:
Revision 8 as of 2006-12-12 22:13:14
Size: 1505
Editor: tjyang
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
#language fr
== Unix System configuration management ==
Texte.
#language english
== Unix System configuration management Overview ==

Every Unix system got deployed has a life similar to software source codes. Once the system is built and delivered into production by OS CD or netinstall server, it assume its decentralized life in an IT system. Configuration changes over time often make the system unmanageable.

Changes are done by system administrators and those configuration changes are hardly recorded or documented.
It is a costly process to dig out what got changed without a SCM solution.

There are many solutions exists to tackle this area of challenge(see references).

This howto is an attempt to use hg and Trac to tackle group system administration.


=== Model of IT Unix system administration ===

  * GSA (group system administration) : A group of system administrators administration a group of machines.
  * CSA (centralized system administration): One or two administrators administrate a group of machines.
Line 7: Line 21:
{{{
xxx
}}}
 hg is a distributed SCM solution that fit very well with current IT DSA model. TBC
=== Trac ===
 The use of Trac in this case is not to track source codes changes on a computer system.
 it is used to track system configuration files like NIS maps,/etc/hosts,/etc/nodes,/etc/mail/aliases etc.
 files to got changed by system administrator or software program.
Line 11: Line 27:
=== Trac ===
xxx
=== Bill of Material ===
 1. hg on every system.
    1. python interpretor.
 1. Trac server.
=== References ===

Unix System configuration management Overview

Every Unix system got deployed has a life similar to software source codes. Once the system is built and delivered into production by OS CD or netinstall server, it assume its decentralized life in an IT system. Configuration changes over time often make the system unmanageable.

Changes are done by system administrators and those configuration changes are hardly recorded or documented. It is a costly process to dig out what got changed without a SCM solution.

There are many solutions exists to tackle this area of challenge(see references).

This howto is an attempt to use hg and Trac to tackle group system administration.

Model of IT Unix system administration

  • GSA (group system administration) : A group of system administrators administration a group of machines.
  • CSA (centralized system administration): One or two administrators administrate a group of machines.

hg

  • hg is a distributed SCM solution that fit very well with current IT DSA model. TBC

Trac

  • The use of Trac in this case is not to track source codes changes on a computer system. it is used to track system configuration files like NIS maps,/etc/hosts,/etc/nodes,/etc/mail/aliases etc. files to got changed by system administrator or software program.

Bill of Material

  1. hg on every system.
    1. python interpretor.
  2. Trac server.

References

HgSysTrac (last edited 2012-05-13 09:39:35 by 62)