Configuring nodes for management
How to configure the newly installed nodes so that they are monitored and added to the OpenShift cluster. For nodes that contribute to storage, add them to the storage cluster.
Before you begin
Meet the following prerequisites for all node types in the specified sequence:
- Ensure switches are in healthy state and connections between node and switches are correct.
- The purchased quantity of nodes are delivered to your location with the following information:
- For Compute-storage nodes, the received new node must have a specific number of NVMe drives. That is, the new node must have the same number of disks as the ones that are already there.
- All new nodes must have a MAC address from IBM.Note: Update your Dynamic Host Configuration Protocol (DHCP) and Domain Name System (DNS) Configuration to include reservations for all nodes in the IBM Fusion HCI. For more information about the prerequisite, see Setting up DHCP for IBM Fusion HCI and Setting up DNS. In case of Static IP, you must update the DNS for the new nodes. For more information about the prerequisites, see Setting up Static IP and Setting up DNS. These configurations are based on the MAC addresses shared with you by IBM.
- Ensure that the IBM Support Representative inserted the nodes in the appropriate rack slots and connected the network and power cables as per the wiring prescription of IBM Fusion HCI rack.
- The IBM Fusion appliance is up and running.
- Red Hat® OpenShift® is up and running and the existing nodes are healthy.
- When you add a node to Red Hat OpenShift, the operation might get stuck for a long time in the node network configuration policy creation stage. To avoid this issue, do the steps that are mentioned in the troubleshooting section before you add the node. For the workaround steps, see Node issues.
- Naming convention of nodes that are added:
compute-<rackid>-<rack unit number>.<domainname>For a single rack, the rackid is always 1. For multi-rack, rackid is the rack number where the node is added. For an example guidance for the base system, see host name conventions.
- Upsizing when backup or restore is in progress
- When a backup or restore job is in progress, you must not upsize the nodes. For scale-out or scale-up operation, turn off the IBM Fusion backup or restore jobs, if any. Do not back up or restore when an upsize action is in progress.
- Upsize nodes to brand-new racks
-
- Upsize node must be powered on only on a running IBM Fusion HCI (stage 2 complete). Otherwise, keep the upsized node powered off (remove the power cables from the node).
- Complete the installation.
- Plug-in the power and switch on the node.
About this task
- The following node types are supported in this release:
- Compute-only and compute-storage server model servers are 9155-C10 (32 core node), 9155-C14 (64 core node), 9155-D10 (32 core node), 9155-D14 (64 core node).
- 9155-G03 and 9155-DG1 for GPU node.
- In IBM Fusion HCI rack, when nodes are added they must be added into the lowest available rack position to maintain mechanical stability.
- Allowed node configuration combinations for high-availability multi-rack:
- Select same number of nodes from all three racks. A minimum of three nodes are required for the configuration.
- For scale out, add an equal number of storage nodes from each rack.
- For scale up, add same number of disks across each rack.
Note: Do not deviate from these specification as it can result in an imbalanced configuration of a Data Foundation cluster.