Globus Toolkit® 3.2 GRAM Release Notes

The 3.2 release includes two components for resource management:e Pre-WS GRAM and WS-GRAM. The GRAM components are designed to simplify the use of remote systems by providing a single standard interface for requesting and using remote system resources for the execution of "jobs".

The 3.2 release contains many important bug fixes and improvements on existing functionality.

Improvements:

For the web service (WS) Managed Job Service ( MJS ), we improved the following:
- Faults are more easily internationalized.
- The local scheduler scripts provide better error messages.
- Instances are deactivated during periods of inactivity in order to increase scalability by reducing memory consumption.

For the pre-WS JobManager, we applied a patch for bug 802 which enables an alternate method for job status detection for a user (this is used in Condor-G).
For both WS MJS and pre-WS JobManager, the local scheduler scripts
have been improved to reduce the chance of errors due to NFS caching delays and increase scalability by reducing memory consumption.
The local scheduler scripts have been improved to store job files in a unique job directory instead of the gass cache.
The WS GRAM components are now IPV6 compliant.
For the managed-job-globusrun program, we added these options:
- The -deleg [full | limited] option indicates limited or full proxy delegation.
- The -proxy [ <file path>] option selects credentials to use for authentication.

Important bug fixes:

For the WS MJS, we fixed:
- UHE GRIM credential lifetime to obey user configuration.
- job recovery problems.
For the WS GRAM compontents, we fixed UHE recovery and automatic shutdown (due to inactivity)

All GT 3.2 bug fixes for:

Note 1: If you use Condor-G with Globus Toolkit 3.2, you must use Condor version 6.6.3 or higher.

Note 2: The MJS port type has changed in 3.2, so 3.0 MJS clients cannot use a 3.2 MJS service. And 3.2 MJS clients cannot use a 3.0 MJS service.