clusterctl bmc power

Change the power state of nodes

Synopsis

Change the power state of the nodes through their service processors.

status report the current state, changing nothing on power on off cut the power without asking the operating system soft ask the operating system to shut down cycle power off and on again reset reset without asking the operating system

Powering many nodes on at once trips rack breakers, so a power-on and a power cycle are sent in batches with a pause between them; both come from the configuration. A batch with a failure stops the run, and the nodes of the later batches are reported as not tried.

Each node is reached over the transports of bmc.order, or its vendor’s, in turn. An action falls back to the next transport only when the first provably never reached the service processor, because an action is never sent twice. Nodes with different accounts are sent to the IPMI backend separately.

Slurm is asked first, because powering off a running job loses it. A node that Slurm reports running a job, or cannot say about, is refused unless –lose-jobs is given; –force gets past a protected host, not this check.

clusterctl bmc power ACTION [NODESET] [flags]

Options

      --batch int          how many nodes to power on or cycle at once, at least 1 (default: from the configuration)
  -h, --help               help for power
      --ipmi               act over IPMI only, whatever bmc.order says
      --lose-jobs          go ahead although Slurm reports jobs on the nodes, or cannot say
      --stagger duration   pause between batches (default: from the configuration)

Options inherited from parent commands

      --config strings        configuration file or directory to read, repeatable (default: CLUSTERCTL_CONFIG or the search path)
      --context string        context to act on (default: the current one)
      --dry-run               report what would be done and change nothing
      --fanout int            how many hosts to work on at once, at least 1; caps the service processors and the names asked at once too, which fanout.max and CLUSTERCTL_FANOUT do not (default: from the configuration)
      --force                 allow protected hosts, and nodes the inventory does not know, to be touched
  -n, --nodes stringArray     node set to act on, for example 'exe[1-10],@rack:R02' (default: CLUSTERCTL_NODES)
  -o, --output string         output format: table, wide, json, yaml, nodeset, name, jq= (default "table")
      --progress string       how to show the progress of a command on standard error: auto, tty, counter, plain, none (default: CLUSTERCTL_PROGRESS, else auto, a live tree when standard error is a terminal; plain writes lines for a log)
      --progress-log string   append the progress events of a command to this file, one JSON object per line, created readable by you alone (default: CLUSTERCTL_PROGRESS_LOG; an empty one writes none)
      --set stringArray       override one configuration value as PATH=VALUE, repeatable
  -y, --yes                   answer the confirmation prompts with yes

clusterctl bmc power