Deployment Tutorial

From VCGR Wiki

Jump to: navigation, search

COMPLETE RE-INITIALIZATION

Dropping a new build and starting up the system in a clean state...an easy 10 step process!

STEP 1.1 - Starting

ssh into centurion060 using the gbg account

STEP 1.2 - Ant Build

>cd genesisII-build
>ant

This runs the buildfile. Note the buildnumber will be incremented but not the version number.

This step should take between 5 and 10 minutes.

STEP 1.3 - Merging Config Files

note that this step will not always be required

>cd conf-files
>diff <filename> ../Genesis\ II/<filename>

Check for any changes in these files in relation to the old files. Merge any security changes appropriately. Remember to look at any changes in comments.

STEP 1.4 - Cleaning State

>cd ../GeniiNet
>./net-clean-deployment.sh
>/bin/rm -f -r Genesis\ II GenesisII-installer-0.7.x.jar

We are stopping any existing net, cleaning all states, and deleting old files.

STEP 1.5 - Build Fresh Net

>java -jar ../genesisII-build/GenesisII-installer-0.7.x.jar ../installation-description.xml

STEP 1.6 - Initializing Fresh Net

>./initialize-security.sh
>./net-start-containers.sh

The first script creates/exports certificates, sets up the trust store, etc. The second script starts all containers on local disk. Will fail if container already up. It does not clean the state.

STEP 1.7 - Check Logs for Container Status

After running the script to start up all the containers in the net, you will need to wait a couple of minutes before you can check to see if they are up. You can do this by checking the logs for a successful start with no stack traces for each container. One way is to grep to see if the vital message appeared for each container:
>grep 'Container Started' logs/*

STEP 1.8 - Bootstrap

>./bootstrap.sh

This step should take around 40 minutes.

STEP 1.9 - Transfer Files

First we get the build number:
>cd Genesis\ II
>cat RELEASE

We create a new directory:
>ssh mamba.cs.virginia.edu -l vcgr
>cd public_html/genesisII/downloads
>mkdir Build_<BuildNumer>

Next we transfer the installer file:
>cd Build_<BuildNumer>
>scp gbg@centurion060:~/genesisII-build/GenesisII-installer-0.7.x.jar GenesisII-installer-0.7.3.jar

Finally we transfer the grid related files:
>cd ../Grids
>scp gbg@centurion060:~/GeniiNet/Genesis\\\ II/context.xml UVaContext.xml
>scp gbg@centurion060:~/GeniiNet/Genesis\\\ II/security/trusted.pfx trusted.pfx

STEP 1.10 - Update Website

Still in vcgr, cd into the genesisII directory.
>cd ../..

Open up downloads.html and update the release date, build number, etc.

LIVE FIX

Dropping a new build without destroying the system state...an easy 9 step process!

STEP 2.1 - Starting

ssh into centurion060 using the gbg account

STEP 2.2 - Ant Build

>cd genesisII-build
>ant

This runs the buildfile. Note the buildnumber will be incremented but not the version number.

This step should take between 5 and 10 minutes.

STEP 2.3 - Merging Config Files

note that this step will not always be required

>cd conf-files
>diff <filename> ../Genesis\ II/<filename>

Check for any changes in these files in relation to the old files. Merge any security changes appropriately. Remember to look at any changes in comments.

STEP 2.4 - Stop Containers

>cd ../GeniiNet
>./net-stop-containers.sh

We are stopping any existing containers (but NOT cleaning the state).

STEP 2.5 - Run Installer

>/bin/rm -f -r Genesis\ II GenesisII-installer-0.7.3.jar
>java -jar ../genesisII-build/GenesisII-installer-0.7.3.jar ../installation-description.xml

We are deleting old files and then installing the new net.

STEP 2.6 - Restart Containers

>./net-start-containers.sh

The script starts all containers on local disk. Will fail if container already up. It does not clean the state. Containers start in the state that exists.

STEP 2.7 - Check Logs

>cd logs
>cat <logfile> OR >tail -f <logfile>

Check for no stack traces and successful start.

STEP 2.8 - Transfer Files

First we get the build number:
>cd ../Genesis\ II
>cat RELEASE