Note: This version of the VDT (1.3.3) 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.3.3 Release

We are pleased to announce the release of VDT 1.3.3.

New Features

• The DRM web services interface (SRM) is installed and configured. Users should note that it runs on ports 8081 and 8444 instead of the usual 8080 and 8443.

Bug Fixes

• The Globus log rotation cron job will no longer complain about compressoptions.
• EDG-MakeGridmap can now build grid-mapfiles from the VOMS server included with VDT 1.3.3.
• You no longer need to restart Apache and Tomcat after installing VOMS or jClarens.
• jClarens no longer creates extra directories in /home.
• The VDT will now install on an AFS file system.
• The configure_voms script can now be run after the installation to set up additional VOs.
• The Globus GRIS works properly again. This corrects serious bugs in VDT 1.3.1 and 1.3.2.

Upgraded Software

• Logrotate 3.7
• Apache 2.0.53
• jClarens Discovery Service 0.5.3
• PPDG Cert Scripts 1.5
• Fault Tolerant Shell 2.0.11
• UberFTTP 1.11
• Java 1.4.2_07
• Condor 6.7.6
• DRM 1.2.6a
• VOMS 1.4.0

New Software

• Condor 6.7.6 includes the Stork data placement scheduler.
• The Globus Simple CA is now included, but is not set up by default. It is officially part of the Globus distribution, so we don't separately version it.
• The Globus GridFTP server from Globus 3.9.5 is now available as an optional install (the package is named Globus-New-GridFTP-Server). It will run on a different port, 2812, than the default GridFTP server. Bill Allcock from the Globus Alliance says:
  Why use the new GridFTP server? From a protocol level, the servers are completely identical. Old clients can talk to new servers, new clients can talk to old servers, you can third party transfer between a new server and an old server, etc, so it is NOT mandatory that you upgrade. The real reasons for using the new server are more subtle. First, this code base has been subjected to a much higher level of testing than the previous server. We have successfully handled 1800 clients on a single host, we have achieved 90% utilization on a 30 Gbs link, we have had single file transfers that ran for a month. Second, bugs in the new server are our top priority, while bugs in the old server are very low priority. Third, documentation on the new server is significantly improved. Finally, the new server gives you additional flexibility. We are working on custom Data Storage Interfaces (DSI) to NeST, SRB, and HPSS. If you want to add custom functionality, there are clean interfaces in all the right places, so it should be relatively easy to do, where it is completely impractical with the old server.
  More information about GridFTP 3.9.5
• Nest version 0.9.7pre1 (the package is named Nest), from the Condor Project is now available as an optional install. It relies on the new Globus GridFTP server, and it modifies the install so that all incoming GridFTP requests to the new server will use Nest for all interaction with the disk. More information about Nest

Other Changes

• In VDT 1.2.0 we changed the xinetd configuration from running the Globus Gatekeeper and GridFTP servers directly to calling a small wrapper script. If you use TCP wrappers and are upgrading the VDT from a pre-1.2 release you will need to change the appropriate entries in /etc/hosts.allow and /etc/hosts.deny. More information can be found in our TCP wrappers documentation.
• All web services (Apache, Tomcat and DRM) now run as the daemon user. If you previously had an http service cert owned by nobody you'll need to chown it to daemon.
• Discovered that the VOMS server does not work on Debian Linux. We're working with the developers to fix this for a future VDT release. For now VOMS will not be included with an install on Debian.
• Discovered that the DRM does not work on Debian Linux. The VDT 1.3.3 install on Debian will not include DRM.

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

The VDT 1.3.3 cache is located at: http://vdt.cs.wisc.edu/vdt_133_cache