W.1 Moab Resource Manager Language Data Format

W.1.1 Query Resources Data Format

NAME FORMAT DEFAULT DESCRIPTION
<INTEGER> 0 Available local disk on node (in MB)
<fs id="X" size="X" io="Y" rcount="X" wcount="X" ocount="X"></fs>[...] 0 Available filesystem state
<INTEGER> 0 Available/free RAM on node (in MB)
<INTEGER> 1 Available processors on node
<STRING> --- Compute architecture of node
one or more comma delimited <NAME>:<VALUE> pairs (ie, MATLAB:6,COMPILER:100) --- Arbitrary consumable resources currently available on the node
<INTEGER> 0 Available swap on node (in MB)
one or more bracket enclosed <NAME>:<COUNT> pairs (ie, [batch:5][sge:3]) --- Run classes supported by node. Typically, one class is 'consumed' per task. Thus, an 8 processor node may have 8 instances of each class it supports present, ie [batch:8][interactive:8]
<INTEGER> 0 Configured local disk on node (in MB)
<STRING> 0 Configured filesystem state
<INTEGER> 0 Configured RAM on node (in MB)
<STRING> --- The physical machine that is hosting the virtual machine. Only valid on VMs.
<INTEGER> 1 Configured processors on node
<DOUBLE> 0.0 One minute BSD load average
<INTEGER> --- The node's processor speed in MHz
one or more comma delimited <NAME>:<VALUE> pairs (ie, MATLAB:6,COMPILER:100) --- Arbitrary consumable resources supported and tracked on the node, ie software licenses or tape drives
<INTEGER> 0 Configured swap on node (in MB)
<INTEGER> 0 Number of tasks currently active on the node
one or more colon delimited <STRING>'s (ie, WIDE:HSM) --- Generic attributes, often describing hardware or software features, associated with the node
GEVENT[<EVENTNAME>]=<STRING> --- Generic event occurrence and context data
GMETRIC[<METRICNAME>]=<DOUBLE> --- Current value of generic metric, i.e., 'GMETRIC[temp]=103.5'.
<INTEGER> --- Number of seconds since last detected keyboard or mouse activity (often used with desktop harvesting)
<INTEGER> <CPROC> Maximum number of tasks allowed on the node at any given time
<STRING> --- The IP address of the machine
<INTEGER> --- The node's index
<STRING> --- Operating system running on node
One or more comma delimited <STRING>'s with quotes if the strIng has spaces (ie. "SAS7 AS3 Core Baseline Build v0.1.0","RedHat AS3-U5Development Build v0.2"). --- Operating systems accepted by node
<ATTR>=<VALUE>[,<ATTR>=<VALUE>]... --- Opaque node attributes assigned to node
<STRING> DEFAULT Partition to which node belongs
<BOOLEAN>   Whether the machine is on or off
<INTEGER> --- Node allocation priority
<INTEGER> 0 Rack location of the node
<INTEGER> 0 Slot location of the node
<DOUBLE> 1.0 Relative processor speed of the node. For more information, see Node Attributes Speed
one of the following: Idle, Running, Busy, Unknown, Drained, Draining, or Down Down State of the node
<EPOCHTIME> 0 Time node information was last updated
<ATTR1>=<VAL1>[+<ATTR2>=<VAL2>]... --- Plus-delimited (+) list of <ATTR>=<VAL> pairs that jobs can request
<ATTR>=<VAL> --- Generic variables to be associated with node
<STRING> --- Comma-delimited list (,) of supported virtual machine operating systems for this node
one or more comma delimited <NAME>:<VALUE> pairs (ie, MATLAB:6,COMPILER:100) --- Amount of external usage of a particular generic resource

* indicates required field

Note: node states have the following definitions:

Node is running some jobs and will not accept additional jobs
Resource Manager problems have been detected. Node is incapable of running jobs.
Node is responding but will not accept new jobs
Node is ready to run jobs but currently is not running any.
Node is running some jobs and will accept additional jobs
Node is capable of running jobs but the scheduler will need to determine if the node state is actually Idle, Running, or Busy.

W.1.2 Query Workload Data Format

NAME FORMAT DEFAULT DESCRIPTION
<STRING> --- AccountID associated with job
<STRING> --- job command-line arguments
<STRING> 0 job resource manager extension arguments including qos, dependencies, reservation constraints, etc
<EPOCHTIME> 0 time job completed execution
<INTEGER> 0 quantity of local disk space (in MB) which must be dedicated to each task of the job
name:value[,name:value] --- Dedicated generic resources per task.
<INTEGER> 1 number of processors dedicated per task
<INTEGER> 0 quantity of virtual memory (swap, in MB) which must be dedicated to each task of the job
<EPOCHTIME> [ANY] time by which job must complete
<STRING> --- job environment variables
<STRING> --- file to contain STDERR
<EVENT> --- event or exception experienced by job
<STRING> --- job executable command
<INTEGER> --- job exit code
<STRING> --- job flags
<STRING> --- String describing task geometry required by job
<STRING> --- GroupID under which job will run
comma or colon delimited list of hostnames -
suffix the hostlist with a carat (^) to mean superset; suffix with an asterisk (*) to mean subset; otherwise, the hostlist is interpreted as an exact set
[ANY] list of required hosts on which job must run. (see TASKLIST)
<STRING> --- file containing STDIN
<STRING> --- job's initial working directory
<STRING> --- User specified name of job
<INTEGER> 1 Number of nodes required by job (See Node Definition for more info)
<STRING> --- file to contain STDOUT
one or more colon delimited <STRING>s [ANY] list of partitions in which job can run
colon delimited list of <STRING>s --- List of preferred node features or variables. (See PREF for more information.)
<INTEGER> --- system priority (absolute or relative - use '+' and '-' to specify relative)
<INTEGER> 0 quality of service requested
<EPOCHTIME> 0 time job was submitted to resource manager
<STRING> --- architecture required by job
list of bracket enclosed <STRING>:<INTEGER> pairs --- list of <CLASSNAME>:<COUNT> pairs indicating type and number of class instances required per task. (ie, '[batch:1]' or '[batch:2][tape:1]')
<INTEGER> 0 local disk space (in MB) required to be configured on nodes allocated to the job
one of '>=', '>', '==', '<', or '<=' >= local disk comparison (ie, node must have > 2048 MB local disk)
<INTEGER> 0 reason job was rejected
<INTEGER> 0 number of times job was rejected
<STRING> --- text description of reason job was rejected
<STRING> --- Name of reservation in which job must run
<STRING> --- List of reservations in which job can run
colon delimited list <STRING>'s --- List of features required on nodes
<INTEGER> 0 real memory (RAM, in MB) required to be configured on nodes allocated to the job
one of '>=', '>', '==', '<', or '<=' >= real memory comparison (ie, node must have >= 512MB RAM)
<STRING> --- operating system required by job
<RESTYPE>[{+|:}<COUNT>]
[@<TIMEFRAME>]
--- software required by job
<INTEGER> 0 virtual memory (swap, in MB) required to be configured on nodes allocated to the job
one of '>=', '>', '==', '<', or '<=' >= virtual memory comparison (ie, node must have ==4096 MB virtual memory)
<STRING> --- system id (global job system owner)
<EPOCHTIME> 0 earliest time job should be allowed to start
<EPOCHTIME> 0 time job was started by the resource manager
one of Idle, Running, Hold, Suspended, Completed, or Removed Idle State of job
<INTEGER> 0 Number of seconds job has been suspended
one or more comma-delimited <STRING>'s --- list of allocated tasks, or in other words, comma-delimited list of node ID's associated with each active task of job (i.e., cl01, cl02, cl01, cl02, cl03) The tasklist is initially selected by the scheduler at the time the StartJob command is issued. The resource manager is then responsible for starting the job on these nodes and maintaining this task distribution information throughout the life of the job. (see HOSTLIST)
<INTEGER> 1 Number of tasks required by job (See Task Definition for more info)
<INTEGER> 0 exact number of tasks required per node
<STRING> --- UserID under which job will run
<EPOCHTIME> 0 Time job was last updated
[[HH:]MM:]SS 864000 walltime required by job

* indicates required field

Note: Job states have the following definitions:

Job has completed
Job is in the queue but is not allowed to run
Job is ready to run
Job has been canceled or otherwise terminated externally
Job is currently executing
job has started but execution has temporarily been suspended

Note: Completed and canceled jobs should be maintained by the resource manager for a brief time, perhaps 1 to 5 minutes, before being purged. This provides the scheduler time to obtain all final job state information for scheduler statistics.

See Also

Copyright © 2012 Adaptive Computing Enterprises, Inc.®