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.2.0
- None
Other Supported Features
- 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
- Recording of audit records to a directory, with a tool for uploading audit records to a database.
- An alternate job polling mechanism which uses the Scheduler Event Generator from GRAM4 in place of polling the scheduler directly.
Deprecated Features
- None
Only minor changes and bugfixes have occurred for GRAM2 since the last stable release.
The following problems and limitations are known to exist for GRAM2 at the time of the 4.2.0 release:
- Bug 720: allow gram client to detect the version of a gram server
- Bug 851: Add cleanup RSL attribute for cleaning up a job submission
- Bug 865: Total and available MEM not reported for gram inforproviders
- Bug 1460: Condor Jobmanager missing several features
- Bug 1538: Gatekeeper log rotation and logging job accounting info
- Bug 1550: Fixes for race condition in job manager
- Bug 1934: Gatekeeper's syslog output cannot be controlled
- Bug 2739: Gatekeeper AuthZ/Gridmap Callout result logging
- Bug 2741: catching SIGSEGV if dynamic loading of authorization modules fails
- Bug 3373: globus removes the temporary job directory before pbs writes back into it
- Bug 3795: jobmanager perl modules issues
- Bug 4199: Patch pre-WS GRAM to use individual condor logs for jobs
- Bug 4213: Patch to disable streaming
- Bug 4235: globus-job-manager doesn't exit if the job fails.
- Bug 4360: globus-job-get-output bug prevents output delivery
- Bug 4730: MPI Jobs using Globus LSF in HP XC Cluster....
- Bug 4747: Need evaluation of patch to JobManager.pm
- Bug 4771: date bug in job manager log file
- Bug 4779: gram GT2 log files: timestamps are not ISO 8601 compatible
- Bug 5143: DONE state never reported for Condor jobs when using Condor-G grid monitor
- Bug 5200: GRAM (pre-webservices) from OSG 0.6.0 (VDT 1.6.1) has bad syslog format
- Bug 5207: GRAM SoftEnv extension bug
- Bug 5250: Does not support mpi jobtype of RSL script
- Bug 5272: Invalid parsing of RSL file
- Bug 5429: stdin is lost when jobtype=multiple with jobmanager-lsf
- Bug 5536: Missing dependency in package globus_gram_job_manager_auditing
- Bug 5537: Missing dependency in package globus_gram_job_manager_auditing
- Bug 5554: GRAM2 4.0.5 setup-globus-job-manager-fork.pl silent failure
- Bug 5556: Audit directory setup instructions are insecure
- Bug 5580: ERROR regarding proxy lifetime should not be so frustrating - make it a WARNING
- Bug 5621: gram2 credential refresh problems in 4.0.5
- Bug 5775: gram status of old jobs incorrect on some lsf systems
- Bug 6313: GRAM Error 10 when submitting jobs when the job manager and client are linked with OpenSSL 0.9.8. See advisory for a solution.
- Bug 6240: Gatekeeper crash. See advisory for a solution.
GRAM2 depends on the following GT components:
- C Common Libraries
- Non-WS Authentication and Authorization
- XIO
- GridFTP
GRAM2 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)
There have been no protocol changes since GT version 4.0.x
There have been no API changes since GT version 4.0.x
There have been no exception/error changes since GT version 4.0.x
There have been no schema changes since GT version 4.0.x
See GRAM2 for more information about this component.