Software Links
Getting Started
- Doc Structure
- A Globus Primer
- Quickstart
- Installing GT
- Platform Notes
- Migrating from GT2
- Migrating from GT3
Reference
- PDF version
- Best Practices
- Coding Guidelines
- API docs
- Public Interfaces
- Resource Properties
- Samples
- Glossary
- Index
- Performance Studies
Common Runtime
Security
Data Mgt
Information Svcs
Execution Mgt
Table of Contents
The Grid Resource Allocation and Management (GRAM) service provides a single interface for requesting and using remote system resources for the execution of "jobs". The most common use of GRAM is remote application execution and control. It is designed to provide a uniform, flexible interface to job scheduling systems.
Features new in release 4.1.0
- An alternate job polling mechanism which uses the Scheduler Event Generator from WS-GRAM in place of polling the scheduler directly.
- Recording of audit records to a directory, with a tool for uploading audit records to a database. This feature is turned off by default. It can be turned on by adding the -audit-directory command line option to job manager. Details can be read here
Other Supported Features
- The ability to select the account under which the remote job will be run. If a user's grid credential is mapped to multiple accounts, then the user can specify in the RSL under which account the job should be run.
- Remote job execution and management
- Uniform and flexible interface to batch scheduling systems
- File staging before and after job execution
- Data streaming of stdout/err during jobs execution
Deprecated Features
- None
The following changes have occurred for Pre-WS GRAM since the last stable release, 4.0.2:
The jobmanager perl modules are no longer a part of the jobmanager package. They were put into their own globus_gram_job_manager_scripts package.
- Bug 1037:globus-gram-reporter does not publish additional LSF job attributes in mds 2.4
- Bug 1551:Race condition in job manager
- Bug 1550:Fixes for race condition in job manager
- Bug 1868:globus_gram_reporter is missing from GT 3.2.1 PreWS distribution
- Bug 1934:Gatekeeper's syslog output cannot be controlled
- Bug 2235:GT3.2.1 globus_gram_client_tools-4.3 patch broken
- Bug 3373:globus removes the temporary job directory before pbs writes back into it
- Bug 3425:personal gatekeeper does not work on AIX
- Bug 3428:globus-personal-gatekeeper -list failing
- Bug 2739:Gatekeeper AuthZ/Gridmap Callout result logging
- Bug 2741:catching SIGSEGV if dynamic loading of authorization modules fails
- Bug 3911:Bug in GRAM documentation for Condor log file
- Bug 4116:globus_module_activate( GLOBUS_GRAM_CLIENT_MODULE ) behaves differently for ENOENT and EACCES
- Bug 4235:globus-job-manager doesn't exit if the job fails.
- Bug 4336:If submitting of a job is repeated, an error will occur.
- Bug 4450:GT 4.0.1 globus-gatekeeper hang on UC/ANL TeraGrid
- Bug 4360:globus-job-get-output bug prevents output delivery, PBS jobmanager affected. See also globus-job-clean, globus-job-cancel
Pre-WS GRAM depends on the following GT components:
- C Common Libraries
- Pre-WS Authentication and Authorization
- XIO
- GridFTP
Pre-WS GRAM depends on the following 3rd party software. The dependency exists only for the batch schedulers configured, thus making job submissions possible to the batch scheduling service:
- PBS
- Condor
- LSF
- other batch schedulers... (where the GRAM scheduler interface has been implemented)
Protocol changes since GT version 4.0.2
- None. Pre-WS GRAM in 4.1.0 is interoperable with 4.0.x
See Pre-WS GRAM for more information about this component.