General upgrade instructions for a frontend
These instructions assume that you are only upgrading the frontend. If you need to upgrade more components, it may involve additional steps.
- Back up your glideinWMS (binaries/source), frontstage area for the existing installation.
- Download the glideinWMS tarball and replace the old version with it.
- Make sure you have correct condor in your path. This is important!
- cd frontstage/frontend_Frontend_dir. this is the directory where you have frontend_startup script
- ./frontend_startup upgrade ../instance_v3_0.cfg/frontend.xml
Note that the path names (instance_v3_0) may be slightly different in each case based on existing configuration.
In case you have done any special configuration to glideinWMS/creation/web_base/condor_vars.lst, you need to
redo them for the existing code base.
Alternatively, you can also try backing up files, untar-ing the new version, then copy the instance directory to the new version. Make the required changes and run create_frontend to reconfigure. Then, follow the post-installation tasks in the manual.
Warning: Check the revision history before doing this. Not all versions are compatible.
General upgrade instructions for a factory
These instructions assume that you are only upgrading the factory. If you need to upgrade more components, it may involve additional steps. Upgrading a factory can be done in two ways:
- Installing the new glideinWMS code in a separate directory, and create a new configuration
tree.
The configuration file (glieinWMS.xml) of the existing configuration tree may be used as a base for the new one; only the glidein_ name needs to be changed. See the configuration page for more defaults. - Overwrite the glideinWMS installation and run: factory_startup upgrade config.xml.
If getting the code from CVS, a cvs update -r version will update the code.
Running 'upgrade' overwrites all files in the glidein submit directories including rewriting the configuration file. If you use 'reconfig', this will only upgrade the files with factory configuration information so some of the scripts may not get updated.
Which option you choose is really up to you; the second one is easier, but the first one is cleaner and easier to revert back.
Warning: Check the revision history before doing this. Not all versions are compatible. For example, changes to a factory configuration file may not allow you to reuse an old glideinWMS.xml.
Upgrading from v2+ to v3+
We normally don't recommend major version upgrades as there are
significant changes to the configuration files and content in the working
directories.
Starting v3.1, glideinwms provides tools to convert v2.7 config files and
rrds to v3.1 equivalent. See below for detailed steps to upgrade factory
and frontend.
prompt$ ./convert_frontend_2to3.sh
Usage: convert_frontend_2to3.sh <options>
where <options> are:
-s <path> : path to top directory glideinWMS source
-i <frontend-2.xml> : v2 frontend.xml
-o <frontend-3.xml> : v3 frontend.xml
prompt$ ./convert_factory_2to3.sh
Usage: convert_factory_2to3.sh <options>
where <options> are:
-s <path> : path to top directory glideinWMS source
-i <glideinWMS-2.xml> : v2 glideinWMS.xml
-o <glideinWMS-3.xml> : v3 glideinWMS.xml
prompt$ ./convert_factory_rrds_2to3.sh
Usage: convert_factory_rrds_2to3.sh <options>
where <options> are:
-c <glideinWMS.xml> : full path to the v3 glideinWMS config file
The upgrade process is not fully automated and involves few steps. NOTE: Please back up your configurations (they can be a reference for any customizations you have done) when reinstalling the services.
#################################
# UPGRADING FACTORY v2.7+ to v3.1
#################################
# STEP 1: Stop the v2 factory service
# STEP 2: Install glideinwms v3.1
# STEP 3: Backup and Convert v2 config and rrds to v3
# STEP 4: Run factory_startup with upgrade option
# STEP 5: Start the factory service
# GLIDEINWMS from TARBALL/GIT, assuming following
# Glideinwms SRC_DIR=/opt/glideinwms
# Factory WORK_DIR=/home/factory/glideinsubmit/glidein_v1_0
# Factory CONFIG_DIR=/home/factory/glideinsubmit/glidein_v1_0.cfg
prompt$ cd $WORK_DIR
prompt$ ./factory_startup stop
prompt$ tar xzf -C $SRC_DIR /tmp/glideinwms_v3_1.tgz
prompt$ cp $WORK_DIR/glideinWMS.xml $WORK_DIR/glideinWMS-2.xml
prompt$ cp $CONFIG_DIR/glideinWMS.xml $CONFIG_DIR/glideinWMS-2.xml
prompt$ $SRC_DIR/factory/tools/convert_factory_2to3.sh -i $WORK_DIR/glideinWMS-2.xml -o $WORK_DIR/glideinWMS.xml -s $SRC_DIR
prompt$ $SRC_DIR/factory/tools/convert_factory_2to3.sh -i $CONFIG_DIR/glideinWMS-2.xml -o $CONFIG_DIR/glideinWMS.xml -s $SRC_DIR
prompt$ $SRC_DIR/factory/tools/convert_factory_rrds_2to3.sh -c $CONFIG_DIR/glideinWMS.xml
prompt$ ./factory_startup upgrade
prompt$ ./factory_startup start
# GLIDEINWMS from RPM, assuming following
# Glideinwms SRC_DIR=/usr/lib/python2.4/site-packages/glideinwms
# Factory WORK_DIR=/var/lib/gwms-factory/work-dir
# Factory CONFIG_DIR=/etc/gwms-factory
prompt$ service gwms-factory stop
prompt$ rpm -Uvh <glideinwms rpm>
prompt$ cp $WORK_DIR/glideinWMS.xml $WORK_DIR/glideinWMS-2.xml
prompt$ cp $CONFIG_DIR/glideinWMS.xml $CONFIG_DIR/glideinWMS-2.xml
prompt$ $SRC_DIR/factory/tools/convert_factory_2to3.sh -i $WORK_DIR/glideinWMS-2.xml -o $WORK_DIR/glideinWMS.xml -s $SRC_DIR
prompt$ $SRC_DIR/factory/tools/convert_factory_2to3.sh -i $CONFIG_DIR/glideinWMS-2.xml -o $CONFIG_DIR/glideinWMS.xml -s $SRC_DIR
prompt$ $SRC_DIR/factory/tools/convert_factory_rrds_2to3.sh -c $CONFIG_DIR/glideinWMS.xml
prompt$ service gwms-factory upgrade
prompt$ service gwms-factory start
##################################
# UPGRADING FRONTEND v2.7+ to v3.1
##################################
# STEP 1: Stop the v2 frontend service
# STEP 2: Install glideinwms v3.1
# STEP 3: Backup and Convert v2 config to v3
# STEP 4: Run frontend_startup with upgrade option
# STEP 5: Start the frontend service
# GLIDEINWMS from TARBALL/GIT, assuming following
# Glideinwms SRC_DIR=/opt/glideinwms
# Frontend WORK_DIR=/home/frontend/frontstage/frontend_myfrontend
# Frontend CONFIG_DIR=/home/frontend/frontstage/instance.cfg
prompt$ cd $WORK_DIR
prompt$ ./frontend_startup stop
prompt$ tar xzf -C $SRC_DIR /tmp/glideinwms_v3_1.tgz
prompt$ cp $WORK_DIR/frontend.xml $WORK_DIR/frontend-2.xml
prompt$ cp $CONFIG_DIR/frontend.xml $CONFIG_DIR/frontend-2.xml
prompt$ $SRC_DIR/frontend/tools/convert_frontend_2to3.sh -i $WORK_DIR/frontend-2.xml -o $WORK_DIR/frontend.xml -s $SRC_DIR
prompt$ $SRC_DIR/frontend/tools/convert_frontend_2to3.sh -i $CONFIG_DIR/frontend-2.xml -o $CONFIG_DIR/frontend.xml -s $SRC_DIR
prompt$ ./frontend_startup upgrade
prompt$ ./frontend_startup start
# GLIDEINWMS from RPM, assuming following
# Glideinwms SRC_DIR=/usr/lib/python2.4/site-packages/glideinwms
# Frontend WORK_DIR=/var/lib/gwms-frontend/vofrontend
# Frontend CONFIG_DIR=/etc/gwms-frontend
prompt$ service gwms-frontend stop
prompt$ rpm -Uvh <glideinwms rpm>
prompt$ cp $WORK_DIR/frontend.xml $WORK_DIR/frontend-2.xml
prompt$ cp $CONFIG_DIR/frontend.xml $CONFIG_DIR/frontend-2.xml
prompt$ $SRC_DIR/frontend/tools/convert_frontend_2to3.sh -i $WORK_DIR/frontend-2.xml -o $WORK_DIR/frontend.xml -s $SRC_DIR
prompt$ $SRC_DIR/frontend/tools/convert_frontend_2to3.sh -i $CONFIG_DIR/frontend-2.xml -o $CONFIG_DIR/frontend.xml -s $SRC_DIR
prompt$ service gwms-frontend upgrade
prompt$ service gwms-frontend start
Upgrading from v1+ to v3+
We do not support upgrading from v1+ to v3+. There are too many changes between these versions and reinstallation of ALL services is required.