Difference between revisions of "Monk upgrade"
BrettGiles (talk | contribs) (→Schedule: Add heading) |
(fleshing out a bit) |
||
Line 19: | Line 19: | ||
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... |
||
+ | |||
+ | === Apache === |
||
+ | Migration to version 2. Need to update server config, and .htaccess files. |
||
+ | |||
+ | Start using mod_python? --SimonM |
||
+ | |||
+ | === MySQL === |
||
+ | Nobody claimed to be using this. |
||
+ | |||
+ | === PostreSQL === |
||
+ | Nobody claimed to be using this. |
||
+ | |||
+ | === SQLite === |
||
+ | Used by Trac. I'm not sure whether the upgrade will require a dump/restore of the Trac dbs, we should look into this --SimonM. |
||
+ | |||
+ | === CVS === |
||
+ | Paul offerred to deal with this one. |
||
+ | |||
+ | === Trac === |
||
+ | It should be possible to upgrade Trac independently after the upgrade. If so, I think we should do that, in order to reduce dependencies and shorten the downtime. |
||
+ | |||
+ | === Darcs === |
||
+ | No upgrade required: we don't use the Debian-supplied version here. |
||
== Downtime plan == |
== Downtime plan == |
||
The downtime plan in as much detail as possible. |
The downtime plan in as much detail as possible. |
||
+ | |||
+ | We need to move /home to the /srv partition, as it is running out of space. |
||
===Schedule=== |
===Schedule=== |
||
Line 28: | Line 53: | ||
===Regression tests=== |
===Regression tests=== |
||
Preferably scripted, with "owner" who decides how to proceed in event of failure. |
Preferably scripted, with "owner" who decides how to proceed in event of failure. |
||
+ | |||
+ | Verify that we can |
||
+ | * use darcs, including remote push |
||
+ | * send external email (including darcs reports) |
||
+ | * use all the Tracs |
||
+ | * use darcsweb |
||
+ | * use Hackage |
||
+ | * use CVS |
||
===Rollback plan(s)=== |
===Rollback plan(s)=== |
Revision as of 07:49, 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...
Apache
Migration to version 2. Need to update server config, and .htaccess files.
Start using mod_python? --SimonM
MySQL
Nobody claimed to be using this.
PostreSQL
Nobody claimed to be using this.
SQLite
Used by Trac. I'm not sure whether the upgrade will require a dump/restore of the Trac dbs, we should look into this --SimonM.
CVS
Paul offerred to deal with this one.
Trac
It should be possible to upgrade Trac independently after the upgrade. If so, I think we should do that, in order to reduce dependencies and shorten the downtime.
Darcs
No upgrade required: we don't use the Debian-supplied version here.
Downtime plan
The downtime plan in as much detail as possible.
We need to move /home to the /srv partition, as it is running out of space.
Schedule
Regression tests
Preferably scripted, with "owner" who decides how to proceed in event of failure.
Verify that we can
- use darcs, including remote push
- send external email (including darcs reports)
- use all the Tracs
- use darcsweb
- use Hackage
- use CVS
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)