ON THIS PAGE
Add Worker Nodes
Use the instructions provided in this topic to add additional worker nodes to your Routing Director deployment cluster.
A typical Routing Director deployment cluster has a minimum of four nodes with three primary and worker nodes and one worker-only node. If your deployment is running out of CPUs, memory, and/or disk space, or you are deploying more applications or scaling existing ones, you may have to increase your compute resources. You can add additional worker nodes to your existing Routing Director deployment cluster using Deployment Shell. Additional nodes help distribute workloads and also reduce the impact of a single node failure.
You must prepare and configure the additional nodes before you add it to the cluster.
Prepare the Node
To prepare a node you must create and configure the node VM.
Download the OVA bundle, or the OVF and .vmdk bundle onto your computer.
Log in to the hypervisor server where have installed Routing Director.
Create the node VM.
Depending on your hypervisor, perform the steps described in the following sections to create the VM.
Configure the node VM
Perform the following steps to configure the node VM.
Connect to the node VM console. You are logged in as root automatically.
You are prompted to change your password immediately. Enter and re-enter the new password. You are automatically logged out of the VM.
Note:We recommend that you enter the same password for as the VMs in your existing cluster.
When prompted, log in again as root user with the newly configured password.
Configure the following information when prompted.
Table 1: VM Configuration Wizard Prompt
Action
Do you want to set up a Hostname? (y/n)
Enter y to configure a hostname.
Please specify the Hostname
Enter an identifying hostname for the VM. For example: node5. The hostname should be under 64 characters and can include alphanumeric and some special characters.
If you do not enter a hostname, a default hostname in the format
controller-<VM-IP-address-4th-octet> is assigned.Do you want to set up Static IP (preferred)? (y/n)
Enter y to configure an IP address for the VM.
Please specify the IP address in CIDR notation
Enter the IP address in the CIDR notation. For example, 10.1.2.10/24.
Your node VMs can be in the same subnet or in different subnets.
Please specify the Gateway IP
Enter the gateway IP address.
Ensure that you enter the gateway IP address corresponding to the network of your node VM.
Please specify the Primary DNS IP
Enter the primary DNS IP address.
Please specify the Secondary DNS IP
Enter the secondary DNS IP address.
Do you want to set up IPv6? (y/n)
Enter
yto configure IPv6 addresses.If you don't want to configure IPv6 addresses, enter
nand proceed to Step 4.e.Please specify the IPv6 address in CIDR notation
Enter the IPv6 address in the CIDR notation. For example, 2001:db8:1:2::10/64.
Your node VMs can be in the same subnet or in different subnets.
Please specify the Gateway IPv6
Enter the gateway IPv6 address.
Ensure that you enter the gateway IP address corresponding to the network of your node VM.
Please specify the Primary DNS IPv6
Enter the primary DNS IPv6 address.
Please specify the Secondary DNS IPv6
Enter the secondary DNS IPv6 address.
When prompted if you are sure to proceed, review the information displayed, type y and press Enter.
You are logged into Deployment Shell.
You have completed the node preparation steps and are ready to add the node to your cluster.
Add the Node
To add the node to your existing cluster.
Log in to the installer node from which you deployed your existing Routing Director deployment cluster. You are placed in Deployment Shell, by default.
********************************************************************* WELCOME TO Routing Director SHELL! You will now be able to execute Routing Director CLI commands! ********************************************************************* user@node1>Enter the configuration mode in Deployment Shell.
user@node1> configure Entering configuration mode [edit] user@node1#
Configure
Your index should be a number higher than the four nodes of your existing cluster.kubernetes 5index for the worker node with the static IP address of the new node VM.user@node1# set deployment cluster nodes kubernetes 5 address 10.1.2.10 [edit] user@node1# commit commit complete [edit] user@node1# exit Exiting configuration mode user@node1>
Regenerate the configuration files.
user@node1> request deployment config Deployment inventory file saved at /epic/config/inventory Deployment config file saved at /epic/config/config.yml
Regenerate ssh keys on the cluster nodes.
When prompted, enter the SSH password for all the existing VMs and the new VM. Enter the same password that you configured to log in to the VMs.
user@node1> request deployment ssh-key Please enter comma-separated list of IP addresses: 10.1.2.3,10.1.2.4,10.1.2.5,10.1.2.6,10.1.2.10 Please enter SSH username for the node(s): root Please enter SSH password for the node(s): checking server reachability and ssh connectivity ... Connectivity ok for 10.1.2.3 Connectivity ok for 10.1.2.4 Connectivity ok for 10.1.2.5 Connectivity ok for 10.1.2.6 Connectivity ok for 10.1.2.10 <output snipped>
Add the new node to the cluster.
user@node1> request deployment add-node address 10.1.2.10 Process running with PID: 23xx077 To track progress, run 'monitor start /epic/config/log'
(Optional) Monitor the progress of the deployment.
user@node1> monitor start /epic/config/log