globus_gram_job_manager_script_interface(3) [debian man page]
globus_gram_job_manager_script_interface(3) globus gram job manager globus_gram_job_manager_script_interface(3)NAME
globus_gram_job_manager_script_interface - Job Manager Scheduler Interface The GRAM Job Manager interfaces with the job filesystems and
scheduler through scheduler-specific Perl modules.
GRAM provides several Perl modules which can be used to implement scheduler-specific interfaces to the GRAM Job Manager. These are:
Globus::GRAM::Error
This module implements the GRAM error results as objects. Methods in this module will construct a GRAM error with the value matching
the values in the GRAM Protocol library. A scheduler-specific JobManager module may return one of these objects from its methods to
indicate errors to the Job Manager program.
Globus::GRAM::JobState
This module defines the GRAM job state constants. A scheduler-specific JobManager module returns one of these values from its methods
to indicate the managed job's current state.
Globus::GRAM::JobSignal
This module defines the GRAM job signal constant values. The Job Manager uses these values to communicate which signal is being invoked
in the manager's signal method.
Globus::GRAM::JobManager
This module defines the actual implementatoin of the Job Manager scheduler interface. One writing a scheduler-specific GRAM interface
will create a subclass of this object which overrides the default implementation's methods.
Globus::GRAM::JobDescription
This module mimics the RSL job description using perl syntax. The job manager passes an object of this type to the JobManager modules's
constructor. The job manager stores RSL and some configuration values in that JobDescription object. The manager accesses values stored
in the JobDescription by invoking methods containing the RSL attribute's name (example: $description->gram_my_job()). Method names are
handled as if they were based on the canonical RSL representation of the attribute name. For example, the gram_my_job may be
equivalently referred to as GramMyJob, grammyjob, or GRAM_My_Job.
Version 13.33 Mon Apr 30 2012 globus_gram_job_manager_script_interface(3)
Check Out this Related Man Page
globus_gram_job_manager_configuration(3) globus gram job manager globus_gram_job_manager_configuration(3)NAME
globus_gram_job_manager_configuration - Job Manager Configuration The Job Manager is generally configured using the setup-globus-gram-job-
manager setup script.
This section of the Job Manager manual describes all options which may be passed to the GRAM Job Manager in the configuration file
$GLOBUS_LOCATION/etc/globus-job-manager.conf.
Configuration File Options-k
Indicate that the job manager was built with the kerberos GSSAPI instead of GSI. This disables checks for a delegated GSI credential.
-home GLOBUS_LOCATION
Set the GLOBUS_LOCATION environment variable to the specified Globus-Location.
-target-globus-location GLOBUS_LOCATION
Set the GLOBUS_LOCATION environment variable to the execution node's GLOBUS_LOCATION, if different than the GRAM node's GLOBUS_LOCATION
-type JOB_MANAGER_TYPE
Set the type of scheduler interface to use for this job manager. A similarly named Perl module in the
$GLOBUS_LOCATION/lib/perl/Globus/GRAM/JobManager/ directory is needed.
-history PATH
Set the path to the directory to store job history files.
-cache-location PATH
Set the path for the GASS cache. This path must be unique for each user. RSL substitutions (such as /tmp/buildd and pbuilder) may be
used in this path. See RSL Substitions for a list of available RSL substitutions.
-extra-envvars VAR1[=VAL],VAR2,...
The Job manager will attempt to get the listed VARs from its environment and set them the same for the job's environment. For example,
-extra-envvars LD_LIBRARY_PATH,GLOBUS_TCP_PORT_RANGE
-scratch-dir-base PATH
Set the default scratch directory root for the job manager. Job-specific scratch directories will be created as a subdirectory of this
directory. RSL substitutions (such as /tmp/buildd and pbuilder) may be used in this path. See RSL Substitions for a list of available
RSL substitutions. If this option is not present in the configuration file, then the job manager will create scratch directories as
subdirectories of the user's home directory.
-condor-arch ARCH
Set the condor architecture for this job manager to be the specified ARCH. This is optional when the job manager type is condor.
-condor-os OSNAME
Set the condor operating system name for this job manager to be the specified OSNAME. This is optional when the job manager type is
condor.
-globus-gatekeeper-host HOST
Set the name of the gatekeeper host. This will be made available in the GLOBUS_GATEKEEPER_HOST RSL substitution.
-globus-gatekeeper-port PORT
Set the TCP port of the gatekeeper. This will be made available in the GLOBUS_GATEKEEPER_PORT RSL substitution.
-globus-gatekeeper-subject SUBJECT
Set the GSI subject name of the gatekeeper. This will be made available in the GLOBUS_GATEKEEPER_SUBJECT RSL substitution.
-globus-host-manufacturer MANUFACTURER
Set the manufacturer name of the host machine. This will be made available in the GLOBUS_HOST_MANUFACTURER RSL substitution.
-globus-host-cputype CPUTYPE
Set the cpu type of the host machine. This will be made available in the GLOBUS_HOST_CPUTYPE RSL substitution.
-globus-host-osname OSNAME
Set the operating system name of the host machine. This will be made available in the GLOBUS_HOST_OSNAME RSL substitution.
-globus-host-osversion OSVERSION
Set the operating system version of the host machine. This will be made available in the GLOBUS_HOST_OSVERSION RSL substitution.
-globus-tcp-port-range RANGE
Set the range of TCP port numbers which the job manager will use. This will also be made available in the GLOBUS_TCP_PORT_RANGE
environment variable and RSL substitution.
-globus-tcp-source-range RANGE
Set the range of TCP source port numbers which the job manager will use. This will also be made available in the
GLOBUS_TCP_SOURCE_RANGE environment variable and RSL substitution.
-state-file-dir PATH
Set the path to store job manager state files (used for restarting a job manager which fails). If this is not set, then job state files
will be stored in the $GLOBUS_LOCATION/tmp/gram_job_state directory.
-x509-cert-dir PATH
Set the path to the X.509 trusted certificate directory on the job execution hosts. If not present, then the trusted certificate
directory used by the job manager (usually set by the Gatekeeper) will be used
-seg-module MODULE
Use the named module as a way to interact with the scheduler instead of polling for job status.
-audit-directory DIRECTORY
Store job auditing records in DIRECTORY. This directory should be sticky and group writable but not group readable. Audit records can
be uploaded to a database by using the globus-gram-audit command.
-globus-toolkit-version VERSION-STRING
Use the string VERSION-STRING as the toolkit version in audit records.
-enable-syslog
Send log messages to the system log.
-stdio-log LOG_DIRECTORY
Obsolete way to set the directory for writing log messages. Messages will be written to LOG_DIRECTORY/gram_DATE.log. Use -log-pattern
instead
-log-pattern PATTERN
RSL-substituted pattern for naming log files. Possible variables are HOME, LOGNAME, DATE. The -stdio-log is equivalent to -log-pattern
/tmp/buildd/gram_.log
-log-levels [FATAL|ERROR|WARN|DEBUG|INFO|TRACE]
List of log levels to enable site-wide. These may be joined by the '|' character.
Version 13.33 Mon Apr 30 2012 globus_gram_job_manager_configuration(3)