Hello. I'm assuming that you have paswordless ssh to the servers in question as root. Also I assume that you don't use central management/deployment software (ansible/puppet/chef) In similar cases I usully use parallel-ssh (gnu-parallel is another alternative). First stage install the package manually on one server to see that configuration is OK, daemons restart, etc... If this stage is ok second step will be creating list of servers for "complain" list and install package on them trough parallel-ssh. Instead of waiting for complains, one can define metrics to check and use some monitoring appliance for verification. I case of failure remove package from repository and remove-install again. Third will be parallel-ssh install on all the servers.
P. S. In case of few tens of servers I'd prefer to work with ansible or alternative, it's worh it in most cases/ Best Regards, Evgeniy. On Tue, Aug 2, 2016 at 8:50 PM, Elazar Leibovich <elaz...@gmail.com> wrote: > Hi, > > I'm having a few (say, a few tens) Debian machines, with a local > repository defined. > > In the local repository I have some home made packages I'm building and > pushing to the local repository. > > When I'm upgrading my package, I want to be sure the update wouldn't cause > a problem. > > So I wish to install them on a few percentage of the machines, wait for > complaints. > > If complaints arrive - roll back. > Otherwise keep upgrading the whole machines. > > I'll appreciate your advice and experience of similar situation, > I'll appreciate if someone who had actual real life experience with this > situation would mention it in the comments. > > Thanks, > > _______________________________________________ > Linux-il mailing list > Linux-il@cs.huji.ac.il > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > > -- So long, and thanks for all the fish.
_______________________________________________ Linux-il mailing list Linux-il@cs.huji.ac.il http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
