[Yum] Package management strategy with yum

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I'm interested in how you guys would approach this problem.

Say I have two webserver clusters.  One www.foo.com and one for 
www.bar.com.  Each with say 3 webservers and an app server. How would 
you go about:

1.) Upgrading a package across all webservers? (say an apache security fix)

2.) Upgrading a package on only the www.bar.com webservers? (say I want 
to test out a new apache version on one first)

3.) Upgrade a package (say the kernel) on all www.bar.com servers, but 
no www.foo.com servers.

Basically what I want to be able to do is have an overlapping group 
structure so that I can granularly decide to update a package on 
"machines in the foo group that are also in the webservers group".

thanks,
jim

[Index of Archives]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux