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

Clarify resetting a node's state and reason in the configuration file.

parent 7cfb033a
No related branches found
No related tags found
No related merge requests found
...@@ -265,6 +265,11 @@ of larger clusters. ...@@ -265,6 +265,11 @@ of larger clusters.
In order to support the concept of jobs requiring consecutive nodes In order to support the concept of jobs requiring consecutive nodes
on some architectures, on some architectures,
node specifications should be place in this file in consecutive order. node specifications should be place in this file in consecutive order.
If a specific node name is listed more than once in the configuration
file only its "State" and "Reason" fields may be reset.
This may be useful to record the state of nodes which are temporarily
in a DOWN or DRAINED state without altering permanent configuration
information as shown in the example.
The node configuration specifies the following information: The node configuration specifies the following information:
.TP .TP
\fBNodeName\fR \fBNodeName\fR
...@@ -507,7 +512,9 @@ NodeName=DEFAULT State=UNKNOWN ...@@ -507,7 +512,9 @@ NodeName=DEFAULT State=UNKNOWN
.br .br
NodeName=dev[0-25] NodeAddr=edev[0-25] Weight=16 NodeName=dev[0-25] NodeAddr=edev[0-25] Weight=16
.br .br
NodeName=dev26 State=DOWN Reason="power,ETA=Dec25" # Update records for specific DOWN nodes
.br
NodeName=dev20 State=DOWN Reason="power,ETA=Dec25"
.br .br
# #
.br .br
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment