On Wed, 2005-09-07 at 23:56, David Johnston 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?
I would use yum to keep the testing system up to date, and use rsync to copy specific RPM packages to the production server.
That's pretty painful when the production servers have better connectivity to the internet than to the test location.
I would not install yum on the production server at all if you need to control things tightly.
Hmmm... that's not very complimentary of yum's capability. I'd really rather not need to know every single version number myself - just that they are all the same as had been tested.