VDT 1.8.0 has been released.


Highlights of the new features since 1.6.1:

* Red Hat Enterprise Linux 5 is now supported.

* We are now using Globus 4.0.5. This release incorporates many (but not all) of the patches that we used to apply to Globus. In particular, it incorporates nearly all of the community branch (for TeraGrid) changes that we used apply as a set of patches. This change will make it easier to maintain our Globus build. Also, WS-GRAM received a number of fixes to improve reliability and scalability. You can see our patches to Globus. (VDT Ticket 2721)

* Java 5 is now the default instead of Java 4, except for web applications running in Tomcat 5.0. (VDT Ticket 2718)

* VOMS nows runs on 64-bit computers.

* For OSG installations, batch job managers (Condor, PBS, SGE, and LSF) will reset GLOBUS_LOCATION for jobs based on OSG_GRID. This allows GLOBUS_LOCATION to be different for the gatekeeper and the worker nodes. This has been tested on all platforms, but it might not be working on LSF – the current behavior on LSF seems to simply not change GLOBUS_LOCATION, so it is no worse than it used to be.

* There is now an RPM for installing the CA certificates. It has been lightly tested. If you want to use it, it’s best to tell the VDT not to install the CA certificates at all, and then just use the RPM.

* There is now a program, vdt-update-certs, for automatically updating the CA Certificates. It is a cron job that is optionally enabled.

* The way in which web applications are installed into Tomcat 5.0 and 5.5 is now more robust and more consistent with Tomcat best practices.

* Pacman 3.20 is now the minimum supported version of Pacman. It is substantially faster than previous versions of pacman, which makes a VDT install faster.

VDT Team