Note: This version of the VDT (1.9.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.9.1 Release

On 2008-04-02, the VDT team announced the release of VDT 1.9.1.

Upgraded Software Since 1.9.0

Software	Ticket (if applicable)
glexec-osg 0.2 (glexec 0.5.23.3, lcas 1.3.7.1 and lcmaps 1.4.3.1) 0.5.2	(VDT ticket 3415)
Globus Toolkit, pre web-services 4.0.7
Globus Toolkit, web-services 4.0.7
OSG Resource and Service Validation (RSV) 2.1.0
OSG Resource and Service Validation (RSV) Probes 2.1.0

Bug Fixes Since 1.9.0

The URL given when asking the question about where CA certificate should be installed was incorrect. It is now correct.
The vdt-update-certs script will now error out if the directory CERTS_DIRECTORY/certificates is a directory and not a symlink. This script requires that this location is a symlink to work properly, and will record an error if it is not. (CERTS_DIRECTORY is the directory pointed at by $VDT_LOCATION/globus/TRUSTED_CA). (VDT ticket 3390)
VOMS now works on x86-64 SLES 9. (VDT ticket 3401)
Picked up the correct version of our pre-compiled Perl modules on x86-64 SLES 9. (VDT ticket 3340)
The Condor NFS lite job manager now works with WSGRAM. (VDT ticket 3411)
We now tell Tomcat to set Java's maximum PermGen memory to be larger, to avoid running out of PermGen memory. (VDT ticket 3419)
Improved how we track what files are installed by Globus, so they can be removed. This should improve our ability to have smooth updates for Globus components. (VDT ticket 3102)
The SGE job manager now works with rotated log files.
Fixed a bug in the Condor job manager where it would interpret aborted jobs as successful. (VDT ticket 3406)

Other Changes since 1.9.0

CA Certificates are now initially installed using the vdt-update-certs script. We have removed the CA-Certificates-Base package from the cache. (VDT ticket 3405)
Condor-Devel has been replaced with Condor-Cron to better reflect the current use of the package. Condor-Cron has been simplified to support only the subset necessary to run "cron-like" jobs. Users requiring a full batch system or grid computing capabilities should continue to use the Condor package. (VDT ticket 3410)

The affects OSG sites using RSV. The upshot for you is that Condor-Cron is always installed, and you cannot use your pre-installed Condor instead of Condor-Cron. This keeps RSV jobs separate from your production jobs: you can stop or restart RSV jobs without affecting your production jobs. Also, we've provided wrappers for Condor commands specific to Condor-Cron. For example, you can see RSV jobs with condor_cron_q.
There is a new script called ca-certs-status to help you understand the state of the CA certificates installation. For example:
```
# ca-certs-status 

CA-Certificates Info:
Version: 35-1
vdt-update-certs last run: 2008-04-02T13-22-15
```
It will give a warning if it hasn't been run in a while:
```
# ca-certs-status 

CA-Certificates Info:
Version: 35-1
vdt-update-certs last run: 2008-03-31T16-55-35
WARNING: vdt-update-certs has not run in over 24 hours
```
Future versions of this script will also give information about the CA CRLs.
We added a check to our prereq script to detect if a system has SELinux enabled. There are known issues when attempting to install/execute the VDT with SELinux enabled, so we now will print a warning near the beginning of the install.
The configure_osg_rsv script has moved from $VDT_LOCATION/vdt/setup to $VDT_LOCATION/osg-rsv/setup. We have created a symlink in the old directory to help avoid confusion.
Made the vdt-install.log file be readable only by the installing user, in case the log file contains sensitive data. (VDT ticket 3215)
Added --enable and --disable options to vdt-control, which allow a user to set the desired state of one or more services without having to run a separate command (vdt-register-service). (VDT ticket 3412)

Learning More

To learn more, you can view the main documentation page or documentation specific to VDT 1.9.1.

Known Problems

The VDT 1.9.1 cache is located at: http://vdt.cs.wisc.edu/vdt_191_cache