On Thu, 2005-09-08 at 07:31 -0500, Les Mikesell wrote:
On Thu, 2005-09-08 at 07:11, Johnny Hughes wrote:
If you managed a set of servers running homegrown code that may or may not be sensitive to library and utility program versions, what steps would you use to keep a test server up to date, then after performing any needed application testing, to roll out the same changes to the production servers in various different locations? The object is to install exactly the updates you just tested in spite of any subsequent repository changes or out-of-sync mirrors.
You would run a local mirror that only had the updates you tested on it :)
Local to what?
Setup your own mirror and access it via ftp, http, nfs or whatever...
The production boxes are distributed but have good internet connectivity. The test box only has so-so internet connectivity. Isn't having to do that an admission that yum doesn't really do a good job of managing the packages you want on a box?
No, this is clearly an admission on your part that you don't know how yum works, or how to setup your own repo.
Don't the people writing package management tools actually manage any machines or understand that keeping them identical is desirable?
--jesse