Adding a Worker Node - GCP

Overview

This procedure is for adding a worker node to an existing TOS Aurora cluster on the GCP platform. If you have not yet installed TOS Aurora, on the primary data node, start with Clean Install of TOS Aurora on GCP. For all other installation paths such as upgrade or other platforms, see the menu for the appropriate procedure.

You do not need to install TOS on the worker nodes.

Prerequisites

You cannot use IP Tables. All IP tables rules will be flushed when adding the node.
Your primary data node must also be deployed on GCP.
You must know the resources you will need - CPU cores, RAM, disk space and the load-model parameter, provided by your account team based on the procedure Calculate resources - clean install.
You will need to allow access to required Ports and Services.
If you intend to use syslog, allocate a syslog VIP on the same subnet as your primary VIP.
The node's network IP must be on the same subnet as the cluster primary VIP.
Give the node a unique hostname in the cluster - use the command below, replacing <mynode> with your preferred name:

[<ADMIN> ~]$ sudo hostnamectl set-hostname <mynode>

sudo hostnamectl set-hostname <mynode>

You will need to configure three partitions: /opt, /tmp and /var. The /opt partition will contain your data, which will increase over time. Most of your available disk space should be allocated to this partition and the minimum is determined by the load model parameter (small, medium, large) provided by your account team. Minimum sizes for all partitions:

Minimum Partition Sizes

/opt/

(Small)*

/opt/

(Medium)*

/opt/

(Large)*

/tmp/

/var/

Central cluster / remote cluster primary data node / HA data nodes

80 GB

170 GB

370 GB

25 GB

200GB

Worker node (central and remote clusters)

70 GB

25 GB

60 GB

*Small, medium and large refer to the load model parameter provided by your account team.

We recommend allocating /opt partition all remaining disk space after you have partitioned the other directories.

Procedure

Before you proceed, read and understand Prerequisites - this may prevent unexpected failures.

Launch the instance.
For additional help, refer to the official documentation Create and start a VM instance.
1. In the Google Cloud console, navigate to Compute Engine > VM instances
2. Click +CREATE INSTANCE.
3. Configure:
  - Name:
  - Region/Zone: As appropriate
  - Machine family: GENERAL-PURPOSE
  - Series: E2
  - Machine type: Custom
  - Cores / Memory: According to the load-model parameter value received from your account team.
4. Under Boot Disk, click CHANGE.
5. Configure the boot disk.
  - Make sure tab Public Images is selected.
  - Operating system: Red Hat Enterprise Linux or Rocky Linux
  - Version:
    
    Red Hat Enterprise Linux 8.6, 8.8, 8.9, or 8.10
    
    Rocky Linux 8.6, 8.8, 8.9, or 8.10
  - Boot disk type, SSD persistent disk
  - Size, The value received from your account team.
6. Click Select. The boot disk settings will be saved.
7. Select Advanced options.
8. Select Networking.
9. Configure Networking:
  - Network tags: default-allow-ssh allow-nginx-ingress
  - Hostname: Optional
10. (Optional) Host name: Type a host name or use the default device value.
11. Click CREATE.
Add the VM to the instance group.
Add the VM to the Instance Group

For more information about managing instance groups, see the vendor documentation Group unmanaged VMs together.

Leave default values for all parameters not mentioned.
1. Navigate to Instance groups.
2. Select the instance group that contains the existing VMs in the cluster.
3. Configure:
  - VM Instances: Add the new VM created previously
4. Click SAVE.
Add the VM to the SysLog UDP Load Balancer.
For more information, see the vendor documentation Set up the load balancer.

Leave default values for all parameters not mentioned.
1. Navigate to Load balancing - Network services.
2. Select the load balancer created previously for the primary data node
3. Click Backend configuration:
4. Enter values:
  - Backends: SELECT EXISTING INSTANCES
  - VM instances: Add the new VM created previously
5. Click DONE.
Connect to the VM Using SSH.
To connect via ssh you can add an existing ssh key to GCP via UI or use the gcloud utilily to generate key and add it.

To generate a key using gcloud:
1. Download gcloud to your workstation.
2. Run gcloud auth login command to login to your account. Variable <PROJECT_ID> can be set once globally to avoid entering it each time.
  gcloud config set project "<PROJECT_ID>"
  
  gcloud config set project "<PROJECT_ID>"
  gcloud compute ssh --zone "<ZONE>" "<VM_INSTANCE_NAME>"
  
  gcloud compute ssh --zone "<ZONE>" "<VM_INSTANCE_NAME>"
Configure Partitions.

If not done already, set up partitions according to the Prerequisites.
Configure the Operating System.
1. If you are not currently logged in as user root, do so now.
  [<ADMIN> ~]$ su -
  
  su -
2. If you want to change the host name or IP of the machine, do so now. Once TOS Aurora has been installed, changing the host name or IP address will require reinstalling - see Changing IP Address/Host Names. To change the host name, use the command below, replacing <mynode> with your preferred name.
  [<ADMIN> ~]# hostnamectl set-hostname <mynode>
  
  hostnamectl set-hostname <mynode>
3. Modify the environment path to run TOS CLI commands without specifying the full path (/usr/local/bin/tos).
  [<ADMIN> ~]# echo 'export PATH="${PATH}:/usr/local/bin"' | sudo tee -a /root/.bashrc > /dev/null
  
  echo 'export PATH="${PATH}:/usr/local/bin"' | sudo tee -a /root/.bashrc > /dev/null
4. Synchronize your machine time with a trusted NTP server. Follow the steps in Configuring NTP Using Chrony.
5. Configure the server timezone.
  [<ADMIN> ~]# timedatectl set-timezone <timezone>
  
  timedatectl set-timezone <timezone>
  where <timezone> is in the format Area/Location. Examples: America/Jamaica, Hongkong, GMT, Europe/Prague. List the time-zone formats that can be used in the command.
  [<ADMIN> ~]# timedatectl list-timezones
  
  timedatectl list-timezones
6. Upgrade the kernel:
  [<ADMIN> ~]# dnf upgrade
  
  dnf upgrade
7. Disable SELinux:
  - If file /etc/selinux/config exists, edit and change the value of SELINUX to disabled:
    SELINUX=disabled
  - If the file doesn't exist or SELINUX is already set to disabled, do nothing.
8. Reboot the machine and log in.
9. Install Wireguard. This is needed to encrypt communication between nodes (machines) within the cluster. See Install Wireguard and follow the steps for your Linux distribution.
10. Reboot the machine and log in.
11. Install screen and rsync:
  [<ADMIN> ~]# dnf install -y rsync screen
  
  dnf install -y rsync screen
12. Disable the firewall:
  [<ADMIN> ~]# systemctl stop firewalld
  
  systemctl stop firewalld
  [<ADMIN> ~]# systemctl disable firewalld
  
  systemctl disable firewalld
13. Create the TOS Aurora load module configuration file /etc/modules-load.d/tufin.conf. Example using vi:
  [<ADMIN> ~]# vi /etc/modules-load.d/tufin.conf
  
  vi /etc/modules-load.d/tufin.conf
14. Specify the modules to be loaded by adding the following lines to the configuration file created in the previous step. The modules will then be loaded automatically on boot.
  br_netfilter wireguard overlay ebtables ebtable_filter
  
  br_netfilter wireguard overlay ebtables ebtable_filter
15. Load the above modules now:
  [<ADMIN> ~]# cat /etc/modules-load.d/tufin.conf |xargs modprobe -a
  
  cat /etc/modules-load.d/tufin.conf |xargs modprobe -a
  Look carefully at the output to confirm all modules loaded correctly; an error message will be issued for any modules that failed to load.
16. Check that Wireguard has loaded correctly.
  [<ADMIN> ~]# lsmod |grep wireguard
  
  lsmod |grep wireguard
  The output will appear something like this:
```
wireguard              201106  0
ip6_udp_tunnel         12755  1 wireguard
udp_tunnel             14423  1 wireguard
```
  If Wireguard is not listed in the output, contact support.
17. Create the TOS Aurora kernel configuration file /etc/sysctl.d/tufin.conf. Example using vi:
  [<ADMIN> ~]# vi /etc/sysctl.d/tufin.conf
  
  vi /etc/sysctl.d/tufin.conf
18. Specify the kernel settings to be made by adding the following lines to the configuration file created in the previous step. The settings will then be applied on boot.
  net.bridge.bridge-nf-call-iptables = 1 fs.inotify.max_user_watches = 1048576 fs.inotify.max_user_instances = 10000 net.ipv4.ip_forward = 1
  
  net.bridge.bridge-nf-call-iptables = 1 fs.inotify.max_user_watches = 1048576 fs.inotify.max_user_instances = 10000 net.ipv4.ip_forward = 1
19. Apply the above kernel settings now:
  [<ADMIN> ~]# sysctl --system
  
  sysctl --system
For maximum security, we recommend only installing official security updates and security patches for your Linux distribution, as well as the RPMs specifically mentioned in this section.
Add the node to the Cluster.
1. Log in to the primary data node.
2. On the primary data node:
  [<ADMIN> ~]$ sudo tos cluster node add --role=worker
  
  sudo tos cluster node add --role=worker
  On completion, a new command string is displayed, which you will need to run on the new node within 30 minutes. If the allocated time expires, you will need to repeat the current step.
3. Copy the command string to the clipboard.
4. Log in to the new node.
5. On the new node, paste the command string copied previously and run it. If the allocated time has expired, you will need to start from the beginning.
6. Verify that the node was added by running sudo tos cluster node list on the primary data node.

Check the TOS status.

On the primary data node, check the TOS status.
```
[<ADMIN> ~]$ tos status
```
tos status
In the output, check if the System Status is Ok and all the items listed under Components appear as Ok. If this is not the case, contact Tufin Support.

Example output for a central cluster data node:

[<ADMIN> ~]$ tos status         
[Mar 28 13:42:09]  INFO Checking cluster health status           
TOS Aurora
Tos Version: 24.2 (PRC1.1.0)

System Status: "Ok"
            
Cluster Status:
   Status: "Ok"
   Mode: "Multi Node"

Nodes
  Nodes:
  - ["node1"]
    Type: "Primary"
    Status: "Ok"
    Disk usage:
    - ["/opt"]
      Status: "Ok"
      Usage: 19%
  - ["node3"]
    Type: "Worker Node"
    Status: "Ok"
    Disk usage:
    - ["/opt"]
      Status: "Ok"
      Usage: 4%

registry
  Expiration ETA: 819 days
  Status: "Ok"

Infra
Databases:
- ["cassandra"]
  Status: "Ok"
- ["kafka"]
  Status: "Ok"
- ["mongodb"]
  Status: "Ok"
- ["mongodb_sc"]
  Status: "Ok"
- ["ongDb"]
  Status: "Ok"
- ["postgres"]
  Status: "Ok"
- ["postgres_sc"]
  Status: "Ok"

Application
Application Services Status OK
Running services 50/50

Remote Clusters
Number Of Remote Clusters: 2
  - ["RC"]
     Connectivity Status:: "OK:"
  - ["RC2"]
     Connectivity Status:: "OK"

  Backup Storage:
  Location: "Local
s3:http://minio.default.svc:9000/velerok8s/restic/default "
  Status: "Ok"
  Latest Backup: 2024-03-23 05:00:34 +0000 UTC

Example output for a remote cluster data node:

[<ADMIN> ~]$ tos status         
[Mar 28 13:42:09]  INFO Checking cluster health status           
TOS Aurora
Tos Version: 24.2 (PRC1.0.0)

System Status: "Ok"
            
Cluster Status:
   Status: "Ok"
   Mode: "Single Node"

Nodes
  Nodes:
  - ["node2"]
    Type: "Primary"
    Status: "Ok"
    Disk usage:
    - ["/opt"]
      Status: "Ok"
      Usage: 19%
  
registry
  Expiration ETA: 819 days
  Status: "Ok"

Infra
Databases:
- ["mongodb"]
  Status: "Ok"
- ["postgres"]
  Status: "Ok"

Application
Application Services Status OK
Running services 16/16

  Backup Storage:
  Location: "Local
s3:http://minio.default.svc:9000/velerok8s/restic/default "
  Status: "Ok"
  Latest Backup: 2024-03-23 05:00:34 +0000 UTC

After the node is added, we recommend stopping tos and then starting it to enhance the node's performance. This will require downtime.

Adding a Worker Node - GCP

Overview

Prerequisites

Procedure

Add the VM to the Instance Group