Difference between revisions of "Configuration Management"
(→Virtualisation) |
(→Virtualisation) |
||
| Line 6: | Line 6: | ||
*Virtualisation of services would mean that they can be set up once and moved around the servers as hardware is upgraded |
*Virtualisation of services would mean that they can be set up once and moved around the servers as hardware is upgraded |
||
*Access can be controlled on a per-service level |
*Access can be controlled on a per-service level |
||
| + | *Does not solve the configuration managment problem |
||
*Xen 3.0.3 will reach etch on Oct-31st. Remaining updates are most likely to just be bug fixes. |
*Xen 3.0.3 will reach etch on Oct-31st. Remaining updates are most likely to just be bug fixes. |
||
Revision as of 08:16, 23 October 2006
Contents
How best to manage the configuration of the servers
- It has become clear that a configuration managment system needs to be implemented for the servers
Virtualisation
- Virtualisation of services would mean that they can be set up once and moved around the servers as hardware is upgraded
- Access can be controlled on a per-service level
- Does not solve the configuration managment problem
- Xen 3.0.3 will reach etch on Oct-31st. Remaining updates are most likely to just be bug fixes.
Revision Control System
- /etc could be put into CVS
- A possible structure would have different branches for each server and trunk holds common configuration
- Update would be pushed in a similar way to the website ie. on each commit a script is run to push the updates
Configuration Management Software
- Cfengine or puppy are the most popular candidates
