Main Page   Related Pages  

GRAM Reporter Scheduler Interface

The GRAM reporter interfaces with the job scheduler through a scheduler-specific script. The GRAM reporter will execute the scheduler script and will read the scripts STDOUT looking for lines prefixed with a special string. The strings are either "GRAM_SCRIPT_Q:" or "GRAM_SCRIPT_QE:". A single GRAM job manager service can submit job's to a scheduler targeting more than one queue. Likewise, the GRAM reporter can publish more than one queue object under the Job Manager's object in the MDS.
GRAM_SCRIPT_Q: <attribute> <value>
This reporter expects first a "startqueue" value to signal the start of a set of attributes that will define the queue. Then and "endqueue" value to signal the end. In between, the valid attributes are list below. Defaults for all attributes with an N value is 0. Defaults for all attributes with a String value is NULL (except for queuename).
maxtime N <\b>
The maximum amount of time (minutes) for a job
maxcount N <\b>
The maximum number of processes for a job
maxcputime N <\b>
The maximum amount of cputime (minutes) for a job
maxrunningjobs N <\b>
The maximum number of active jobs for all users
maxjobsinqueue N <\b>
The maximum number of jobs a user can have in a queue
maxtotalmemory N <\b>
The maximum amount of memory for all nodes in this queue
maxsinglememory N <\b>
The maximum amount of memory for a single node in this queue
totalnodes N <\b>
The number of nodes in this queue
freenodes N <\b>
The number of free nodes in this queue
queuename String <\b>
The name of the queue. Default "default"
whenactive String <\b>
Statement of when this queue is active
status String <\b>
the status of the queue. Up or Down
dispatchtype String <\b>
Either Batch or Immediate (fork)
priority String <\b>
queue's priority: High, Medium, Low, ...
alloweduserlist String <\b>
users given priveledge to submit jobs to the queue
jobwait String <\b>
the wait time for jobs in the queue
schedulerspecific String <\b>
put info here that does not fit into the above attributes

GRAM_SCRIPT_QE: <attribute> <value>
This reporter expects first a "startqueue" value to signal the start of a set of attributes that will define the queue. Then and "endqueue" value to signal the end. In between, the valid attributes are list below. Defaults for all attributes with an N value is 0. Defaults for all attributes with a String value is NULL (except for queuename).
localjobid String
The local schedulers job id for this job
localusername String
The submittors username local to this host
count N
The number of processes requested by this job
status String
The GRAM status for the job: ACTIVE, PENDING, DONE, ...
starttime String
The Actual or expected start time for the job
elapsedtime String
The elapsed time for the job
finishtime String
The finish time for the job
requestedmemory N
The number of MegaBytes requested by the job
requestedtime N
The user requested start time for the job
schedulerspecific String
put info here that does not fit into the above attributes


about globus | grid research | globus toolkit | software development

Comments? webmaster@globus.org