|
Size: 1505
Comment:
|
Size: 1906
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| 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. | Every computer systems got deployed has a life similar to software source codes, they need to face changes. Once the system is built and delivered into production by OS CD or netinstall server, it assume its decentralized life in an IT system or your home. Configuration changes over time without proper tracking often make the system unmanageable. |
| Line 7: | Line 7: |
| Changes are done by system administrators and those configuration changes are hardly recorded or documented. | Changes are done by system administrators daily and those configuration changes are hardly recorded or documented. |
| Line 20: | Line 20: |
| === 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. |
=== Requirements === 1. We want to have a check in/out mechanism on every computer system without dependency of central SCM server online. 1. We want to have a SCM server to push the change to when SA feel guilty. 1. We want to be able to find out a machine's configuration got changed by web browser. |
| Line 27: | Line 25: |
| === Bill of Material === 1. hg on every system. |
=== Bill of Materials === 1. hg client/server on every system. hg is a distributed SCM solution that fit very well with current IT GSA model. TBC |
| Line 31: | Line 31: |
| 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 32: | Line 35: |
| 1. cfinge |
Unix System configuration management Overview
Every computer systems got deployed has a life similar to software source codes, they need to face changes. Once the system is built and delivered into production by OS CD or netinstall server, it assume its decentralized life in an IT system or your home. Configuration changes over time without proper tracking often make the system unmanageable.
Changes are done by system administrators daily 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.
Requirements
- We want to have a check in/out mechanism on every computer system without dependency of central SCM server online.
- We want to have a SCM server to push the change to when SA feel guilty.
- We want to be able to find out a machine's configuration got changed by web browser.
Bill of Materials
- hg client/server on every system.
- hg is a distributed SCM solution that fit very well with current IT GSA model. TBC
- python interpretor.
- Trac server.
- 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.
References
- cfinge