Note: This web site is only kept up to date for OSG Software
1.2 (VDT 2.0.0). If you are looking for information for the most recent
release, the RPM-based OSG Software 3.0, please see
the OSG documentation web site
Note: This version of the VDT (1.3.10) 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.10d Release
We are pleased to announce the release of VDT 1.3.10. (08-March-2006)
VDT 1.3.10a was released on 16-March-2006.
VDT 1.3.10b was released on 06-April-2006.
VDT 1.3.10c was released on 10-October-2006.
Changes from VDT 1.3.10c to VDT 1.3.10d
Changes from VDT 1.3.10b to VDT 1.3.10c
Changes from VDT 1.3.10a to VDT 1.3.10b
- Condor was upgraded to Condor 6.7.18 for a security fix.
- During installation, the gridftp.log file is created, so
monitoring system aren't confused by a non-existent file.
- vdt-change-user was fixed to set secondary group memberships
properly.
- The
Globus-Updates package was added.
- The
VDT-Client package now includes
Globus-WS-Client (the Globus web service client tools).
Changes from VDT 1.3.10 to VDT 1.3.10a
- Removed a hard-coded, incorrect pathname from the managed fork jobmanager
that prevented it from working outside of the VDT facility
- Fixed a bug that prevented the managed fork job manager from
recognizing a pre-existing Condor installation.
- Added a new environment variables (VOMS_USERCONF) so
voms-proxy-init can find the vomses file that is in the
VDT_LOCATION.
- Added an extra configuration variable to Condor to work around a
bug in Condor 6.7.17.
New Features
- Changed Globus's Condor jobmanager to use a Condor job log per job instead
of one job log for all jobs. This affects only pre-web services GRAM. This
is a patch to our Globus build. See 65__prewsgram_multi_condor_log.diff
at VDT 1.3.10 patches and
Globus
bugzilla ticket #4199
- Added a feature to Globus's pre-web services jobmanager to allow system
administrators to reject jobs that request streaming output, which can cause
high load on the gatekeeper. This is a patch to our Globus build. See
66__disable_streaming.diff at VDT 1.3.10
patches and
Globus
bugzilla ticket #4213
- Because the Generic Information Provider was updated along with our
corresponding configure_gip script, lcg-info-generic-config has been removed
and you no longer need to run it.
- We now configure the jClarens VOMS publisher properly
(vdt-support #1348)
- We have added a way to run Globus within Tomcat and therefore to use the
default web services port number (8443). Because this change happened after
the VDT code freeze, it is not done by default and is considered
unsupported. It is also a bit of a pain to do; we intend to simplify it in a
future VDT release. You can see
details for getting this to
work
New Software
- There is a now a managed
fork jobmanager based on Condor that allows you control jobs submitted
to the fork jobmanager
Upgraded Software
- Apache HTTPD 2.2.0
- Condor/Condor-G 6.7.18
- DRM 1.2.10
- Generic Information Provider 1.0.15 (Iowa 15-Feb-2006)
- GSI-Enabled OpenSSH 3.6
- jClarens Discovery Services registration scripts 20060206
- MonALISA 1.4.12
- MyProxy 3.4
- UberFTP 1.18
- Virtual Data System 1.4.4
- VOMS 1.6.10.2
Bug Fixes
- Added code to the installation framework to help ensure that files and
directories have secure ownership and permissions. By default, nothing
should be writable by group or other; exceptions are made on a per-package
basis as needed. Our test framework now includes a second, tighter check for
correct permissions in addition to the ownership checks already there. There
is a VDT security advisory
concerning this issue.
- Improved a rewrite rule in Apache so that older VOMS Admin URLs work
correctly from both the web browser and edg-mkgridmap
(vdt-support #1474)
- Fixed configure_voms so that it starts only the VO that is being
configured when starting the VOMS service
(vdt-support #1476)
- Fixed the VOMS startup script to continue starting VOs after hitting a VO
that is already started (vdt-support
#1476)
- Fixed the VOMS startup script to use vdt-change-user instead of su, which
fixes a problem that can prevent VOMS from starting up at boot time on
operating systems like RHEL4
(vdt-support #1475)
- Applied several patches (from John Weigand) to edg-crl-upgraded to fix
problems that included the daemon dying when it was not supposed to
(vdt-support #1446)
- Fixed the MySQL init script so that it shuts down properly when non-root
(vdt-support #1469)
- The configure_mds script was broken in the last few version of the VDT,
and the -secure option did not correctly turn on authentication. This has
been fixed.
- Init scripts are set up to start/stop in the proper order on SuSE
Linux
- The GRIS configuration no longer relies on the deprecated GRAM reporter
(vdt-support #1096)
- MonALISA VO modules no longer send debugging emails
(vdt-support #1207)
- Improved configure_monalisa's creation of the MonALISA configuration. If
configure_monalisa is run more than once, it no longer saves old settings as
comments (vdt-support #1456)
- Installing Condor will now install Java; this ensures that submissions to
web-services Globus will work, because Condor uses Java to do the
submission
- Moved functionality that patches a Globus file for the Condor jobmanager
so that it is installed correctly for both pre-web and web services
GRAM
- Fixed Globus's Condor jobmanager to get rid of a small bug that caused
some inefficiency (vdt-support
#1437)
- MonALISA'S MLD daemon no longer fails at boot-time on RHEL 4 when using
the daemon user (it appeared as an ssh-keygen prompt); for curious users, we
switched from using su to using vdt-change-user
(vdt-support #1367)
- MonALISA will now work with sites that use a pre-existing Condor install,
provided that
HISTORY is set to $(SPOOL)/history
(the default) in the Condor config file
- If you elect to install CA certificates in
/etc/grid-security/certificates, $GRID_SECURITY_DIR will be set to
/etc/grid-security; it will still be set to $VDT_LOCATION/globus/etc for
local CA certificate installs
(vdt-support #1218)
- You will no longer see permission denied warnings from bash when starting
services (vdt-support #1229)
- Fixed a bug that caused harmless but annoying error messages in the GRAM
jobmanager logs (vdt-support
#1502)
- Patched Globus to fix a bug in the Reliable File Transfer (RFT) service
that caused failures if there was a long time (usually eight hours) between
job submissions. This is a patch to our Globus build. See
67__rft_disconnect.diff at VDT 1.3.10 patches
and
Globus bugzilla ticket #3685
- Added a temp directory to Tomcat 5, to ensure that jClarens runs correctly
(vdt-support #1431)
Other Changes
- Support for installing a 32-bit version of the VDT on x86-64 architectures
has been improved and should work much better. If
VDT_PRETEND_32 is defined in your environment before you do a
Pacman installation, it will install the 32-bit version on x86-64
platforms.
- Changed GridFTP logging to include transfer logs in gridftp.log and put
authentication logs in gridftp-auth.log
(vdt-support #1395)
- The VDT installation now requires Pacman 3.16.1 or later instead of Pacman
3.15 or later (as was required in VDT 1.3.9)
- The jClarens web services framework now runs under Tomcat 5 instead of
Tomcat 4. Tomcat 4 is no longer distributed with the VDT.
- The Bouncy Castle provider JAR file is installed just once into Tomcat 5
and removed from any web application that is installed into Tomcat 5. Doing
so should prevent any strange classloader errors.
To learn more, you can view
the main documentation page,
documentation specific to VDT 1.3.10d or support tickets closed in VDT 1.3.10d.
The VDT 1.3.10d cache is located at:
http://vdt.cs.wisc.edu/vdt_1310_cache