Note: This version of the VDT (1.7.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 1.10.1.
VDT 1.7.1 Release
Release History
| Version |
Released On |
Notes |
| 1.7.1b |
24 August 2007 |
VOMRS security update |
| 1.7.1a |
16 July 2007 |
Bug fix in configure-gip, see below |
| 1.7.1 |
6 July 2007 |
Initial release |
Note: This is a development release, and it is is not as
well-tested or high-quality as our stable releases. Unless you have a strong
reason to do so, we recommend using VDT 1.8.0 or
later.
Updating from 1.7.1a to 1.7.1b
This is a development release of the VDT, so we have not tested updates for
this release. If you have installed VOMRS prior to this update, we strongly
recommend that you delete that old installation and start over, preferably
with a newer version of the VDT.
If you would like to risk your installation with an update, here are the
standard commands (not tested for this update):
cd VDT-1.7.1-LOCATION
. setup.sh
vdt-control --off
pacman -update VOMRS
vdt-control --on
Changes in VDT 1.7.1a
- A bug in configure-gip was fixed. The script will no longer die if a configuration file (osg-info-static-service.conf) does not exist.
Highlights of changes since 1.7.0
-
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. However, there are some
known problems with VOMS Admin.
-
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. There is no documentation yet. It’s a cron job that is
optionally enabled. We will write documentation for it by VDT 1.8.0.
New Software Since 1.7.0
- Bestman 2.2.0.1 (VDT Ticket 2764)
- Gratia Glexec Probe 0.25 (VDT Ticket 2761)
- Gratia Metric Probe 0.25
- Globus GRAM 4 (web services) support for SGE 1.1
(VDT Ticket 2762)
Please note that it has been added, but there are problems
preventing it from working. Details
- lcg-info 1.11.0-1 and
lcg-infosites 2.6-2 have
been added. These allow easy querying of a BDII.
- Pegasus 2.0.0 (VDT Ticket 2719)
Upgraded Software Since 1.7.0
Removed Software Since 1.7.0
Other Changes since 1.7.0
- Java 5 is now the default instead of Java 4, except for web
applications running in Tomcat 5.0. (VDT Ticket 2718)
- Squid was upgraded to version 2.6.13
(VDT Ticket 2710), and the configuration was tweaked a bit (VDT Ticket 2711)
- The Gratia PBS and LSF probe is now compiled on all supported
platforms. This should resolve problems people had when the
probe didn't work due to failed dynamic linking.
(VDT Ticket 2634) (VDT Ticket 2761)
- The configuration of the generic information provider has been
updated. (VDT Ticket 2763)
Learning More
To learn more, you can view
the main documentation page or
documentation specific to VDT 1.7.1.
Known Problems
The VDT 1.7.1 cache is located at:
http://vdt.cs.wisc.edu/vdt_171_cache
