Naming a Node
A node can be named, by means of the REST API.
Names and, if required, renames an individual node. This API is therefore used as part of the node-provisioning process, and can also be used or reused subsequent to all other aspects of node-provisioning, including specification of username and password for the Full Administrator. However, the API can only be used while the node constitutes a single-node cluster: once the node has become part of a multi-node cluster, the API can no longer be used.
curl -X POST -u <username>:<password> \ http://<ip-address-or-domain-name>:8091/node/controller/rename \ -d hostname=<name>
password need only be specified if credentials have been configured for the administrator, as described in Establishing Credentials.
name argument must be one of the following:
The IP address of the underlying host (either IPv4 or IPv6).
A fully qualified hostname that corresponds, in the appropriate network maps, to the IP address of the underlying host.
The loopback address,
Failure to specify the
name argument correctly returns
400 Bad Request, and a message such as the following:
["Could not listen on address \"10.144.220.107\": eaddrnotavail"].
If a username and password have already been assigned, failure to authenticate returns
An incorrectly expressed URI or flag returns
404 Object Not Found.
The following example specifies the IP of the underlying host as the name of the node.
curl -X POST -u Administrator:password \ http://10.144.220.101:8091/node/controller/rename \ -d hostname='10.144.220.101'
The sequence of tasks divided into initialization and provisioning is explained in Cluster Initialization and Provisioning.
For general information on naming, see Naming Clusters and Nodes.
For further information on initialization and provisioning — using the UI, the CLI, and the REST API — see Manage Nodes and Clusters.