Power Commands
Once you reservation is active (i.e., it has a green background on your igor show list), you can issue power commands to its nodes.
$ igor power {on|off|cycle} {-r RESNAME | -n NODES}
Unless otherwise specified, nodes will immediately begin a power cycle operation when the reservation becomes active, thus no power command is necessary for start up. Future reservations cannot accept power commands because you don’t own the hosts until your reservation is running.
Power cycling will turn node power off and back on again, ensuring that hosts boot for the first time with the image specified by the reservation distro.
Optionally, you can use the -n flag to specify any nodes for which you belong to an active reservation. This not only allows you to run power commands on a subset of hosts, but also on hosts spanning multiple reservations. For example, you might have two reservations connected to the same VLAN and you want to reboot a selection of nodes on each one at the same time.
Examples:
$ igor power cycle -r MyCoolRes
$ igor power cycle -n kn[1,5,27]
Did My Power Command Work?
Power commands are routed through Igor to an external IPMI service that tells Igor immediately if the command was successfully submitted. The actual booting of a host can fail for many other reasons. Attempts to power command a node should therefore be followed up with close monitoring to check that the boot completed, sometimes taking as long as a few minutes before the power status changes.
Group Member Power Commands
If a reservation is attached to a group, then all members of the group will have the ability to use power commands on nodes in the reservation.
Early Termination
If you are finished with a reservation before it expires, it is recommended that once you have saved off any data or other files you intend to keep that you delete your reservation early. This allows other users to take advantage of nodes that are no longer being used.
Group members also have the ability to delete a reservation.