Note: If you installed the component using the RPMs, you must upgrade using RPMs as described in the OSG guides (see Frontend RPM installation, Factory RPM installation). This document refers to the TAR files installation.
General upgrade instructions for a Frontend
These instructions assume that you are only upgrading the Glidein Frontend. If you need to upgrade more components, it may involve additional steps.
- Back up your glideinwms (binaries/source) and frontstage (working directory) areas for the existing installation.
- Download the GlideinWMS tarball and replace the old version with it.
- Make sure you have correct HTCondor 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 (glideinwms, frontstage, frontend_Frontend_dir, instance_v3_0) may be slightly different in each case based on your 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 Glidein 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
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 GIT, git pull origin branch (or master) 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 v1+ or v2+ to v3+
We do not support upgrading from v1+ or v2+ to v3+. There are too many changes between these versions and reinstallation of ALL services is required.