Difference between revisions of "Configuration Management"
(→Virtualisation) |
|||
| (5 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| + | {{Historical}} |
||
| − | ==How best to manage the configuration of the servers== |
||
| + | =Puppet= |
||
| − | *It has become clear that a configuration managment system needs to be implemented for the servers |
||
| + | ==Adding a new client== |
||
| − | ==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 |
||
| − | *Xen 3.0.3 will reach etch on Oct-31st. Remaining updates are most likely to just be bug fixes. |
||
| + | On the client: |
||
| − | ==Revision Control System== |
||
| + | '''sudo aptitude install puppet''' |
||
| − | */etc could be put into CVS |
||
| + | '''sudo puppetd --test''' |
||
| − | *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 |
||
| + | On the server (puppet): |
||
| − | ==Configuration Management Software== |
||
| + | '''sudo puppetca --list''' |
||
| − | *Cfengine or puppy are the most popular candidates |
||
| + | The new client hostname should be displayed. Then |
||
| − | [[Category:Servers]] |
||
| + | '''sudo puppetca --sign''' ''<client hostname>'' |
||
| + | |||
| + | |||
| + | [[Category:IT]] |
||
Latest revision as of 22:53, 9 February 2019
 | This page is obsolete. It is kept for historical interest only. It may document extensions or features that are obsolete and/or no longer supported. Do not rely on the information here being up-to-date. |
Puppet
Adding a new client
On the client:
sudo aptitude install puppet sudo puppetd --test
On the server (puppet):
sudo puppetca --list
The new client hostname should be displayed. Then
sudo puppetca --sign <client hostname>
