# GlideinWMS The Glidein-based Workflow Management System

- Home
- Download
- Glidein Frontend
- Corral Frontend
- WMS Factory
- Components
- FAQ

Loading

## Search Results

## GlideinWMS

- Overview
- Download
- Documentation
- Install
- History
- License

### Upgrade Guide

Jump to:

1. Upgrade from v2.x
2. Upgrade from v1.6
3. Upgrade from v1.6

Related Links:

- Installation Overview

### Upgrading frontend from Version 2.x

These instructions assume that you are only upgrading the frontend. If you need to upgrade more components, it may involve additional steps.

1. Back up your glideinWMS (binaries/source), frontstage area for the existing installation.
2. Download the glideinWMS tarball and replace the old version with it.
3. Make sure you have correct condor in your path. This is important!
4. cd frontstage/frontend_Frontenddir. this is the directory where you have frontend_startup script
5. ./frontend_startup upgrade ../instance_v1_0.cfg/frontend.xml

Note that the path name (instance_v1_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. For v2.4 to v2.4.x, there are not many changes to frontend.xml.

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.

### Upgrading from Version 1.6 and older

No upgrading instructions exist for this version. You will need to re-install glideinWMS and transfer your configuration specific changes over into the new installation.

### Upgrading a factory to a new version of glideinWMS

Upgrading a factory configuration tree to a new version of glideinWMS can be done in two ways:

- Installing the new glideinWMS code in a separate directory, and create a new configuration tree as explained above.
  The configuration file (glideinWMS.xml) of the existing configuration tree can 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. Warning: Check the revision history before doing this. Not all versions are compatible.

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.