Skip to content
Snippets Groups Projects
Commit f67c5874 authored by Moe Jette's avatar Moe Jette
Browse files

Minor revisions based upon code development. Default, Rootkey, and Shared 

partition information now to take values YES or NO. - Jette
parent b5c60582
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
doc/html/admin.guide.html
+ 42
− 37
View file @ f67c5874
...@@ -102,10 +102,25 @@ considered adjacent in the computer. ...@@ -102,10 +102,25 @@ considered adjacent in the computer.
<dd>Number of processors on the node (e.g. "2"). The default <dd>Number of processors on the node (e.g. "2"). The default
value is 1. value is 1.
<dt>Feature
<dd>A comma delimited list of arbitrary strings indicative of some
characteristic associated with the node.
There is no value associated with a feature at this time, a node
either has a feature or it does not.
If desired a feature may contain a numeric component indicating,
for example, processor speed.
By default a node has no features.
<dt>RealMemory <dt>RealMemory
<dd>Size of real memory on the node in MegaBytes (e.g. "2048"). <dd>Size of real memory on the node in MegaBytes (e.g. "2048").
The default value is 1. The default value is 1.
<dt>State
<dd>State of the node with respect to the initiation of user jobs.
Acceptable values are "UNKNOWN", "IDLE", "BUSY", "DOWN", "DRAINED",
"DRAINING". For example, the SLURM control machine may very well
not be used for initiation of user jobs and its state could thus
be set to "DRAINED". The default value is "UNKNOWN".
<dt>TmpDisk <dt>TmpDisk
<dd>Total size of temporary disk storage in TMP_FS in MegaBytes <dd>Total size of temporary disk storage in TMP_FS in MegaBytes
(e.g. "16384"). TMP_FS (for "Temporary File System") (e.g. "16384"). TMP_FS (for "Temporary File System")
...@@ -120,21 +135,6 @@ The PROLOG and/or EPILOG programs (specified at build time) might ...@@ -120,21 +135,6 @@ The PROLOG and/or EPILOG programs (specified at build time) might
be used to insure the file system is kept clean. be used to insure the file system is kept clean.
The default value is 1. The default value is 1.
<dt>State
<dd>State of the node with respect to the initiation of user jobs.
Acceptable values are "UNKNOWN", "IDLE", "BUSY", "DOWN", "DRAINED",
"DRAINING". For example, the SLURM control machine may very well
not be used for initiation of user jobs and its state could thus
be set to "DRAINED". The default value is "UNKNOWN".
<dt>Feature
<dd>A comma delimited list of arbitrary strings indicative of some
characteristic associated with the node.
There is no value associated with a feature at this time, a node
either has a feature or it does not.
If desired a feature may contain a numeric component indicating,
for example, processor speed.
By default a node has no features.
</dl> </dl>
<p> <p>
Only the NodeName must be supplied in the configuration file; all other Only the NodeName must be supplied in the configuration file; all other
...@@ -167,13 +167,6 @@ The size of each line in the file is limited to 1024 characters. ...@@ -167,13 +167,6 @@ The size of each line in the file is limited to 1024 characters.
<p> <p>
The node states have the following meanings: The node states have the following meanings:
<dl> <dl>
<dt>UNKNOWN
<dd>Default initial node state upon startup of SLURM.
An attempt will be made to contact the node and acquire current state information.
<dt>IDLE
<dd>The node is idle and available for use.
<dt>BUSY <dt>BUSY
<dd>The node has been allocated work (one or more user jobs) and is <dd>The node has been allocated work (one or more user jobs) and is
processing it. processing it.
...@@ -184,18 +177,26 @@ DOWN or failed to respond to system state inquiries or has ...@@ -184,18 +177,26 @@ DOWN or failed to respond to system state inquiries or has
explicitly removed itself from service due to a failure. This state explicitly removed itself from service due to a failure. This state
typically indicates some problem requiring administrator intervention. typically indicates some problem requiring administrator intervention.
<dt>DRAINING
<dd>The node has been made unavailable for new work by explicit administrator
intervention. It is processing some work at present and will enter state
"DRAINED" when that work has been completed. This might be used to
prepare some nodes for maintenance work.
<dt>DRAINED <dt>DRAINED
<dd>The node is idle, but not available for use. The state of a node <dd>The node is idle, but not available for use. The state of a node
will automatically change from DRAINING to DRAINED when user job(s) executing will automatically change from DRAINING to DRAINED when user job(s) executing
on that node terminate. Since this state is entered by explicit on that node terminate. Since this state is entered by explicit
administrator request, additional SLURM administrator intervention is typically administrator request, additional SLURM administrator intervention is typically
not required. not required.
<dt>DRAINING
<dd>The node has been made unavailable for new work by explicit administrator
intervention. It is processing some work at present and will enter state
"DRAINED" when that work has been completed. This might be used to
prepare some nodes for maintenance work.
<dt>IDLE
<dd>The node is idle and available for use.
<dt>UNKNOWN
<dd>Default initial node state upon startup of SLURM.
An attempt will be made to contact the node and acquire current state information.
</dl> </dl>
<p> <p>
SLURM uses a hash table in order to locate table entries rapidly. SLURM uses a hash table in order to locate table entries rapidly.
...@@ -235,18 +236,20 @@ If at least one group associated with the user submitting the ...@@ -235,18 +236,20 @@ If at least one group associated with the user submitting the
job is in AllowGroups, he will be permitted to use this partition. job is in AllowGroups, he will be permitted to use this partition.
The default value is "ALL". The default value is "ALL".
<dt>MaxTime
<dd>Maximum wall-time limit for any job in minutes. The default
value is "UNLIMITED", which is represented internally as -1.
<dt>Default <dt>Default
<dd>If this keyword is set, jobs submitted without a partition <dd>If this keyword is set, jobs submitted without a partition
specification will utilize this partition. specification will utilize this partition.
Possible values are "YES" and "NO".
The default value is "NO".
<dt>MaxNodes <dt>MaxNodes
<dd>Maximum count of nodes which may be allocated to any single job, <dd>Maximum count of nodes which may be allocated to any single job,
The default value is "UNLIMITED", which is represented internally as -1. The default value is "UNLIMITED", which is represented internally as -1.
<dt>MaxTime
<dd>Maximum wall-time limit for any job in minutes. The default
value is "UNLIMITED", which is represented internally as -1.
<dt>Nodes <dt>Nodes
<dd>Comma separated list of nodes which are associated with this <dd>Comma separated list of nodes which are associated with this
partition. Node names may be specified using the <a href="#NodeExp"> partition. Node names may be specified using the <a href="#NodeExp">
...@@ -271,6 +274,8 @@ to the partition. ...@@ -271,6 +274,8 @@ to the partition.
The non-privileged user would not be able to submit jobs The non-privileged user would not be able to submit jobs
directly to this partition for lack of a key. directly to this partition for lack of a key.
Issued keys will remain valid for a single use only. Issued keys will remain valid for a single use only.
Possible values are "YES" and "NO".
The default value is "NO".
<dt>Shared <dt>Shared
<dd>Specify if more than one job may execute on each node in <dd>Specify if more than one job may execute on each node in
...@@ -307,8 +312,8 @@ The job may specify a particular PartitionName, if so desired, ...@@ -307,8 +312,8 @@ The job may specify a particular PartitionName, if so desired,
or use the system's default partition. or use the system's default partition.
<pre> <pre>
# Partition specifications # Partition specifications
PartitionName=batch MaxNodes=10 MaxTime=UNLIMITED Nodes=lx[10-30] RootKey PartitionName=batch MaxNodes=10 MaxTime=UNLIMITED Nodes=lx[10-30] RootKey=YES
PartitionName=debug MaxNodes=2 MaxTime=60 Nodes=lx[03-09] Default PartitionName=debug MaxNodes=2 MaxTime=60 Nodes=lx[03-09] Default=YES
PartitionName=class MaxNodes=1 MaxTime=10 Nodes=lx[31-32] AllowGroups=students PartitionName=class MaxNodes=1 MaxTime=10 Nodes=lx[31-32] AllowGroups=students
</pre> </pre>
<p> <p>
...@@ -530,8 +535,8 @@ NodeName=lx[01-02] State=DRAINED ...@@ -530,8 +535,8 @@ NodeName=lx[01-02] State=DRAINED
NodeName=lx[03-16] Feature=CoolDebugger NodeName=lx[03-16] Feature=CoolDebugger
# #
# Default partition specification # Default partition specification
PartitionName=batch MaxCpus=128 MaxTime=240 Nodes=lx[10-30] RootKey PartitionName=batch MaxCpus=128 MaxTime=240 Nodes=lx[10-30] RootKey=YES
PartitionName=debug MaxCpus=16 MaxTime=60 Nodes=lx[03-09] Default Shared=YES PartitionName=debug MaxCpus=16 MaxTime=60 Nodes=lx[03-09] Default=YES Shared=YES
PartitionName=class MaxCpus=16 MaxTime=10 Nodes=lx[31-32] AllowGroups=students PartitionName=class MaxCpus=16 MaxTime=10 Nodes=lx[31-32] AllowGroups=students
</pre> </pre>
...@@ -562,7 +567,7 @@ Remove node lx30 from service, removing jobs as needed: ...@@ -562,7 +567,7 @@ Remove node lx30 from service, removing jobs as needed:
<hr> <hr>
URL = http://www-lc.llnl.gov/dctg-lc/slurm/admin.guide.html URL = http://www-lc.llnl.gov/dctg-lc/slurm/admin.guide.html
<p>Last Modified February 12, 2002</p> <p>Last Modified February 15, 2002</p>
<address>Maintained by <a href="mailto:slurm-dev@lists.llnl.gov"> <address>Maintained by <a href="mailto:slurm-dev@lists.llnl.gov">
slurm-dev@lists.llnl.gov</a></address> slurm-dev@lists.llnl.gov</a></address>
</body> </body>
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment
Nutzungsbedingungen | Datenschutzerklärung | Barrierefreiheitserklärung