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

On 6 December 2006, the VDT team announced the release of VDT 1.5.2.

Highlights

• EDG-Make-Gridmap is now invoked in a way that preserves information from a VOMS server if it exists but cannot be contacted.
• vdt-startup and vdt-shutdown, which were added in VDT 1.5.1, have been coalesced into a single script, vdt-control. vdt-startup is equivalent to vdt-control --on and vdt-shutdown is equivalent to vdt-control --off. Also, the new script is much more careful about replacing existing system files, especially ones that do not seem to come from the current VDT. In some cases, vdt-control will not make system changes (and thus not enable the service in question) unless you specify the --force option.
• We have added the ability to copy some configuration from an old VDT installation on the same computer to your new installation. To use this, define $OLD_VDT_LOCATION before you begin your installation. It should be set to the full pathname of the old location for the VDT.
  Currently, we preserve configuration for GUMS, VOMS, and EDG-MakeGridmap. We chose to focus on these because they are the hardest for most people to preserve by hand: GUMS and VOMS have MySQL databases in addition to configuration files. As time permits, we will expand the configuration that we can preserve. If you have any components that you think we should address first, please let us know.
  • For GUMS, we can preserve configuration from VDT 1.3.9 and later
  • For VOMS, we can preserve configuration from VDT 1.3.7 and later
  • For EDG-Make-Gridmap, any version of the VDT
  Note that we also preserve the questions: your answers to all questions are copied from the old installation, and you are not asked any questions that you previously answered.
• Many questions asked by the VDT used to have three possible answers: y (yes), n (no), and s (skip). 'No' would uninstall any existing service that looked like the one that was being installed, so 's' was the answer most people normally wnated. This was confusing, so now there are only two answers, yes and no. After installation, no services are running, and you must start them up with vdt_control --on. When vdt-control tries to start up each service, it will refuse to start up a service if it appears that it's already running from a different installation (VDT or system-wide). You can force it to start it up by using the --force option.
• We have a new version of Globus with updated features from the Globus community branch. This is code shared with TeraGrid. It includes the new GRAM auditing features. They are turned off by default, and we don't yet have advice on how to use them. (Please see the known problems.)
• Patched the SGE jobmanager with patches from Jerome Lauret.

New Software

• Curl 7.16.0

Upgraded Software

• MonALISA 1.6.8
• PRIMA Authorization Module 0.5
• SRM V1 Client 1.25

Platforms No Longer Supported

After consulting with the VDT community about the need for supporting old platforms, we have dropped support for the following:

• RedHat 7
• RedHat 9

Known Problems

To learn more, you can view the main documentation page, documentation specific to VDT 1.5.2 or support tickets closed in VDT 1.5.2.

The VDT 1.5.2 cache is located at: http://vdt.cs.wisc.edu/vdt_152_cache