Note: This version of the VDT (1.10.1) is supported, but is not our latest stable release. The current stable release is 2.0.0.

VDT 1.10.1v Update

On 2009-04-21, the VDT team announced the release of VDT 1.10.1v.

Changes to VDT 1.10.1v

This is a substantial in-place update that affects three major areas: Globus, authorization infrastructure, and information reporting.

Globus Updates

Globus has been updated to version 4.0.8. Previously we were using 4.0.7. This provides us with compatibility with TeraGrid and many bug fixes. We have also updated our set of patches for Globus. (VDT ticket 3814) New Globus patches Globus 4.0.8 release notes

Settings for Globus web services have been modified to improve performance and scalability. These changes touch a variety of packages. (VDT ticket 2987)

• The maximum heap size was increased from 512MB to 1024MB
• The initial heap size was set to 256MB
• The init script for globus-ws set the file descriptor limit to 16,384, overriding lower defaults (typically 1,024)
• The container thread setting containerThreads has been increased from 2 to 20
• The container thread setting containerThreadsMax has been increased from 20 to 50
• The container thread setting containerThreadsHighWaterMark has been set to 10
• enableLocalInvocations have been turned on
• maxActiveAllowed has been reduced to 30 from 100

Authorization infrastructure updates

1. GUMS has been updated to 1.3.14 (VDT ticket 4202)

   See the GUMS release notes for full changes. Highlights include:

   • Ability to ban users or VOs
   • Please note: This new version of GUMS will give an error if you have duplicate mappings in your configuration file. This is usually the sign of a problem, but in the past it was an easily ignored warning.
2. PRIMA has been updated to 0.8.3. (VDT ticket 4250)
3. Glexec has been updated to 0.6.5. (VDT ticket 4361)
   Aditionally, Glexec is now supported on RHEL5/x86_64. (VDT ticket 3562)
4. EDG-Make-Gridmap (or more accurately, our wrapper for it) has been upgraded so that it properly detects if PRIMA/GUMS is being used.

Information reporting updates

1. There has been a major update to GIP 1.1.0. (VDT tickets 4602, 4627, 4640) GIP changelog
2. CEMon has been updated to 1.10.1.0. The biggest change is that there is improved support for advertising MPI information. CEMon also shuts down faster in some cases, and there are a variety of bug fixes.
   (VDT ticket 4383)
   CEMon Release Notes (Look for “Tag glite-ce_R_1_10_1_0”)
3. The verify-gip-for-cemon script to verify GIP output has been upgraded to 1.5.1. This includes bug fixes and a new --summary option. (VDT ticket 4848)
4. The central Gratia collectors have changed. The VDT Gratia configuration script, configure_gratia, should automatically change to the new default collectors when you run configure-osg.py. There is no Pacman update necessary for this change. (VDT ticket 4795)

Storage updates

1. Updated Bestman to 2.2.1.2.i4 (VDT ticket 4808)
   Added more command-line options to configure_bestman (VDT ticket 4818)
   Fixed a problem with configuration preservation during updates (VDT ticket 5083)

Other updates

1. Updated OSG-RSV (Core and Probes) to version 2.4.1 (VDT ticket 4919)

   Highlights include:

   • SRM and GridFTP probes can be run on non-standard ports now
   • CRL warning threshold has been decreased to 48 hours
   • Job manager status probe's wait time has been fixed to be consistent
2. Updated Wget to 1.11.4 and removed references to /home/condor in the binary itself. (VDT ticket 4660)
3. The LFC-Client package has been added to the VDT-Client package. It was requested by ATLAS.
4. Updated LCG-Info from 1.11.0-1 to 1.11.4-1.
5. The Open Science Grid Match Maker package has been added as OSG-Match-Maker. (VDT ticket 4600)

Updating to VDT 1.10.1v

Starting with this release of the VDT, we strongly encourage users to update the VDT using the new VDT updater script. If you really want to do it the hard way, instructions are available on another page. Otherwise, continue below with the updater script.

Updating with the Updater Script

Please read through these instructions once before starting. They’re not long and it might help to understand how the process goes.

Also note that the actual updater script (second to last step) can run for quite a while, especially during the pacman updates themselves (step 4 in the script). We have observed step 4 taking 10–15 minutes for an OSG CE. Once that step begins, it is safe to ignore the updater for a while. But, do check back after a while, because there may be some wrap-up steps for which you need to answer questions.

And last, but hardly least: It is critical to have a backup of your VDT installation. But, it is equally important to the updater script that the backup include the updater package itself, so there is a step below for making your backup at the appropriate time.

1. Log in to the machine as the same user who installed the VDT
2. Change directories to your VDT_LOCATION
3. If needed, source a setup file (setup.sh or setup.csh)
4. Shut down all VDT services

   vdt-control --off

   Make sure all VDT processes are stopped before continuing. There’s no easy way for us to define exactly how to do this step. In a nutshell, use ps and look for processes that look like they come from your VDT install, then kill them.

5. Get the updater

   pacman -get http://vdt.cs.wisc.edu/vdt_1101_cache:VDT-Updater

6. Make a complete, exact backup

   cp -pr $VDT_LOCATION BACKUP-LOCATION

   or

   rsync -a $VDT_LOCATION/ BACKUP-LOCATION

   The updater script is going to verify the contents of your backup, so you should have a backup that is a file-level copy of the VDT installation. Do not use tar, for example, to make the backup or else the updater script will not be able to verify the backup for you.

7. Run the updater and follow its prompts

   vdt/update/vdt-updater

8. If the update goes well, restart VDT services

   vdt-control --on