VDT logo
Search:

(Powered by Google)

Note: This version of the VDT (1.8.1) is no longer supported. Feel free to look through the documentation and install it, but we cannot guarantee support for it. The current stable release is 2.0.0.

VDT 1.8.1a Update

On 2007-10-08, the VDT team announced the release of VDT 1.8.1a.

Changes to VDT 1.8.1a

  1. Globus web-services GRAM (also known as GRAM 4) now properly supports SGE. (VDT ticket 2540)
  2. Updated glexec so it actually works. Previously, glexec didn’t work because it couldn’t find the shared libaries. (VDT ticket 2992)
  3. OSG-RSV improvements and bug fixes (VDT ticket 2979)
    • Added the ability to probe multiple hosts from a single machine
    • Allowed the use of a pre-existing Condor 6.9.x installation; set VDTSETUP_CONDOR_DEVEL_LOCATION before installing to do this
    • Added ability to serve RSV HTML status pages with Apache
    • Bug fix: prevents Gratia’s metric ProbeConfig file from resetting (Data|Working|Log)Folder variables when configure_gratia is run
    • Updated RSV probes to version 1.4.1
  4. The Generic Information Providers were updated to allow more customization and to fix some information. (VDT ticket 3006)
  5. Gratia probe configuration improvements:
    • When you install the Gratia probe for SGE, it configures the probe so that it can find SGE’s accounting file.
    • Fixed a bug in which pbsAcctLogDir was set incorrectly by configure_gratia in $VDT_LOCATION/gratia/probe/pbs/urCollector.conf (VDT ticket 2991)
  6. TclGlobus
    • Added the $VDT_LOCATION/tclglobus/lib directory to the LD_LIBRARY_PATH
    • Added the TclGlobus-Client package, which installs a smaller subset of Globus (VDT ticket 2973)
  7. Changed the Tomcat configuration to make the catalina.out file be readable only by the user who runs Tomcat. There was some concern about the contents of this log file, so we restricted who can view it. (VDT ticket 2972)
  8. Updated to GUMS 1.2.8a, which fixes a problem with gums-host-cron, among other things. Improved process for updating GUMS. Updating GUMS from VDT 1.8.1 to 1.8.1a will require one extra command; after that, normal updates should work fine. (VDT tickets 3002, 3007)
  9. Improved error handling and error messages in the GUMS configuration process when copying an old VDT GUMS configuration. Note: This change does not affect existing installations, so there is no need to update for this change. (VDT ticket 2988)

Updating to VDT 1.8.1a

If you installed VDT 1.8.1 after VDT 1.8.1a was released on 2007-10-08, you do not need to do any of these update operations because you will have 1.8.1a.

The best way to do the update is to update the individual packages that have changed. To be clear, we do not recommend using pacman -update without specifying specific package names. Also note that you only need to update packages if you installed them. You can see what packages have been installed with: 

pacman -l -d 1

Common update directions

Before you do the update directions that follow, please run the following commands. They apply for all of the updates. 

cp -pr $VDT_LOCATION BACKUP-LOCATION
cd $VDT_LOCATION
. setup.sh

The copy command makes a complete backup of your VDT installation, in case something goes wrong. Do not skip this step!

1. Updating Globus/SGE job interface

pacman -update Globus-SGE-Setup
cd globus/setup/globus
./setup-globus-job-manager-sge
cd $VDT_LOCATION

2. Updating glexec

pacman -update Glexec

3. Updating OSG-RSV

The OSG-RSV directory structure has changed significantly in this release. This results in a slightly more complicated upgrade. It will be necessary to preserve some of your configuration files if you have made changes, and move them to new locations. The steps to do some are listed below. 

# 1) Backup files (OPTIONAL)
# Backup what you would like to save first.  If you have not made changes to the
# defaults, you do not need to save any of this
cp osg-rsv/config/metrics.conf metrics.conf.bkup
cp -r osg-rsv/specs/probes specs.bkup

# 2) Update OSG-RSV
pacman -remove OSG-RSV
rm -fr osg-rsv
pacman -get http://vdt.cs.wisc.edu/vdt_181_cache:OSG-RSV

# 3) Restore files if you backed them up in step 1
# In the command below, substitute HOSTNAME for the host your are probing
mv metrics.conf.bkup osg-rsv/config/HOSTNAME_metrics.conf

# Overwrite the default spec files with any changes you have made
cp specs.bkup/* osg-rsv/specs/global-specs/ 
rm -fr specs.bkup

4. Updating Generic Information Provider

pacman -update Generic-Information-Provider

5. Updating Gratia Configuration

# Make sure SGE_ROOT (and SGE_CELL, if appropriate) are set correctly.
pacman -update Configure-Gratia
vdt/setup/configure_gratia --probe sge
For SGE configuration: 
# Make sure SGE_ROOT (and SGE_CELL, if appropriate) are set correctly.
pacman -update Configure-Gratia
vdt/setup/configure_gratia --probe sge
For PBS configuration: 
vdt/setup/configure_gratia --probe pbs

6. Updating TclGlobus

pacman -update TclGlobus
or: 
pacman -get http://vdt.cs.wisc.edu/vdt_181_cache:TclGlobus-Client
Please note that you do not need TclGlobus-Client if you have TclGlobus: it is a strict subset.

7. Update Tomcat for catalina.out file permissions

First, update the VDT configuration script for Tomcat: 

pacman -update Configure-Tomcat

Then, check to see which versions of Tomcat you have installed: 

% ls tomcat
v5  v55

Reconfigure each version of Tomcat that you have installed. You may need only one of the following two commands: 

./vdt/setup/configure_tomcat --version 5 --server y
./vdt/setup/configure_tomcat --version 55 --server y

8. Updating GUMS

Be sure to do the extra step of removing the config symlink before running the update, or else the update will overwrite your existing GUMS configuration file. 

unlink $VDT_LOCATION/tomcat/v55/webapps/gums/WEB-INF/config
pacman -update GUMS