mirror of
https://github.com/xcat2/confluent.git
synced 2026-07-27 08:17:30 +00:00
Laurence
00a772785d
These commands ship in confluent_client/bin but had no .ronn man page, so they did not appear in the generated documentation. Add man pages matching the existing style, with synopsis and options taken from each command's argument parser: - confluent2ansible: export node inventory to an Ansible hosts file - confluent2lxca: export nodes to a Lenovo XClarity Administrator bulk import CSV - confluent2xcat: export nodes to an xCAT stanza definition (and optional macs.csv) - dir2img: build a FAT image from a directory for nodemedia upload - nodecertutil: manage BMC CA certificates and sign BMC certificates - nodegrouprename: rename a node group - noderename: rename nodes
35 lines
923 B
Markdown
35 lines
923 B
Markdown
noderename(8) -- Rename nodes in the confluent management service
|
|
=================================================================
|
|
|
|
## SYNOPSIS
|
|
|
|
`noderename <noderange> <newname>`
|
|
|
|
## DESCRIPTION
|
|
|
|
`noderename` changes the name of the node or nodes matched by the given
|
|
noderange to `<newname>`. As with other attribute changes, the rename is
|
|
applied through the confluent datastore and does not by itself alter the
|
|
operating system hostname of a running node.
|
|
|
|
When renaming more than one node, `<newname>` is normally an expression so that
|
|
each matched node receives a distinct name (see noderange(5) and the attribute
|
|
expression syntax).
|
|
|
|
## OPTIONS
|
|
|
|
* `-h`, `--help`:
|
|
Show help message and exit
|
|
|
|
## EXAMPLES
|
|
|
|
* Rename a single node:
|
|
`# noderename n1 n2`
|
|
|
|
* Rename a range of nodes using an expression:
|
|
`# noderename n1-n4 'compute{n1}'`
|
|
|
|
## SEE ALSO
|
|
|
|
nodedefine(8), noderemove(8), nodeattrib(8), noderange(5)
|