Software Links
Getting Started
- A Globus Primer
- Globus Is Modular!
- Quickstart
- Installing GT
- Platform Notes
- GT Developer's Guide
- GT User's Guide
- Migrating Guides
Reference
Manuals
Common Runtime
Security
- GSI C
- GSI Java
- Java WS A&A
- C WS A&A (coming soon)
- CAS
- Delegation Service
- MyProxy
- GSI-OpenSSH
- SimpleCA
Data Mgt
WS MDS
Execution Mgt
Table of Contents
GRAM4 is built and installed as part of a default GT 4.2.0 installation. For basic installation instructions, see Installing GT 4.2.0.
In order to use GRAM4, the container must be started with Transport Level
security. The "-nosec" option should *not* be used with
globus-start-container.
GRAM4 requires that the sudo command is installed and functioning on the service host where GRAM4 software will execute.
Authorization rules will need to be added to the
sudoers file to allow the GRAM4 service
account to execute (without a password) the scheduler adapter in the
accounts of authorized GRAM users. For sudo configuration details, see the
Configuring section.
Platform Note: On AIX, sudo is not installed by default, but it is available as source and rpm here: AIX 5L Toolbox for Linux Applications
GRAM4 depends on a local mechanism for starting and controlling jobs. Included in the GRAM4 software is a Fork scheduler, which requires no special software installed to execute jobs on the local host. However, to enable GRAM4 to execute and manage jobs to a batch scheduler, the scheduler software must be installed and configured prior to configuring GRAM4.
GRAM4 depends on scheduler adapters to translate the GRAM4 job description document into commands understood by the local scheduler, as well as monitor the jobs.
Scheduler adapters included in the GT 4.2.0 release are: PBS, Condor, LSF
Third party schedulers adapters available for GT 4.2.0 are: Sun Grid Engine
For configuration details, see "Configuring scheduler adapters" in the Configuring section.
Though staging directives are processed by RFT (see next section), RFT uses GridFTP servers underneath to do the actual data movement. As a result, there must be at least one GridFTP server that shares a file system with the execution nodes. There is no special process to get staged files onto the execution node before the job executable is run. See the "Non-default GridFTP server" section of Configuring GRAM4 for details on how to configure GRAM4 for your GridFTP servers used in your execution environment.
GRAM4 depends on RFT to perform file staging and cleanup directives in a job description. For configuration details, see System Administrator's Guide. Important: Jobs requesting these functions will fail if RFT is not properly setup.