Note: This version of the VDT (1.10.0) 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.10.0 Release
On 2008-04-08, the VDT team announced the release of VDT 1.10.0.
Updates to VDT 1.10.0
| Update |
Release Date |
Notes |
| 1.10.0a |
2008-04-24 |
A large number of bug fixes and software updates |
| 1.10.0 |
2008-04-08 |
Initial release |
Highlights of changes since 1.8.1
- Globus and other software are now linked against the system
OpenSSL instead of the one provided with Globus. See below for
details.
- We've added support for Debian 4.
- There is now a
ca-certs-status program to show you what is
happening with CA certificate CRL updates.
- Condor-Devel has been replaced with Condor-Cron
- We've updated a ton of software and fixed many small bugs.
New Software Since 1.8.1
- VOMRS-Client (VDT ticket 3040)
- Unsup-Xrootd
We have added Xrootd, a cluster file server. It was a late
addition, so we only provide the binaries for a variety of
platforms, but no configuration. Because the VDT Team is still
learning about Xrootd, we've labeled it as an unsupported package.
- Procd
The Procd is a unprivileged, supporting tool used by glexec.
Upgraded Software Since 1.8.1
Bug Fixes Since 1.8.1
-
PyGlobus now only sets one PYTHONPATH (lib or lib64), not both. (VDT ticket 3299)
- Fixed the MySQL wrappers that the VDT creates so that commands
like "mysql" return exit codes properly. (VDT ticket 3300)
- The JDK-1.4 and JDK-1.5 packages are now fixed to properly
install a 32-bit version of Java when running a 32-on-x86_64
install. (VDT ticket 3306)
- Fixed an issue that prevented RSV jobs from running if
vdt-control was run in a directory that had restricted file
permissions for the RSV user. (VDT ticket 3284)
- Added a timeout to the RSV gratia-script-consumer to prevent RSV
outages when the central Gratia collector hangs. (VDT ticket 3317)
- A handful of packages that were unable to be installed with
Pacman have been fixed.
-
The URL given when asking the question about where CA
certificate should be installed was incorrect. It is now
correct.
-
The vdt-update-certs script will now error out if the directory
CERTS_DIRECTORY/certificates
is a directory and not a symlink. This script requires that this
location is a symlink to
work properly, and will record an error if it is not.
(CERTS_DIRECTORY is the directory
pointed at by $VDT_LOCATION/globus/TRUSTED_CA). (VDT ticket 3390)
-
VOMS now works on x86-64 SLES 9. (VDT ticket 3401)
-
Picked up the correct version of our pre-compiled Perl modules on
x86-64
SLES 9. (VDT ticket 3340)
-
The
Condor NFS lite job manager now works with WSGRAM.
(VDT ticket 3411)
-
We now tell Tomcat to set Java's maximum PermGen memory to be
larger, to avoid running out of PermGen memory. (VDT ticket 3419)
-
Improved how we track what files are installed by Globus, so they
can be removed. This should improve our ability to have smooth
updates for Globus components. (VDT ticket 3102)
-
The SGE job manager now works with rotated log files.
-
Fixed a bug in the Condor job manager where it would interpret
aborted jobs as successful. (VDT ticket 3406)
-
Installing the Globus-ManagedFork-Setup package no longer
installs the Condor job manager, but just the managed fork job
manager. (VDT ticket 3393)
New Platform Support
- The VDT now supports Debian 4 on both x86 and x86-64 architectures.
- The VDT now supports Suse Linux Enterpise 9 (SLES 9) on x86-64.
Platforms Dropped from Support
- We have dropped support for Fedora Core 4.
Other Changes since 1.8.1
-
Globus is no longer linked against the version of OpenSSL provided
with Globus (which was quite out of date), but is linked against
the version that comes with your OS. We also used to link lots of
VDT software against the Globus OpenSSL. Using the OS-provided
OpenSSL should be more secure: if problems are found in OpenSSL,
your OS vendor will likely update OpenSSL quickly, and software in
the VDT will benefit from it.
-
The Generic Information Provider has had a major upgrade. You'll
now find it in
$VDT_LOCATION instead of
$VDT_LOCATION/lcg. Hopefully you'll also find a lot
of bug fixes and improvements. One of the finer points: the
dynamic condor probe used to only subtract Owner VMS from the
total if you set OSG_GIP_SUBTRACT_OWNER .. the
behavior is completely toggled. Now it does the subtraction unless
you set OSG_GIP_DONT_SUBTRACT_OWNER
(VDT ticket 3387)
-
Condor-Devel has been replaced with Condor-Cron to better reflect
the current use of the package. Condor-Cron has been simplified
to support only the subset necessary to run "cron-like" jobs.
Users requiring a full batch system or grid computing capabilities
should continue to use the Condor package. (VDT ticket 3410)
The affects OSG sites using RSV. The upshot for you is that
Condor-Cron is always installed (if you are using RSV), and you
cannot use your pre-installed Condor instead of Condor-Cron. This
keeps RSV jobs separate from your production jobs: you can stop or
restart RSV jobs without affecting your production jobs. Also,
we've provided wrappers for Condor commands specific to
Condor-Cron. For example, you can see RSV jobs with
condor_cron_q.
-
Added --enable and --disable options to vdt-control, which allow a
user to set the desired state of one or more services without
having to run a separate command (vdt-register-service).
(VDT ticket 3412)
-
There is a new script called ca-certs-status to help you
understand the state of the CA certificates installation. For
example:
# ca-certs-status
CA-Certificates Info:
Version: 35-1
vdt-update-certs info:
Last run: 2008-04-07T10-10-21
Status: Installed and running
Fetch-CRL info:
Last run: 2008-04-07T16-56-57
Status: Installed and running
It will give a warning if the CA certificate updater hasn't been run in a while:
# ca-certs-status
CA-Certificates Info:
Version: 35-1
vdt-update-certs info:
Last run: 2008-04-07T10-10-21
WARNING: vdt-update-certs has not run in over 24 hours
Status: Installed and running
Fetch-CRL info:
Last run: 2008-04-07T16-56-57
Status: Installed and running
(Note, this has been improved since VDT 1.9.1.)
-
A new script has been added that checks for some prerequisites for
the VDT. This will notify users of missing prerequisites earlier
in the install process. For example, it checks if a system has
SELinux enabled. There are known issues when attempting to
install/execute the VDT with SELinux enabled, so we now will print
a warning near the beginning of the install.
-
CA Certificates are now initially installed using the
vdt-update-certs script. We have removed the CA-Certificates-Base
package from the cache. (VDT ticket 3405)
-
Squid has been reconfigured to support 16,384 open file
descriptors, an increase from the default 1,024. This should
allow extremely busy Squid caches to scale to more simultaneous
requests. (VDT ticket 3132)
-
Squid now preserves configuration data when using "pacman -update
Squid". It also attempts to preserve old Squid configurations
when using OLD_VDT_VERSION when installing a new VDT version.
This functionality only works on VDT 1.8.1 and later.
(VDT ticket 2978)
- Unsup-Dccp has been renamed to Dccp
- Unsup-Stunnel has been renamed to Stunnel
- NMI-Build-And-Test has been renamed to Metronome
-
Improved how the fully qualified hostname is determined, and
improved error logging in cases in which it is not possible to
determine one. (VDT ticket 3187)
-
The configure_gratia script now preserves the state information
from
$OLD_VDT_LOCATION/gratia/var/tmp during
side-by-side upgrades. (VDT ticket 3221)
-
Permissions have been loosened on the vdt-control state file.
This means that an unprivileged user can now run
vdt-control --list (VDT ticket 3301)
- CEMon-Client has been removed from the VDT
-
The configure_osg_rsv script has moved from
$VDT_LOCATION/vdt/setup to $VDT_LOCATION/osg-rsv/setup.
We have created a symlink in the old directory to help avoid confusion.
-
Made the vdt-install.log file readable only by the installing
user, in case the log file contains sensitive data. (VDT ticket 3215)
Learning More
To learn more, you can view
the main
documentation page or
documentation
specific to VDT 1.10.0.
Known Problems
The VDT 1.10.0 cache is located at:
http://vdt.cs.wisc.edu/vdt_1100_cache