Upgrading to version 2.7
Starting in version 2.7, glideinWMS now is packaged as a set of
python modules. This means that the top-level directory
must be called "glideinwms" (case-sensitive). [Python module
organization is based on the directory name. Also, note that
symbolic links can get around this naming convention if needed but
are not recommended]. For the RPM, no action is needed.
The tarball will by default use this naming scheme from this version
onwards. Because of this, the source directory will necessarily
change. You will need to change the source directory in your
startup script (factory_startup or frontend_startup).
glideinWMS_dir='/PATH_TO_DIR/glideinwms'
It is also recommended (but not strictly required) that you set your PYTHONPATH to include the parent of the glideinwms directory. For instance, if your tarball is installed into /home/gfactory/v2.7/glideinwms, you can put:
export PYTHONPATH=$PYTHONPATH:/home/gfactory/v2.7into your factory.sh/frontend.sh (ini based installs) or into your profile.d (Q&A-based installs).
Upgrading from versions earlier than v2.5.3 to versions 2.5.3 or 2.5.4 only
Special steps need to be taken to upgrade a factory or frontend to v2.5.3 or v2.5.4. This does not apply to
any later versions.
NOTE: You only need to follow this procedure if you are upgrading in-place. If you are installing an entire
new factory or frontend, you can just follow the normal install procedure.
To upgrade the factory:
- Download this file: reconfig_glidein
- Replace the reconfig_glidein script in the glideinWMS/creation/ directory with the downloaded file.
- Follow the rest of the normal in-place upgrade procedure.
To upgrade the frontend:
- Download this file: reconfig_frontend
- Replace the reconfig_frontend script in the glideinWMS/creation/ directory with the downloaded file.
- Follow the rest of the normal in-place upgrade procedure.
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.
- 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_Frontenddir. this is the directory where you have frontend_startup script
- ./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 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.