Note: This version of the VDT (1.3.7) 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 1.10.1.

VDT 1.3.7 Release

We are pleased to announce the release of VDT 1.3.7.

New Supported Platforms

• Fedora Core 4. Note: SELinux must be disabled
• RedHat Enterprise Linux 4 Advanced Server

New Features

• vdt-rotate-globus-logs has been replaced by vdt-rotate-logs, which rotates logs from all VDT packages. Finding unbounded logs is difficult so if you see any that aren't rotated please let us know.
• You can now remove VOs with configure_voms
• You can now set a MySQL root password with configure_mysql
• MySQL is now built with SSL support
• The GT4 webservices-bases GRAM, RFT and MDS services are now included, along with VDT configuration scripts to simplify setup.

New Software

• Globus 4.0.1 web services are now included.
• Clarens 0.7.2 and the JobMon service 0.2
• gLite CE Monitor 1.0.2 for all platforms except Debian and RedHat 7.
• SRM Tester for all platforms except ROCKS. (SRM Tester is a subset of DRM that can be used to test an SRM installation, but it doesn't require all of DRM to be installed.)
• DRM is now included on Debian Linux.

New Documentation

• We've started documenting some aspects of the VDT that most users won't care about, but some will care very much about. These are in our technical notes.
• When we learned how to submit jobs to the new web services GRAM, we learned about a few differences from submitting jobs to the pre-web services GRAM. We documented a few details of how to submit jobs to WS GRAM.

Bug Fixes

• John Weigand noticed that the EDG-CRL-Update utilities were missing from several component installs. They are now included in all the appropriate spots.
• The MonaLisa configuration script has been rewritten in order to fix several longstanding problems and help preserve configuration across VDT upgrades. By default, it now takes parameters on the command line. If you want the old-style interactive prompts you must call it with --prompt.
• $GLOBUS_LOCATION/tmp is now sticky world-writable. This simplifies GT4 GRAM installation, and is needed for other software. See VDT Support Ticket #829.
• Fixed a typo in the Condor configuration which resulted in the grid monitor not being used.
• Condor will now start up properly if you answer 'yes' to the Condor question.
• inetd/xinetd will be restarted if you answer 'yes' to the Globus gatekeeper question.
• MySQL now properly ignores the global /etc/my.cnf configuration file.
• Previously, Tomcat was configured to listen on the main network interface. This has been changed to localhost. Since access to Tomcat hosted services (GUMS, VOMS, jClarens) is done through a local Apache proxy this should not effect any users.
• A bug in the gpt-update utility has been fixed, but as it's deprecated users should transition to gpt-install.

Upgraded Software

• Clarens 0.7.2
• Condor/Condor-G 6.7.12
• DRM 1.2.9
• Globus Toolkit, pre web-services 4.0.1
• GSI-Enabled OpenSSH 3.5
• GUMS 1.1.0
• Java SDK 1.4.2_08
• jClarens 0.6.0
• jClarens Web Service Registry 0.6.0
• Monalisa 1.2.46
• MyProxy 2.2
• MySQL 4.0.25
• PyGlobus gt4.0.1-1.13
• UberFTP 1.15
• Virtual Data System 1.4.1
• VOMS 1.6.7
• VOMS Admin (client 1.0.7, interface 1.0.2, server 1.1.2) 1.1.0-r0

Other Changes

• Pacman 3.14 is required to install VDT 1.3.7.
• We have switched the VDT cache from Pacman 2 to Pacman 3 syntax. While this is mostly under the hood, it will change the output pacman gives during a successful install or errors. Please let us know if you have any questions.
• The Condor and Globus-Condor-Setup packages have been removed from VDT-Gatekeeper. From now on, VDT-Gatekeeper will provide a complete gatekeeper install on a machine that already has a batch system set up and configured, or you can install these after installing VDT-Gatekeeper.
• Incorporated updates to the generic information provider to benefit Open Science Grid. In particular, the batch system information now includes per-VO information, and there is an OSG-specific configuration file that is included. To go along with this change the GLUE schema has been slightly extended with the GlueHostApplicationSoftwareLocation attribute.
• VOMS – both client and server – will not install on RedHat 7. Due to a last minute compilation problems with VOMS, we were unable to provide it for this platform. Previously, VOMS Admin did not work on RedHat 7, and hence we did not support VOMS Admin or the VOMS server there. If you need the VOMS client to work on RedHat 7, please let us know, or we may drop support for it on RedHat 7 permanently.
• The Globus-New-GridFTP-Server package has been removed, as it is part of Globus 4.0.1.
• In order to not interfere with pre-existing servers, MySQL will no longer use the default port (3306) and socket (/tmp/mysql.sock). Instead, a random port will be picked at install time (recorded in vdt/etc/mysql.vars) and the socket moved to vdt-app-data/mysql/var/mysql.sock. Configuration for VDT daemons has been updated to reflect this change, but you may need to reconfigure any external clients and servers that access the VDT MySQL database.
• In upgrading VOMS Admin to a recent gLite version, the VOMS Admin files moved from the $VDT_LOCATION/voms directory to a new $VDT_LOCATION/glite directory. VOMS itself is still installed in $VDT_LOCATION/voms.
• In order to work with as many systems as possible, the PyGlobus package is now built at install time. The Python package provided by the VDT will only be used if your local python package is incomplete (usually missing the python-devel package) or too old (PyGlobus only supported Python 2.x). Because this adds a significant amount of time to the install, the PyGlobus package was removed from VDT-Client.

To learn more, you can look at the main documentation page or documentation specific to VDT 1.3.7.

The VDT 1.3.7 cache is located at: http://www.cs.wisc.edu/vdt/vdt_137_cache