Adding new nodes to the system

When you add new nodes to the system physically, they are automatically discovered and enabled. You can then assign the personality to the new nodes to define their role in the system.

Before you begin

Hardware expansion, if needed, is performed by IBM installers.
If you are planning to use the newly added nodes for Netezza, there is no need to set their personality with this procedure. Instead, follow the instructions in Installing Netezza Performance Server for Cloud Pak for Data System.

Table 1. Node personalities
Node personality	Personality reported by platform manager	Description
Control Node	`control`	Three servers in a system are always assigned a control role and these three nodes are designated as a Control Plane. These servers are candidates for a Platform Manager hub. They host one Control Virtual Machine. The control plane nodes manage your cluster and your Cloud Pak for Data deployment. At least two of the three control nodes must be operational for the system to work.
Worker Node - Universal	`worker`	Compute node. Can host one or more Cloud Pak for Data Worker Virtual Machines. Can host any service, container, or pod as designated by Cloud Pak for Data.
Worker Node - Labeled	`worker <labelX>`	Compute node. A dedicated VM to host only a specific pod or application designated by Label.
Db2® Warehouse Node	`DB2WH`	A node dedicated to host Db2 Warehouse SMP in Red Hat® OpenShift®.
NPS Node	`NPS`	Compute node dedicated to Netezza Performance Server Note: Nodes in this role are not managed by Platform Manager, hence their state is always UNMANAGED.
Unset Node	`Unset`	A node with no personality assigned.

Procedure

Ensure that the node personality is Unset by running the ap node command. If not Unset, as root, from e1n1, run:
```
ap node set_personality <node> Unset
```
Example:
```
ap node set_personality  enclosure2.node3 Unset
```
It might take several minutes to change the role to Unset. You can verify it by running the ap node command.
Run the following command to set the personality of the node to worker:
```
ap node set_personality <node> worker
```
Example:
```
ap node set_personality  enclosure2.node3 worker
```
You can set the personality for multiple nodes at a time by providing a comma separated list of nodes. It is recommended not to modify more than 4 nodes at a time.
```
ap node set_personality <node1>,<node2>,<node3>,<node4> Worker 
```
Example:
```
ap node set_personality  enclosure2.node3, enclosure2.node4, enclosure3.node1, enclosure3.node2 Worker
```
The personality value is provided as <roleX>, or <roleX>[<labelX>]. The latter should be used only when the label is not blank. If a node has more than one role, both roles must be provided as a comma-separated list, for example: <roleX>,<roleY>, or <roleX>[<labelX>],<roleY>[<labelY>]

Results

You can verify that the command ran successfully by running the ap node command.