Rudy Gevaert wrote:
Hello, On Thu, Feb 17, 2005 at 04:27:08PM +0100, Benedict Verheyen wrote:1. This should be avoided to prevent problems. Updates should really be monitored.I agree with this, but what when one has to update an infrastructure with over e.g. 100 servers?
>
If one has an uniform infrastrure consisting of the same configurations it can be tested on one server and then deployed with ease (I think). Rudy
In that case i would install one of those servers or another machine to download the packages every night (apt-proxy, apt-cacher,debmirror,...) and test the packages on another machine to see if something goes hideously wrong.
Then test the packages and if you can't see anything wrong with them and apt-listbugs doesn't list serious bugs, then you could issue an
apt-get --download-only --yes upgrade on all those machines. Also point their sources.list to the 1 machine serving as apt cache.(If updating 100 machines at the same time, using another machine as package cache could be interesting)
Regards, Benedict