Maui Administrator's Guide

Maui Administrator's Guide - setres

setres command overview

setres [ARGUMENTS] <RESOURCE_EXPRESSION>

ARGUMENTS:

                [ -a <ACCOUNT_LIST> ]
                [ -c <CHARGE_SPEC> ]
                [ -d <DURATION> ]
                [ -e <ENDTIME> ]
                [ -E ]** // EXCLUSIVE
                [ -f <FEATURE_LIST> ]*
                [ -g <GROUP_LIST> ]
                [ -n <NAME> ]
                [ -o <OWNER> ]**
                [ -p <PARTITION> ]
                [ -q <QUEUE_LIST> ]* // (ie CLASS_LIST)
                [ -Q <QOSLIST> ]
                [ -r <RESOURCE_DESCRIPTION> ]
                [ -R <RESERVATION_PROFILE> ]**
                [ -s <STARTTIME> ]
                [ -T <TRIGGER> ]**
                [ -u <USER_LIST> ]
                [ -x <FLAGS> ]
* NOTE: only available in Maui 3.2 and higher.
* NOTE: only available in Moab 4.0 and higher.

Purpose

Reserve resources for use by jobs with particular credentials or attributes.

Access

This command can be run by level 1 and level 2 Maui administrators.

Parameters

Name Format Default Description

ACCOUNT_LIST <STRING>[:<STRING>]... [NONE] list of accounts that will be allowed access to the reserved resources

CHARGE_SPEC <ACCOUNT>[,<GROUP>[,<USER>]] [NONE] specifies which credentials will be accountable for unused resources dedicated to the reservation

CLASS_LIST <STRING>[:<STRING>]... [NONE] list of classes that will be allowed access to the reserved resource

DURATION [[[DD:]HH:]MM:]SS [[[DD:]HH:]MM:]SS duration of the reservation (not needed if ENDTIME is specified)

ENDTIME [HH[:MM[:SS]]][_MO[/DD[/YY]]]
or
+[[[DD:]HH:]MM:]SS [INFINITY] absolute or relative time reservation will end (not required if Duration specified)

EXCLUSIVE N/A N/A requests exclusive access to resources
FEATURE_LIST <STRING>[:<STRING>]... [NONE] list of node features which must be possessed by the reserved resources

FLAGS <STRING>[:<STRING>]... [NONE] list of reservation flags (See Managing Reservations for details)

GROUP_LIST <STRING>[:<STRING>]... [NONE] list of groups that will be allowed access to the reserved resources

NAME <STRING> name set to first name listed in ACL or SYSTEM if no ACL specified name for new reservation
OWNER <CREDTYPE><CREDID> where CREDTYPE is one of user, group, acct, class, or qos N/A specifies which credential is granted reservation ownership privileges
PARTITION <STRING> [ANY] partition in which resources must be located
QOS_LIST <STRING>[:<STRING>]... [NONE] list of QOS's that will be allowed access to the reserved resource

RESERVATION_
PROFILE existing reservation profile ID N/A requests that default reservation attributes be loaded from the specified reservation profile (see RSVPROFILE)
RESOURCE_
DESCRIPTION colon delimited list of zer or more of the following <ATTR>=<VALUE> pairs
PROCS=<INTEGER>
MEM=<INTEGER>
DISK=<INTEGER>
SWAP=<INTEGER> PROCS=-1 specifies the resources to be reserved per task. (-1 indicates all resources on node)

RESOURCE_
EXPRESSION
ALL
or
TASKS{==|>=}<TASKCOUNT>
or
<HOST_REGEX> Required Field. No Default specifies the tasks to reserve. ALL indicates all resources available should be reserved.
NOTE: if ALL or a host expression is specified, Maui will apply the reservation regardless of existing reservations and exclusitivity issues. If TASKS is used, Maui will only allocate accessible resources.

STARTTIME [HH[:MM[:SS]]][_MO[/DD[/YY]]]
or
+[[[DD:]HH:]MM:]SS [NOW] absolute or relative time reservation will start

TRIGGER <STRING> N/A comma delimited reservation trigger list following format described in the trigger format section of the reservation configuration overview.
USER_LIST <STRING>[:<STRING>]... [NONE] list of users that will be allowed access to the reserved resources

Description

The setres command allows an arbitrary block of resources to be reserved for use by jobs which meet the specifed access constraints. The timeframe covered by the reservation can be specified on either an absolute or relative basis. Only jobs with credentials listed in the reservation ACL (i.e., USERLIST, GROUPLIST,...) can utilize the reserved resources. However, these jobs still have the freedom to utilize resources outside of the reservation. The reservation will be assigned a name derived from the ACL specified. If no reservation ACL is specified, the reservation is created as a system reservation and no jobs will be allowed access to the resources during the specified timeframe (valuable for system maintenance, etc). See the Reservation Overview for more information.

Reservations can be viewed using the showres command and can be released using the releaseres command.

Example 1

Reserve two nodes for use by users john and mary for a period of 8 hours starting in 24 hours

% setres -u john:mary -s +24:00:00 -d 8:00:00 TASKS==2

reservation 'john.1' created on 2 nodes (2 tasks)

node001:1
node005:1

Example 2

Schedule a system wide reservation to allow a system maintenance on Jun 20, 8:00 AM until Jun 22, 5:00 PM.

% setres -s 8:00:00_06/20 -e 17:00:00_06/22 ALL

reservation 'system.1' created on 8 nodes (8 tasks)

node001:1
node002:1
node003:1
node004:1
node005:1
node006:1
node007:1
node008:1

Example 3

Reserve one processor and 512 MB of memory on nodes node003 through node 006 for members of the group staff and jobs in the interactive class

% setres -r PROCS=1:MEM=512 -g staff -l interactive 'node00[3-6]'

reservation 'staff.1' created on 4 nodes (4 tasks)

node003:1
node004:1
node005:1
node006:1

Related Commands

Use the showres command to view reservations.
Use the releaseres command to release reservations.
Use the diagnose -r command to analyze and present detailed information about reservations.