Newly added nodes are automatically discovered and enabled. You can also 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.
Procedure
- Ensure that the node personality is
Unset. If not, 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.
Setting a node personality (specifically to worker universal or worker labeled(db2wh with portworx storage)) is actually adding a node to OpenShift and Portworx clusters.