There is a node state of "FUTURE" that may satisfy your needs. This is
from "man slurm.conf":
FUTURE Indicates the node is defined for future use and need not
exist when the SLURM daemons are started. These nodes can be made
available for use simply by updating the node state using the
scontrol command rather than restarting the slurmctld daemon. After
these nodes are made available, change their State in the slurm.conf
file. Until these nodes are made available, they will not be seen
using any SLURM commands or Is nor will any attempt be made to contact
them.
Quoting Jonathan Stoppani <[email protected]>:
Hi,
I'm developing a virtualization layer to dynamically feed virtual
nodes to SLURM, based on user requests. These nodes can be virtual
machines running on physical nodes of a cluster or come from cloud
computing service providers or what else you can imagine....
Once the node (running slurmd) is up and running, I add the relevant
configuration entry to the SLURM configuration file and issue an
"scontrol reconfigure" command for the controller to pick it up.
Are there better ways to dynamically manage nodes? Are there
reconfiguration consequences I should be aware of?
Thanks,
Jonathan
