Difference between revisions of "Monk upgrade"

From HaskellWiki
Jump to: navigation, search
m (MonkUpgrade moved to Monk upgrade)
(Heading case as per wiki standards)
Line 12: Line 12:
 
# Wider post-upgrade testing and observations
 
# Wider post-upgrade testing and observations
   
== Application Upgrades ==
+
== 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 Plan ==
+
== 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-Upgrade Notes and Observations ==
+
== 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

  1. Which crucial applications will be upgraded (with specific version numbers)?
    1. What config files will need tweaking?
    2. What binary data stores (e.g., database disk files) will need processing?
  2. The downtime plan
    1. Schedule
    2. Regression tests (including who will carry them out)
    3. Rollback plan(s)
  3. 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)