OS upgrades
From GridPP Wiki
Revision as of 14:27, 11 September 2009 by Alessandra forti (Talk | contribs)
OS upgrade is one of the most disruptive for obvious reasons. It needs preparation, testing and planning.
Preparation
- Mirror the OS locally
- Create the appropriate kickstart environment
- Yum directories links
- Yum config files if needed
- Tftp directories and files
- If needed ask for a certificate and put it in the cvs/cfengine framework
- Mirror the middleware that goes with the new OS locally
- Add the new directories for the new OS to CVS
- Make a list of changes required during the transition
- Partition modifications
- Third parties packages
- Changes suggested OS release notes
- Changes suggested in middleware release notes
- Changes required by the expriments on their ID cards or elsewhere
- Changes suggested by other system administrators who already have gone through it (mailing lists, blogs, google)
- ....
- Modify kickstart to accomodate any changes planned
- Modify cfengine scripts to accomodate any changes planned
- Test all the changes on a test machine
- Minimum requirement that it installs but test as much functionality as possible considering it is not in production
- Each service that requires an upgrade will need to be tested, i.e. testing WN can be installed is not enough if a CE needs to be upgraded as well