Note: This version of the VDT (1.6.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 2.0.0.

VDT 1.6.1 Release

Release History

Version	Released On	Notes
1.6.1m	23 August 2007	VOMRS security update (skipped letter “l” release letter to avoid confusion with digit “1”)
1.6.1k	11 July 2007	Updated the Gratia probes to version 0.25
1.6.1j	06 July 2007	Updated PPDG-Cert-Scripts to work with new DOEGrids web site
1.6.1i	21 May 2007	Globus security update and bug fix
1.6.1h	10 May 2007	Minor change for support of RedHat Enterprise Linux AP 5
1.6.1g	08 May 2007	Addition of Unsup-VOMRS and minor bug fixes
1.6.1f	17 April 2007	Updates to PPDG-Cert-Scripts and EDG-Make-Gridmap
1.6.1e	10 April 2007	Security and bug fix update—see details below
1.6.1d	2 April 2007	Security and bug fix update—see details below
1.6.1c	20 March 2007	Bug fix update—see details below
1.6.1b	26 February 2007	Bug fix update—see details below
1.6.1a	16 February 2007	Bug fix update—see details below
1.6.1	22 January 2007	Initial release

Updating from 1.6.1k to 1.6.1m

VOMRS is an experimental, unsupported package in VDT 1.6.1. Therefore, 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.6.1-LOCATION
. setup.sh
vdt-control --off
pacman -update VOMRS
vdt-control --on

Updating from 1.6.1j to 1.6.1k

Change List

If you are using a Gratia probe (and if you are an OSG site, you almost certainly are), update the applicable probe as below. You do not need to update the Gratia-Services or Gratia-Reporting packages.

For Gratia-Condor-Probe:

> cd $VDT_LOCATION
> . setup.sh
> cp gratia/probe/condor/ProbeConfig .
> pacman -update Gratia-Condor-Probe
> mv ProbeConfig gratia/probe/condor/

For Gratia-PBS-Probe:

> cd $VDT_LOCATION
> . setup.sh
> cp gratia/probe/pbs-lsf/ProbeConfig .
> cp gratia/probe/pbs-lsf/urCollector.conf .
> pacman -update Gratia-PBS-Probe
> mv ProbeConfig gratia/probe/pbs-lsf/
> mv urCollector.conf gratia/probe/pbs-lsf/

For Gratia-LSF-Probe:

> cd $VDT_LOCATION
> . setup.sh
> cp gratia/probe/pbs-lsf/ProbeConfig .
> cp gratia/probe/pbs-lsf/urCollector.conf .
> pacman -update Gratia-LSF-Probe
> mv ProbeConfig gratia/probe/pbs-lsf/
> mv urCollector.conf gratia/probe/pbs-lsf/

For Gratia-SGE-Probe:

> cd $VDT_LOCATION
> . setup.sh
> cp gratia/probe/sge/ProbeConfig .
> pacman -update Gratia-SGE-Probe
> mv ProbeConfig gratia/probe/sge/

Updating from 1.6.1i to 1.6.1j

Change List

> cd $VDT_LOCATION
> . setup.sh
> pacman -update PPDG-Cert-Scripts

Updating from 1.6.1h to 1.6.1i

Change List

To install the security update for your GRAM 2 (pre-web services) server: (Note that this includes a minor bug fix for globus-url-copy as well.)

Precursor steps
> cd $VDT_LOCATION
> . setup.sh   (or source setup.csh)

Turn off running services
> vdt-control --off globus-gatekeeper
> vdt-control --off gsiftp

Install the update
> pacman -update Globus-Base-Essentials
> pacman -update Globus-Base-RM-Essentials

Turn services back on
> vdt-control --on globus-gatekeeper
> vdt-control --on gsiftp

To install the security update for developers that link against Globus libraries. This is not needed to secure your server, but if you build an application against the affected libraries:
```
> cd $VDT_LOCATION
> . setup.sh   (or source setup.csh)

Install the update
> pacman -update Globus-Base-SDK
```

To install a new version of the GridFTP server with a bug fix in the DSI. (Unlikely to be needed by anyone outside of EGEE)

Precursor steps
> cd $VDT_LOCATION
> . setup.sh   (or source setup.csh)

Turn off running services
> vdt-control --off gsiftp

Install the update
> pacman -update Globus-Base-Data-Server

Turn services back on
> vdt-control --on gsiftp

Updating from 1.6.1g to 1.6.1h

Change List

This update is only to add support to RHEL 5 on x86_64. There is no need to do an update, this change will only affect new installs on RHEL 5.

Updating from 1.6.1f to 1.6.1g

Change List

Most people do not need to update, unless they want to install VOMRS. If you do wish to perform the update:

To install VOMRS

pacman -get http://vdt.cs.wisc.edu/vdt_161_cache:Unsup-VOMRS

To get minor bug fixes (see the change list for details):

cd $VDT_LOCATION
pacman -update VDT-Service-Management
pacman -update VDT-Configure-Base
pacman -update Perl-Environment
pacman -update OSG-Site-Verify

Updating from 1.6.1e to 1.6.1f

Change List

To upgrade PPDG-Cert-Scripts
```
pacman -update PPDG-Cert-Scripts
```

To upgrade EDG-Make-Gridmap (only works as root)

cd $VDT_LOCATION
mv edg/etc/edg-mkgridmap.conf .
pacman -update EDG-Make-Gridmap
mv edg-mkgridmap.conf edg/etc/.

Updating from 1.6.1d to 1.6.1e

Change List

To upgrade the Generic Information Provider:
```
pacman -update Generic-Information-Provider
```
To upgrade GSI OpenSSH
```
pacman -update GSIOpenSSH
```

Updating from 1.6.1c to 1.6.1d

Change List

If you have VDT 1.6.1c and you wish to upgrade to VDT 1.6.1d, you probably do not need to do so. There is only two cases in which you need to ugprade, and we believe that both are rare among VDT users.

Case 1: If you are using the Gratia Services (not probes), you should upgrade Tomcat and MySQL to correct security flaws. Note that you must run configure_gratia after this update.
```
pacman -update Tomcat-5.5
pacman -update MySQL-5
. setup.sh
configure_gratia --services --reporting
```
Case 2:If you installed a Gratia probe (and you did so if you are using the OSG installation) and your version of Python is too old, the probe won't work. Specifically, if Python is older than 2.2 or if you are using the SGE probe and it's older than 2.3, you can upgrade the probe. When you do so, it will install Python in the VDT location, and should work.
```
pacman -update Gratia-Condor-Probe
   or
pacman -update Gratia-PBS-Probe
  or
pacman -update Gratia-LSF-robe
  or
pacman -update Gratia-SGE-Probe
```

There was another bug fix in configure_prima_gt4, but this fixes a bug during installation and so it doesn't help you to upgrade now. But if you wish, you can upgrade it with:

pacman -update Configure-PRIMA-GT4

Updating from 1.6.1b to 1.6.1c

If you have VDT 1.6.1b and you wish to upgrade to VDT 1.6.1c, you probably do not need to do so. There are two cases in which you should update.

Case 1: If you are using PBS or LSF and Gratia (you are using Gratia if you are part of OSG), then you need to update the Gratia Probe with either
```
pacman -update Gratia-PBS-Probe
```
or
```
pacman -update Gratia-LSF-Probe
```
Case 2: If you are on a multi-homed host and are part of OSG, and the GIP reports your host name incorrectly, you need to update the program that configures the GIP:
```
pacman -update Configure-GIP
```
After this update you can set GLOBUS_HOSTNAME in your environment to be the host name you wish to report. Then, rerun the configure_gip script to have it report your host name correctly.

Updating from 1.6.1a to 1.6.1b

Change List

If you have VDT 1.6.1a and you wish to upgrade to VDT 1.6.1b, you probably do not need to do so. There are two cases in which you should update.

Case 1: If you are using PBS, and job submissions to your site are not working, please update with:
```
pacman -update Globus-PBS-Setup
```
Case 2: If you are using LSF, and job submissions to your site are not working, please update with:
```
pacman -update Globus-LSF-Setup
```

If you really want the other changes, you can get them with:

pacman -update OSG-Site-Verify
pacman -update VDT-System-Profiler

Updating from 1.6.1 to 1.6.1a or 1.6.1b

Change List

The update from VDT 1.6.1 to VDT 1.6.1a or VDT 1.6.1b requires special steps or else it will break your VDT installation. Please use the special VDT 1.6.1a update instructions to update from VDT 1.6.1 to VDT 1.6.1a. However, due to problems with updates and the OSG cache, OSG users should use the OSG update instructions instead.

Changes in VDT 1.6.1k

The Gratia probes were updated to version 0.25.

Changes in VDT 1.6.1j

The PPDG-Cert-Scripts package was updated to work with the updated DOEGrids site.

Changes in VDT 1.6.1i

A Globus security advisory was fixed. Details on the problem. This affects two packages in the VDT, Globus-Base-Essentials and Globus-Base-RM-Essentials.
A Globus bug affecting globus-url-copy was fixed. This is in Globus-Base-Essentials, so it comes along with the security fix.
A minor omission in the GridFTP DSI was fixed. This only affects developers building plugins for GridFTP, and as far as we know, it only affects software from EGEE that is not yet released. It will not affect most readers of this note, so feel free not to take this part of the update. It affects the Globus-Base-Data-Server package.

Changes in VDT 1.6.1h

RHAP 5 support was verified on x86, x86_64, and 32-on-x86_64. For more information, see the requirements page.
A minor bug was fixed in the PyGridWare package. On RHAP 5 on x86_64, PyGridWare contains python libraries in both a lib and lib64 directory. These are symlinked together now.

Changes in VDT 1.6.1g

VOMRS was added to the VDT. VOMRS is a tool to help manage a VOMS installation. The package name is "Unsup-VOMRS", to reflect the fact that this is major functionality added to an existing release, and is therefore unsupported. In VDT 1.7.0, it will be released as "VOMRS"; that is, with no "Unsup-" prefix.
There was a minor feature added to vdt-control: a new flag called "--no-start". This modifies --on so that it does not restart (x)inetd or run any init.d scripts. This option is rarely used but can be helpful when doing installation in some systems, such as ROCKS.
Init.d scripts now use "." instead of "source" to set up their environment. This change only affects systems like Ubuntu where /bin/sh is the Bourne shell, not the Bash shell.
PERL5LIB is now set correctly on Debian and Ubuntu systems.
The site_verify script was updated to work better with SGE.

Changes in VDT 1.6.1f

The PPDG Cert Script package was updated to allow scripts to use an http_proxy.
The EDG Make Gridmap script was upgraded to work with versions of VOMS Admin newer than version 1.2.10. To date, these new versions of VOMS Admin have not been deployed yet anywhere, but we know that they will be eventually.

Changes in VDT 1.6.1e

GSI OpenSSH was updated to version 3.9 to address a security issue. Most VDT users are not using GSI OpenSSH, but if you are, we recommend upgrading. More information
The Generic Information Provider was upgraded to fix a few small bugs. It fixed problems that caused incompatibilities with WLCG and problems with collection of accurate VO information from PBS. We recommend updating to all OSG users.

Changes in VDT 1.6.1d

MySQL 5 and Tomcat 5.5 were updated to fix security flaws. The only component that used MySQL 5 or tomcat 5.5 in the VDT is the Gratia Service (not the probes) (VDT ticket 2502)
Updated the configure-prima-gt4 script to prevent the following issue: if the file /etc/grid-security/gsi-authz.conf exists and contains entries, these will be preserved in the file. The libprima_authz_module_*.so entry will be updated if necessary. (VDT ticket 2501)
Updated the Gratia probe pacman files to install Python if the existing python on the system is less than the required version. The Gratia probe for SGE requires Python 2.3 or greater. The probes for Condor, PBS, and LSF require Python 2.2 or greater. (VDT ticket 2534)
Updated configure-tomcat to fix a minor bug related to package versions.
There is a new package: Unsup-Globus-CondorNFSLite-Setup. This is an alternative to the Condor jobmanager that uses Condor's file transfer mechanism instead of relying on NFS. More information
There is a first pass at adding VOMRS to the VDT, in Unsup-VOMRS. Right now, it only lays down the bits and requires you to run the VOMRS configuration script by hand. A future version will do more configuration on your behalf.

Changes in VDT 1.6.1b

Fixed a bug in the PBS job manager so that environment variables whose value contains a comma (like GLOBUS_TCP_PORT_RANGE) do not trigger a bug in some versions of PBSPro that cause job submissions to fail.
Fixed a bug in the LSF job manager that uses SoftEnv whether or not it is present.
Fixed a minor bug in OSG-Site-Verify that could run too many MonaLisa tests if the first one failed.
Made a few improvements to the vdt-system-profiler to gather more information.

Changes in VDT 1.6.1a

Patched Globus to fix low-risk security bug in which a malformed grid-mapfile entry could cause denial of service. This is described in Globus Bugzilla Ticket 4979 and is fixed in globus_gss_assist 3.23.
Upgraded Squid to address a low-risk denial-of-service attack.
Added support for the VOMS client on x86-64 machines, both on native x86-64 and 32-on-x86-64 installs. The binaries are the 32-bit binaries, despite what the download messages may say. Updates seem to work.
Patched the CEMon server with Tanya Levshina’s new code to avoid a memory leak and new configuration to support the RAW dialect. To get updates to work, the pacman file now removes any traces of a previous CEMon webapp from Tomcat before installing the new one. (VDT ticket 2426)
Renamed the filename that the Job-Environment patch looks for: osg-attributes.conf became osg-job-environment.conf. (VDT ticket 2423)
Added support for a second configuration file to the Job-Environment patch. The new file, $VDT_LOCATION/monitoring/osg-local-job-environment.conf, has the same format as osg-job-environment.conf and allows local administrators to add their own definitions to the job environment. If the same variable is defined in both files, the definition in osg-local-job-environment.conf is used. Neither file is required. (VDT ticket 2396)
Fixed Globus-LSF-Setup so that it no longer requires soft-msc to be installed. If you previously installed Globus-LSF-Setup but it failed, do a pacman -remove Globus-LSF-Setup, then reinstall it.
When edg-mkgridmap runs, if $VDT_LOCATION/monitoring/osg-local-user-vo-map.txt exists, it is concatenated to the osg-user-vo-map.txt file before we run check-vo-map. This means that you can add in local changes to the user-VO map, but only if they correctly refer to existing accounts.
Changed the text of the prompt for installation questions about enabling services. The old text originated in the days of the “skip” answer and was completely wrong for VDT 1.6. The new text is accurate and hopefully clearer, too, including a reference to some documentation on enabling services.
Updated the Generic Information Provider in minor ways, mostly in the configure_gip script that sets it up.
Removed an extraneous debugging command in the Gratia Condor patch. Previously, the following line occurred in both condor.pm and managedfork.pm:
```
system("echo succesfull copy >> /var/tmp/gratia.log");
```
This command uselessly adds to a log file (thus consuming disk space) and, more importantly, causes spurious error messages because only the first user that touches the log may write to it. The update removes the line from both files. (VDT ticket 2379)
Added the Gratia probes (for Condor, LSF, and PBS) to vdt-version. (VDT ticket 2363)
Added the VDS worker package to vdt-version. Fixed an update problem along the way. (VDT ticket 2364)
Tweaked the log4j settings for CEMon so that BDII messages are logged. Also, the maximum log file size was raised from 100 KB to 2 MB. (VDT ticket 2412)
Patched the three non-Condor Globus-WS-*-Setup packages to fix permissions on key Globus directories after installation. (VDT ticket 2429)

Highlights of changes since 1.4.0

This release is a bug fix release, and it contains numerous small bug fixes and small improvements over 1.6.0. The Open Science Grid Validatin Testbed Group did a great deal of testing that improved VDT 1.6.1. Thank you!

Upgraded Software Since 1.6.0

Bug Fixes Since 1.6.0

Fixed the CA Certificate installation process when you respond "no" to the question about whether or not they should be installed. They are no longer installed, but you can return at a later time to $VDT_LOCATION/post-install/certificates/install.sh to install them. (VDT ticket 1553) (VDT ticket 2162)
Fixed a bug in the SQL setup for RFT that prevented indices being created to improve performance. (VDT ticket 2348)
Installing Gratia services or reporting now correctly enables MySQL 5, Apache, and Tomcat 5.5 (if needed). (VDT ticket 2325)
The Gratia probes were updates to fix a few small bugs.
The Globus Web Services GRAM Client installation was missing some tools (globus-job-run-ws, globus-job-submit-ws, globus-job-get-output-ws and globus-job-clean-ws), and these have been added back in.

Other Changes since 1.6.0

When you run configure_globus_gatekeeper by hand (which you might do to set up the managed fork jobmanager), it requires you to specify the --server option. (VDT ticket 2351)
configure_gip no longer restarts Tomcat when setting up the GIP for CEMon. (VDT ticket 2332)
configure_gip now correctly creates the GIP wrapper script.
configure_gums now correctly preserves configuration from an old VDT location for the client install, not just the server install.
If VDT_GUMS_HOST is set in the environment when you install the GUMS-Client package, its value will be used for the hostname of the GUMS server.
Minor improvements and bug fixes to vdt-control and vdt-register-service. (VDT ticket 2333)
New documentation for vdt-control, vdt-register-service, and vdt-version on both the web and as man pages in an installation.
Where there might be concerns about privacy, we try to be very clear about it. When some components are installed, they will create a post-install/PRIVACY file with notes. These same notes are also on the documentation web page
Several tweaks to how we configure Gratia. (VDT ticket 2354)

To learn more, you can view the main documentation page or documentation specific to VDT 1.6.1.

The VDT 1.6.1 cache is located at: http://vdt.cs.wisc.edu/vdt_161_cache