clusterctl boot set

Set the boot configuration of a node set

Synopsis

Point the PXE service at a boot configuration for each node.

Without a path, the boot path rules of the cluster decide, which is what makes a reinstall a one-liner. A node matched by two rules is an error rather than a silent first match. A rule marked static writes a persistent link, as –persistent does; both need services.pxesrv.staticSuffix.

Before it asks, the command resolves every address, checks that each boot path exists on the PXE host, and refuses a one-shot path for a node that has a persistent one. The question lists each boot path with its nodes.

Every node is tried, and each one’s result is listed; a node that failed or was not reported fails the command.

clusterctl boot set -n exe[1-4] clusterctl boot set -n exe0001 /srv/pxesrv/boot/cluster/1.0/exe/ipxe.net2

clusterctl boot set [NODESET] [PATH] [flags]

Options

  -h, --help         help for set
      --persistent   keep the boot path after the first request (needs services.pxesrv.staticSuffix)

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 boot set