Infrastructure setup

Configuring bonding options

It is essential to configure the bonding opts policy for the physical interface configured on each bond. Otherwise, the cluster will not be capable of achieving good performance.

Note: Ensure that the customer’s infrastructure supports 802.3ad LACP on their network side.

1. Log in to your node via SSH and open the bond interface files for editing:

bond0: /etc/sysconfig/network-scripts/ifcfg-bond0
bond1: /etc/sysconfig/network-scripts/ifcfg-bond1

2. In these files, find the BONDING_OPTS line and add the following LACP hash policy at the end of the line:

1
xmit_hash_policy=1

3. Restart these interfaces and confirm that the new value is working correctly.

1
2
# ifdown bond1; ifup bond1; cat /proc/net/bonding/bond1 | grep -i hash; ifdown bond0; \
ifup bond0; cat /proc/net/bonding/bond0 | grep -i hash;  ifup bond1.3102; ping -c5 8.8.8.8

The command output may contain errors and info messages.

The transmit hash policy was successfully changed.

Creating networks and assigning traffic types

At this stage, your cluster will have two networks (Private and Public), each with different traffic types associated with them. Now, you need to create the remaining infrastructure networks before proceeding with the setup process.

1. In the admin panel, create two additional networks (Storage and Trunk):

2. Go to Infrastructure > Nodes > <your_node> > Network Interfaces, select the network interface, and click Edit.

3. Associate each node’s VLAN interface with your networks:

Assign the Storage network to the bond1.3102 interface with IP subnet 10.0.XX.XX/X.
Assign the Private network to the bond0.3101 interface with IP subnet 192.168.XX.XX/X.
Assign the Services network to the bond0.3100 interface with IP subnet 172.16.XX.XX/X.
Assign the Trunk network to the bond0 interface (required for the compute cluster setup).

Perform this operation on all nodes.

Note: After assigning the Trunk network to the bond0 interface, you may lose the main gateway. In this case, edit the bond0.3100 interface once again and click Save. This action will reset the correct gateway.

Your network interfaces should look as follows in the admin panel or command-line interface:

1
# vinfra node iface list -a

4. Once all of the networks are correctly assigned to network interfaces, go to Infrastructure > Networks and assign traffic types to networks:

Note: In some installations, the Storage traffic type is assigned to the same bond as the Internal network that includes VM private and others traffic types. In the compute network requirements listed in the Administrator Guide, this is supported for the minimal network configuration. For high-end production clusters, it is recommended to have a separate bond interface dedicated solely to the Storage traffic type.

Now, you can proceed to set up the storage cluster.