Difference between revisions of "Monk upgrade"
Jump to navigation
Jump to search
BrettGiles (talk | contribs) m (MonkUpgrade moved to Monk upgrade) |
BrettGiles (talk | contribs) (Heading case as per wiki standards) |
||
| Line 12: | Line 12: | ||
# Wider post-upgrade testing and observations |
# Wider post-upgrade testing and observations |
||
| − | == Application |
+ | == Application upgrades == |
Which crucial applications will be upgraded? |
Which crucial applications will be upgraded? |
||
| Line 20: | Line 20: | ||
MySQL, PostgreSQL, SQLite, BerkeleyDB -- which of them are in active use and candidates for upgrades? Their data stores will likely need a dump and restore... |
MySQL, PostgreSQL, SQLite, BerkeleyDB -- which of them are in active use and candidates for upgrades? Their data stores will likely need a dump and restore... |
||
| − | == Downtime |
+ | == Downtime plan == |
The downtime plan in as much detail as possible. |
The downtime plan in as much detail as possible. |
||
| − | Schedule |
+ | ===Schedule=== |
Regression tests -- preferably scripted, with "owner" who decides how to proceed in event of failure. |
Regression tests -- preferably scripted, with "owner" who decides how to proceed in event of failure. |
||
| − | Rollback plan(s) |
+ | ===Rollback plan(s)=== |
| − | == Post- |
+ | == Post-upgrade notes and observations == |
Anything we learned or observed that will be helpful as we move forward? |
Anything we learned or observed that will be helpful as we move forward? |
||
Revision as of 02:56, 26 June 2007
cvs.haskell.org (aka haskell.galois.com; aka monk) is in need of an OS upgrade. It's currently running Debian sarge; the upgrade will be to etch, the current stable version of Debian.
This page is meant to host discussion of
- Which crucial applications will be upgraded (with specific version numbers)?
- What config files will need tweaking?
- What binary data stores (e.g., database disk files) will need processing?
- The downtime plan
- Schedule
- Regression tests (including who will carry them out)
- Rollback plan(s)
- Wider post-upgrade testing and observations
Application upgrades
Which crucial applications will be upgraded?
Notes on re-configuration...
MySQL, PostgreSQL, SQLite, BerkeleyDB -- which of them are in active use and candidates for upgrades? Their data stores will likely need a dump and restore...
Downtime plan
The downtime plan in as much detail as possible.
Schedule
Regression tests -- preferably scripted, with "owner" who decides how to proceed in event of failure.
Rollback plan(s)
Post-upgrade notes and observations
Anything we learned or observed that will be helpful as we move forward?
Heinlein 19:04, 25 June 2007 (UTC)