Checklist for upgrading production servers to 2.8

Sites to be upgraded on damocles.met.no:

damocles (owns damocles_metadata and damocles_userbase)

dokipy

ipycoord

gcwdemo

Other sites:

arcticdata (separate server)

Phase 1. Preparation

Site configuration

This should ideally be setup via https://svn.met.no/projects/metamodapps/, but will take too long to figure out. Instead will use existing generated master_config as starting point and backmerge changes to svn later. Custom styles ignored at this point - must be added later.

Must be repeated for each site.

Metamod source

checkout to /metno/metamod/metamod28/trunk as root

chown to damocles (needed for building)

Phase 2. Setting up new database

Only done once.

Unresolved questions:

which xml files should be used to populate the DB?

/metno/metamod/damocles/webrun/XML/DAMOC ?

userdb data are not duplicated anywhere else

must dump 2.6 userdb and import into 2.8, then run upgradeuserdb_26-28.sh

metadatadb must probably be generated using createdb.sh

this means the Generate Target part of Phase 3 for site damocles must be executed first

Phase 3. Setting up prototype

This will setup a generic Metamod 2.8 instance to test the system is running. Customization will be done afterwards, and the installation re-run.

Must be repeated for each site.

Generate target

Test Catalyst

Remember each site must have its own dedicated port.

Apache configuration

This server uses DNS-based virtual hosting, however each site already has an existing setup in sites-available. This means the generated httpd.conf in target/etc cannot be used directly; instead you must manually copy & paste the new config into the old file. (Perhaps later when the 2.6 versions are turned off we could use the generated config files directly.)

Install services

Do not run install_jobs.sh; instead install links manually.

Phase 4. Adding custom functions and styling

Todo by someone else (have no idea what is required and how to implement it).

Must be repeated for each site.