future will return resources available immediately and available in the future policy will apply charging policies to determine the total cost of each reported solution (NOTE: only enabled for XML responses) summary will assign all jointly allocated transactions as dependencies of the first transaction reported tid will associate a transaction id with the reported results verbose will return diagnostic information and response hostlists
show resources available to john in XML format with a transaction id
--xml
XML
--xml
report results in XML format
show resources available to john in XML format with a transaction id
-a
AVAILABLE RESOURCES
---
Display available resources
show resources available to john in XML format with a transaction id
-i
INTERSECTION
---
Specifies that an intersection should be performed during an mshow -a command with multiple requirements
-o
NO AGGREGATE
---
Specifies that the results of the command mshow -a with multiple requirements should not be aggregated together
-p
PROFILE
<VPCPROFILEID>
Specifies which virtual private cluster profile should be used to adjust the explicit constraints of the request
-T
TIMELOCK
---
Specifies that the multiple requirements of an mshow -a command should be timelocked
Add a "Where" clause to the current command. (Currently supports up to 6 co-allocation clauses)
-x
EXCLUSIVE
---
Specifies that the multiple requirements of an mshow -a command should be exclusive (ie. each node may only be allocated to a single requirement)
Table 2: Request Attributes
Name
Description
account
the account credential of the requestor
arch
select only nodes with the specified architecture
cal
select resources subject to the constraints of the specified global calendar
class
the class credential of the requestor
coalloc
the co-allocation group of the specific Where request (can be any string but must match co-allocation group of at least one other Where' request) NOTE: the number of tasks requested in each Where request must be equal whether this taskcount is specified via minprocs, mintasks, or gres.
count
the number of profiles to apply to the resource request
displaymode
constrain how results will be presented
duration
the duration for which the resources will be required in format [[[DD:]HH:]MM:]SS
gres
select only nodes which possess the specified generic resource
group
the group credential of the requestor
hostlist
select only the specified resources
job
use the resource, duration, and credential information for the job specified as a resource request template
jobfeature
select only resources which would allow access to jobs with the specified job features
jobflags
select only resources which would allow access to jobs with the specified job flags
label
associate the specified label with all results matching this request
minnodes
return only results with at least the number of nodes specified. If used with TID's, return only solutions with exactly minnodes nodes available
minprocs
return only results with at least the number of processors specified. If used with TID's, return only solutions with exactly minprocs processors available
mintasks
FORMAT: <TASKCOUNT>[@<RESTYPE>:<COUNT>[+<RESTYPE>:<COUNT>]...] where <RESTYPE> is one of procs, mem, disk, or swap. Return only results with at least the number of tasks specified. If used with TID's, return only solutions with exactly mintasks available
nodedisk
select only nodes with at least nodedisk MB of local disk configured
nodefeature
select only nodes with all specified features present using format <feature>[:<feature>]...
nodemem
select only nodes with at least nodemem MB of memory configured
offset
select only resources which can be co-allocated with the specified time offset where offset is specified in the format [[[DD:]HH:]MM:]SS
os
select only nodes with have, or can be provisioned to have, the specified operating system
partition
the partition in which the resources must be located
policylevel
enable policy enforcement at the specified policy constraint level
qos
the qos credential of the requestor
rsvprofile
use the specified profile if committing a resulting transaction id directly to a reservation
starttime
constrain the timeframe for the returned results by specifying one or more ranges using the format <STIME>[-<ENDTIME>][;<STIME>[-<ENDTIME>]] where each time is specified in the format in absolute, relative, or epoch time format ([HH[:MM[:SS]]][_MO[/DD[/YY]]] or +[[[DD:]HH:]MM:]SS or <EPOCHTIME>). NOTE: The starttime specified is not the exact time at which the returned range must start, but is rather the earliest possible time the range may start.
taskmem
require taskmem MB of memory per task located
tpn
require exactly tpn tasks per node on all discovered resources
user
the user credential of the requestor
var
use associated variables in generating per transaction charging quotes
Usage Notes
The mshow -a command allows for querying of available system resources. When combined with the --flags=tid option these available resources can then be placed into a "packaged" reservation (using mrsvctl -c -R) or vpc (using mschedctl -c vpc -R). This allows system administrators to grab and reserve available resources for whatever reason, without conflicting with jobs or reservations that may holding certain resources.
There are a few restrictions on which <ATTR> from the -w command can be placed in the same req: minprocs, minnodes, and gres are all mutually exclusive, only one may be used per -w request.
When the '-o' flag is not used, multi-request results will be aggregated. This aggregation will negate the use of offsets and request-specific starttimes.
The config parameter RESOURCEQUERYDEPTH controls the maximum number of options that will be returned in response to a resource query.
Example 1: Basic Compute Node Query and Reservation
Example 2: Mixed Processor and License Query
Select one node with 4 processors and 1 matlab license where the matlab
license is only available for the last hour of the reservation. Also, select 16
additional processors which are available during the same timeframe but which can be
located anywhere in the cluster. Group the resulting transactions together using
transaction dependencies so only the first transaction needs to be committed to reserve all associated resources.
Example 3: Request for Generic Resources
Query for a generic resource on a specific host (no processors, only a generic resource).
Example 4: Allocation of Shared Resources
This example walks through a relatively complicated example in which a set of resources can be reserved to be allocated for shared requests. In the example below, the first mshow query looks for resources within an existing shared reservation. In the example, this first query fails because there is now existing reservation. The second mshow requests asks for resources outside of a shared reservation and finds the desired resources. These resources are then reserved as a shared pool. The third mshow request again asks for resources inside of a shared reservation and this time finds the desired resources.
Example 5: Full Resource Query in XML Format
The following command will report information on all available resources which meet at least the minimum specified processor and walltime constraints and which are available to the specified user. The results will be reported in XML to allow for easy system processing.
NOTE: This command reports the original query, and the timeframe, resource size, and hostlist associated with each possible time slot.
