|
|||||||||||
|
Re: Automated Patch - Patch management -
From: Aaron Cheek <aaron_cheek(at)yahoo.com>
Date: Wed Apr 23 2003 - 17:11:28 EDT
Basically, you set up a system (the "gold server") for each OpenBSD release. When a new patch is released, you apply the patch to the "gold server" and then rsync the /usr, /bin, /sbin directories and the kernel (/bsd) to all the servers. Creating a script to automate this is trivial. Remember to exclude /usr/local and /usr/src from the synchronization. Eventually, you might have to run some commands on the remote machines manually (restart a daemon, reboot the machine or the like), but if you are handling a big number of machines you probably already have a mechanism in place to accomplish that. For more flexible configuration control and management you can use cfengine (http://www.cfengine.org/) instead of rsync. The result is that you end up applying the patches to only one machine and all the systems are kept in a coherent state. A nice side effect of this approach is that you don't need a compiler in your production machines. By the way, this is not an OpenBSD-only approach. Many other OSs work well with it (specially those that keep additional software in a separate location: /usr/local, /opt, ...). There is an interesting reference that you can check in this direction: http://www.infrastructures.org/
Aaron
This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 13:34:15 EDT |
||||||||||
|
|||||||||||