How to set up two networks (LAN and Public) for the Manager and CRs, and route cluster management, backup and migration traffic through the LAN?

Question

How to set up two networks (LAN and Public) for the Manager and Compute Resources (CRs), so that cluster management, backup and migration traffic goes through the LAN?

Answer

Note: This solution applies only if you have full management and control over a private LAN network between the Manager and all CRs. If you do not control the private network (for example, it is provided by a third party or you cannot assign IP addresses and ranges on it), do not use this setup.

The example below is for a physical LAN network that you manage, combined with VPC.

Prerequisites:

1. The Manager and every CR have two NICs:
   • eth0 – public
   • eth1 – private (LAN)
2. You manage the LAN and can assign IP addresses and ranges on it.
3. VPC is set up as described in How to use VPC (private) network with public IPs in SolusVM 2.

Steps:

1. Create a backup of the Manager node first

   Do this before making any changes:

   # cd /usr/local/solus/bin
   # ./installer -backup

2. Add the CRs to the cluster via the public interface (eth0)

   The CRs will appear in the SolusVM 2 UI with their public IPs.

3. Change the CR host IP to the private IP in the database

   Access the SolusVM 2 database on the Manager and, for each CR, replace the public IP with the private IP in the compute_resources table:

   UPDATE compute_resources SET host = 'Private IP' WHERE host = 'Public IP' AND id = <CR ID FROM UI>;

   or

   UPDATE compute_resources SET host = 'Private IP' WHERE id = <CR ID FROM UI>;

4. Update the agent configuration on each CR

   Connect to the CR via SSH, set the private IP in the "host" field of /etc/solus/agent.json:

   "host": "Private IP"

   Then restart the agent:

   # systemctl restart solus-agent

5. Configure VPC on the LAN

   For the CR VPC IP, use an address from the physical LAN network, and set the VPC IP range from the same LAN network.

   As a result:

   • All cluster communication, including backup and migration, goes through the LAN.
   • VPS are created on br-int or br-routed with public IPs.
   • No node restart is required, and no NICs need to be added to the OVS bridges.