Docs menu
MENU

Compute cluster setup

1. Go to Compute and click Create compute cluster.

compute setup 1

2. Select the first three nodes (this will save you some time, and you will be able to add the remaining nodes after testing that the compute cluster is working) and click Next.

compute setup 2

3. Configure the physical network parameters:

Note: The compute IP address:

  • Consumed by each server
  • Must be Routable
  • Needs a default gateway
  • An (HA) IP address will be used for accessing the management panels
  • Can RFC 1918 compliant IP address pool, but needs to be NATed at least one (HA) address
  • This network will provide Internet connections for virtual machines
  • MTU must be set to 1500
  • Enable IP address management
  • Select the VLAN option
  • Enter the VLAN ID for compute: for example, 3103
  • Specify the subnet CIDR: 10.XX.XX.XX/XX
  • Specify the VLAN’s gateway: 10.XX.XX.1

compute setup 3

4. Set up DHCP and DNS:

  • Enable Built-in DHCP server
  • Specify the allocation pool: 10.XX.XX.4 – 10.XX.XX.254
  • Set the DNS you defined: for example, 1.1.1.1 (Cloudfare’s)

compute setup 4

5. Enable installation of the Kubernetes, load balancer, and billing services.

compute setup 5

6. Confirm that your configuration, and then click Create cluster.

compute setup 6

It will take from 20 to 45 minutes for the compute cluster to be deployed.

You can also check the deployment progress in the command-line interface by running:

1

# tail -f /var/log/vstorage-ui-backend/ansible.log

compute setup 7

During the compute cluster deployment, the Trunk network conversion is automatically being executed in the physical interface that was chosen for the compute VLAN.

Note: While the network conversion is in progress, there’s a high chance of losing the main route and access to the cluster. We recommend accessing the local IPMI session and run the route -n command, then you’ll see there is no gateway. Run ifup ifconfig bond1.3102 and the route command again, to configure the main route correctly.

compute setup 8

Note that after the process is complete, the name of the interface will change to br-bond1.

compute setup 9

Most common reasons of compute deployment issues include:

  • The CPU does not have virtualization capabilities enabled in BIOS.
  • There is no internet connectivity.
  • Some traffic types are assigned incorrectly.

Once the compute cluster is set up, you can test it by creating a simple CirrOS VM and running an ICMP connectivity test inside it.

compute setup 10