|
Size: 625
Comment: TBC, tjyang's effort on using hg+trac to implement a DSA model.
|
Size: 1505
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| == Overview Unix System configuration management == | == Unix System configuration management Overview == |
| Line 5: | Line 5: |
| Every Unix system got deployed has a life similar to software source codes. Changes are done by system administrators. and those changes are hardly recorded or documented. | 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. |
| Line 7: | Line 7: |
| This howto is an attemp to use hg and Trac for tackling decentralized system administration. | 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. |
| Line 9: | Line 10: |
| === Modle of IT unix system administration === * DSA (decentralized system administration) * |
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 13: | Line 21: |
| hg is a distrubuted SCM that fit very well with current IT decentralized system administration model. TBC |
hg is a distributed SCM solution that fit very well with current IT DSA model. TBC |
| Line 16: | Line 23: |
| TBA | 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 18: | Line 27: |
| === References == | === 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
- hg on every system.
- python interpretor.
- Trac server.