Upgrading from v2+ to v3+
There is no way to upgrade from a v2+ to a v3+ version. We normally don't support major version upgrades and in this case there have been significant changes to the configuration files and content in the working directories. Please back up your configurations (they can be a reference for any customizations you have done) and reinstall all the services.
The same applies to upgrading from v1+ to v3+. There are too many changes between these versions and reinstallation of ALL services is required.
Upgrading 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.
Upgrading 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.