Set Up GCP

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, or 8.9

     • Rocky Linux 8.6, 8.8, or 8.9

   • 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.

Create a firewall rule to allow traffic to nginx nodeport and health checking

Leave default values for all parameters not mentioned.

1. Navigate to VPC Network > Firewall

2. Click CREATE FIREWALL RULE

3. Configure:

   • Name: allow-nginx-ingress

   • Network: default

   • Direction: Ingress

   • Action: Allow

   • Targets: Specified target tags

   • Target tags: allow-nginx-ingress

   • Source filter: IPv4 ranges

   • Source IPv4 ranges: 0.0.0.0/0

   • Second sourced filter: None

   • Protocols and ports: Specified ports and protocols - TCP 31443

4. Click CREATE.

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 Compute Engine > Instance groups

2. Click CREATE INSTANCE GROUP.

3. Select New unmanaged instance group (not the stateless or stateful options).

   

4. Configure:

   • Name:

   • Location: As defined for your VM

   • Network / Subnetwork: Same network used by the instance or Default

   • VM Instances: Select the new VM created previously

   

5. Under Port mapping, click ADD PORT

6. Enter port details

   • Name: https

   • Number: 31443

7. Add additional TCP ports, by repeating the previous two steps, depending on the features you intend to use from the list below. Enter a lowercase name of your choice.

   • OPM devices -31099

   • TCP syslogs - 31514

   

8. Click CREATE. The instance group will be created.

Leave default values for all parameters not mentioned.

1. Navigate to Health checks.

2. Click CREATE HEALTH CHECK.

3. Select/Enter values:

   • Name

   • Protocol: TCP

   • Port: 31443

4. Leave default values for health criteria, or change according to your requirements.

5. Click CREATE.

For more information, see the vendor documentation Set up the load balancer.

Leave default values for all parameters not mentioned.

1. Navigate to Network Services - Load balancing.

2. Click CREATE LOAD BALANCER

3. Under TCP load balancing, click START CONFIGURATION.

4. Select/Enter values:

   • Internet facing or internal only: From Internet to my VMs.

   • Multiple regions or single region: Multiple regions.
5. Click Continue.
6. Enter a name for the load balancer.

7. Click Backend configuration:

8. Enter values:

   • Backend type: Instance group

   • Protocol: TCP

   • Named port: https-ingress

   • Timeout: 30

9. Enter/select values:

   • Instance group: The instance group created previously

   • Port numbers: 31443

   • Health check: The health check created previously

10. Click DONE

11. Click Frontend configuration

12. Click ADD FRONTEND IP AND PORT

13. Enter values:

    • New frontend IP and port - Name: https-ingress

    • Protocol: TCP

    • IP version: IPv4

    • IP address: Ephemeral

    • Port: 443

14. Click DONE

15. Click CREATE

For more information, see the vendor documentation Create a new firewall rule.

1. Navigate to VPC Network > Firewall

2. Click CREATE FIREWALL RULE

3. Configure:

   • Name

   • Logs: Off

   • Network: Default

   • Priority: 1000

   • Direction of traffic: Ingress

   • Action on match: Allow

   • Targets: Specified target tags

   • Target tags: (example) syslog-ingress

   • Source filter: IPv4 ranges

   • Source IPv4 ranges: 0.0.0.0/0

   • Second source filter: None

   • Protocols and ports: Specified protocols and ports - UDP 30514

4. Click CREATE.

5. Navigate to VM instances and select the VM created previously

6. Click EDIT

7. Go to Network Tags and add the target tag specified above

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. Click CREATE LOAD BALANCER

3. Under UDP load balancing, click START CONFIGURATION.

4. Select/Enter values:

   • Internet facing or internal only: From Internet to my VMs.

   • Backend type: Target Pool or Target Instance
5. Click Continue.
6. Enter a name for the load balancer.
7. Select same region defined for your VM.

8. Click Backend configuration:

9. Enter values:

   • Backends: SELECT EXISTING INSTANCES

   • VM instances: Your VM name

10. Click Frontend configuration

11. Click ADD FRONTEND IP AND PORT

12. Enter values:

    • New frontend IP and port - Name: 

    • Protocol: UDP

    • Network service Tier: Premium

    • IP address: Ephemeral

    • Port: 30514

13. Click DONE.

14. Click CREATE.

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>"

If not done already, set up partitions according to the Prerequisites.

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

You will need to configure three partitions: /opt, /tmp and /var, as well as a separate disk for etcd. 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:

*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.