SA1 Release Procedure

1. Agree with Netops about the aliases swaps and time of intervention (preferably "on-call")

Server

1. P: perform the database backup
2. P: stop the service (sync with repository)
3. reconfigue the RC (sh configure.sh server)
4. import database (etics + NMI)

Repository

1. P: perform the database backup
2. P: stop the service (sync with server)
   1. service tomcat5 stop
   2. startShutdown
3. reconfigue the RC (sh configure.sh repository)
4. drop database, create database
5. import database
6. attach the correct /home/repository (clean) and 'datastore' (linked)
7. start service

Who does what?

• A. Resco: Decides when is a good time for the release and let us know. Do not announce yet. The best would be Thursday lunch time

• A.Di Meglio: Prepares the Release notes and announcement.

• A.Aimar:; Announces it at the EMT and ask agreement

• A. Resco: Announces the down-time if the EMT agrees.

• A. Resco(and Lorenzo if needed): Executed the release and migrations

• All: Test the new production with the few tests from web app and

• A. Resco: Announce that the service is back

-- MarianZUREK - 11 Jun 2009