I think a local mirror is really your best option. Or possibly two repos. One for testing, which you sync when you want to test updates and point all test systems at it. Then a production repo for production systems that pulls from the frozen test repo. One addition to your idea would be to use git. That way all you have to do is a 'git push' when you want to update your production repo. Could then use other features in git for tracking changes, possible reverts and such.
- Trey On Sep 21, 2011 10:14 PM, "Aleksey Tsalolikhin" atsaloli.tech@gmail.com wrote:
Hello,
Let's say your operating policy is "no patch updates without testing first in the test environment". Let's say it takes you 3 weeks to test. Over the course of the 3 weeks, the repo changes (new packages added, old removed).
Is there a way to "freeze" a set of packages so that when I run "yum update" on a Prod server it'll get the same package and patch set as the Test server did 3 weeks ago?
It's been suggested to maintain a local mirror, and take rsync snapshots of it daily, so then you can point the end node to a particular repository.
What other solutions are there?
Best, -at _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos