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

Add more documentation on node naming.

parent 1d9b1356
No related branches found
No related tags found
No related merge requests found
...@@ -271,7 +271,14 @@ for the host "mcri". Port numbers to be used for ...@@ -271,7 +271,14 @@ for the host "mcri". Port numbers to be used for
communications are specified as well as various timer values.</p> communications are specified as well as various timer values.</p>
<p>A description of the nodes and their grouping into partitions is required. <p>A description of the nodes and their grouping into partitions is required.
Nodes can be in more than one partition and each partition can have different Node names can have up to three names specifications:
<b>NodeName</b> is the name used in all SLURM tools when referring to the node,
<b>NodeAddr</b> is the name or IP address SLURM uses to communicate with the node, and
<b>NodeHostname</b> is the name returned by the command <i>/bin/hostname -s</i>.
Only <b>NodeName</b> is required, although by supporting all three parameters
provides complete control over naming and addressing the nodes.</p>
<p>Nodes can be in more than one partition and each partition can have different
constraints (permitted users, time limits, job size limits, etc.). constraints (permitted users, time limits, job size limits, etc.).
Each partition can thus be considered a separate queue. Each partition can thus be considered a separate queue.
Partition and node specifications use node range expressions to identify Partition and node specifications use node range expressions to identify
......
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