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)

Using gcwdemo as an example in code.

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.

cd /metno/metamod/metamod28/gcwdemo
sudo -u damocles mkdir app
sudo -u damocles cp /metno/metamod/gcwdemo/r1/master_config.txt app/

Postponed until Phase 5

cd /metno/metamod/metamod28
sudo svn co https://svn.met.no/metamod/trunk
sudo chown -R damocles.damocles trunk/ (needed for building)

Only done once.

Database setup requires scripts generated to target. This means the Generate Target part of Phase 3 for site damocles must be executed

• 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 from scratch using createdb.sh?
• which xml files should be used to populate the DB?
  • /metno/metamod/damocles/webrun/XML/DAMOC ? (see damocles/master_config)
  • run import_dataset.pl on files
    • anything else to think of? (if so, probably best Heiko did this)

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.

cd /metno/metamod/metamod28/gcwdemo
sudo -u catalyst ../trunk/update_target.pl app/

Remember each site must have its own dedicated port.

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.)

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

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

Must be repeated for each site.

— Geir Aalberg 2011/04/29 11:04