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.1b Update

On 2007-11-01, the VDT team announced the release of VDT 1.8.1b.

Changes

  1. Updated Globus with three new patches. (VDT ticket 3049)
    IMPORTANT: When you follow the update procedure below, update Globus before other components.
    • Bug fix to GridFTP (VDT ticket 2989) (Globus ticket 5590)
    • Bug fix to job manager to properly find grid monitor state file
    • Removed OpenSSL algorithms that are patented (RC5 and IDEA). (Globus ticket 3689)
  2. Updated Java 1.4 and 1.5 to deal with a minor security issue. (VDT tickets 3029, 3030)
  3. Updated Tomcat 5.5 to 5.5.25 for a minor security issue. (VDT ticket 3035)
  4. Updated the Gratia Probes to version 0.27.5c.
  5. Minor bug fixes to Generic Information Provider (VDT tickets 2959, 3046, 3055)
  6. Updated GUMS to 1.2.10 to fix a couple minor issues in the automatic GIP insertion script and an apparent long-standing but rare bug (VDT tickets 3025, 3066)
  7. Updated Bestman, SRM V2 Client and SRM V2 Tester to version 2.2.0.4. (VDT ticket 3067)
  8. Added a new package, Unsup-Dccp. This is the dCache client, version 1.7.0-39. It is unsupported because it was added after the VDT 1.8.1 initial release and because it hasn’t been tested as part of the VDT’s pacman packaging. dCache is available separately from the VDT (more details) as RPMs, but this is intended for OSG to install on worker nodes.
  9. Updated the OSG RSV Probes.
  10. Updated Gratia-Services and Gratia-Reporting to 0.28. There is no “paman -update” available for this update.
  11. Updated Metronome to 2.4.3 (in NMI-Build-And-Test package). (VDT tickets 3017, 3044) There is no “pacman -update” for this update
  12. Tcl package change — won’t install Tcl if the system version is 8.4 or later. There is nothing to update here: this only affects fresh installations.
  13. Fixed a small bug for Globus-WS in which a non-root install could fail due to an unnecessary chown (note: because this fix is only relevant to new installs, there is no reason to update the package in an existing installation) (VDT ticket 3036)
  14. Added CentOS 5 as a supported platform for both x86 and x86-64. This means that we have CentOS 5 machines in our test pool, that we now run tests on those platforms nightly, and that tests are passing
  15. Added some new documentation and revised other documentation:

Updating to VDT 1.8.1b

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

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. Update Globus

There are four Globus packages to update. You only need to update the ones that you have installed. You know if it is installed if there is a file named $VDT_LOCATION/vdt/etc/package_data/PACKAGE-NAME.filelist. For example, to see if Globus-Base-Essentials is installed: 

> file $VDT_LOCATION/vdt/etc/package_data/Globus-Base-Essentials.filelist 
vdt/etc/package_data/Globus-Base-Essentials.filelist: ASCII text

1a. Update Globus-Base-Essentials

IMPORTANT: Globus-Base-Essentials must be updated before Globus-Base-Jobmanager-Common 

pacman -update Globus-Base-Essentials

1b. Update Globus-Base-Jobmanager-Common

rm -f globus/etc/globus_packages/setup/globus_gram_job_manager_setup/globus_gram_job_manager_setup.gpt 
rm -f globus/etc/globus_packages/setup/globus_gram_job_manager_service_setup/globus_gram_job_manager_setup_fork.gpt
pacman -update Globus-Base-Jobmanager-Common

1c. Update Globus-Base-Data-Server (GridFTP)

pacman -update Globus-Base-Data-Server

1d. Update Globus-Base-SDK

pacman -update Globus-Base-SDK

2. Updating Java

You only need to update Java 5 if you have $VDT_LOCATION/jdk1.5.

You only need to update Java 4 if you have $VDT_LOCATION/jdk1.4. 

pacman -update JDK-1.5
pacman -update JDK-1.4

3.Updating Tomcat 5.5

pacman -update Tomcat-5.5

If (and only if) you have installed the Gratia web services (Gratia-Reporting package), you need to update the VDT configuration script for Gratia and then use it to recreate some extra Tomcat configuration. 

pacman -update Configure-Gratia
. setup.sh
vdt/setup/configure_gratia --reporting

4. Updating Gratia-Probes

You just need to update the Gratia Probes that you have installed. If you are running an OSG site, you probably have one for your batch system and the "Metric" probe. Select the commands below that apply to the probes you have installed: 

# Select the batch system probe you have
pacman -update Gratia-Condor-Probe
pacman -update Gratia-LSF-Probe
pacman -update Gratia-PBS-Probe
pacman -update Gratia-SGE-Probe

# OSG sites probably need the Metric probe updated (for RSV)
pacman -update Gratia-Metric-Probe

# The glexec probe is only if you use glexec: most sites don’t yet
pacman -update Gratia-Glexe-Probe

5. Updating Generic Information Provider

pacman -update Generic-Information-Provider

Note: You should see two packages are updated with this one command: Generic-Information-Provider and Configure-GIP.

6. Updating GUMS

We recommend upating Tomcat before updating GUMS.

Unless you updated to GUMS 1.2.8a (in VDT 1.8.1a), you must remove a symbolic link before running the update, or else the update will overwrite your existing GUMS configuration file. If you are unsure, it is safe to remove the symlink in any case. 

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

In all cases, use pacman to perform the update itself: 

pacman -update GUMS

7a. Updating Bestman

pacman -update Bestman

7b. Updating SRM-V2-Tester

pacman -update SRM-V2-Tester

7c. Updating SRM-V2-Client

pacman -update SRM-V2-Client

8. Installing dccp

pacman -get http://vdt.cs.wisc.edu/vdt_181_cache:Unsup-Dccp

9. Updating OSG RSV Probes

pacman -update OSG-RSV-Probes