← Revision 1 as of 2002-07-10 10:08:43
Size: 1660
Comment:
|
← Revision 2 as of 2002-07-10 10:16:30 →
Size: 1652
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 16: | Line 16: |
* CVS - The main problem with CVS is that it's hard to manage when you want some files to be identical across all machines (passwd/shadow) and other files to be different for every machine (resolv.conf/hosts). There was a [http://lists.personaltelco.net/pipermail/ptp/2002q3/014233.html good post] on a DebianLinux MailingList referencing one way of doing it. SteveBeattie had [http://lists.personaltelco.net/pipermail/ptp/2002q3/014233.html another suggestion] of using CVS brances to control which versions of files go out to given servers. |
* CVS - The main problem with CVS is that it's hard to manage when you want some files to be identical across all machines (passwd/shadow) and other files to be different for every machine (resolv.conf/hosts). There was a [http://lists.personaltelco.net/pipermail/ptp/2002q3/014233.html good post] on a DebianLinux MailingList referencing one way of doing it. SteveBeattie had [http://lists.personaltelco.net/pipermail/ptp/2002q3/014233.html another suggestion] of using CVS brances to control which versions of files go out to given servers. |
The SpecialOps team is currently investigating some method for configuration management. We've ended up managing more DebianLinux boxes then we'd originally expected and the membership of the SpecialOps team is a bit more dynamic then we'd expected so if nothing else we need a good way to manage users on each system. It was started with [http://lists.personaltelco.net/pipermail/ptp/2002q3/014225.html this thread] posted by AdamShand to the MailingList.
If you have any knowledge on how to manage config files using tools like CVS or cfengine we'd love to hear from you.
Currently we're investigating:
[http://www.iu.hio.no/cfengine/ CFEngine] - It has been recommended by serveral people as a good solution but none of the SpecialOps team has actually used it. MichaelRasmussen is checking it out.
CVS - The main problem with CVS is that it's hard to manage when you want some files to be identical across all machines (passwd/shadow) and other files to be different for every machine (resolv.conf/hosts). There was a [http://lists.personaltelco.net/pipermail/ptp/2002q3/014233.html good post] on a DebianLinux MailingList referencing one way of doing it. SteveBeattie had [http://lists.personaltelco.net/pipermail/ptp/2002q3/014233.html another suggestion] of using CVS brances to control which versions of files go out to given servers.
SteveBeattie and WilCooley recommended check on the [http://www.infrastructures.org/ Infrastructure] guys and that a [http://www.infrastructures.org/bootstrap/pushpull.shtml pull approach] was better then a push approach.