Setting up networks for the compute cluster
Prerequisites
- Your network topology meets the requirements listed in Requirements for the compute cluster.
- A clear understanding of the concept Traffic types.
Minimum network setup for the compute cluster
For the compute service deployed for evaluation purposes, the minimum network configuration includes two networks, for internal and external traffic. You can leave the default Public and Private networks as they are. In this case, traffic types should be assigned to these networks, according to the following table:
Network | Traffic types |
---|---|
Private | Storage, Internal management, OSTOR private, ABGW private, VM private, VM backups, VM public |
Public | Admin panel, SNMP, SSH, Self-service panel, Compute API, VM public, iSCSI, NFS, S3 public, ABGW public |
To create the minimum network configuration for the compute cluster
- Add the required traffic types (Compute API, VM private, VM backups, and VM public) to your infrastructure networks:
- On the Infrastructure > Networks screen, click the pencil icon next to the traffic type in the Exclusive traffic types section or next to the Regular traffic types section.
- Add the needed traffic type to your network by selecting the corresponding radio button or check box.
- Click the check mark to apply the changes.
- If you plan to use RDMA over InfiniBand, move the traffic type Storage to a dedicated network and assign that network to the IB interface.
- Configure network interfaces on the nodes that you plan to join the compute storage and connect the interfaces to your networks.
Recommended network setup for the compute cluster
For the compute service deployed for production, the recommended network configuration implies creating additional networks. The following networks are required:
- Private network, assigned to the first bonded connection
- Overlay network, assigned to a VLAN created on the second bonded connection
- Public network, assigned to a VLAN created on the second bonded connection
- External VM network, assigned to a VLAN created on the second bonded connection
- Backup network, assigned to a VLAN created on the second bonded connection
The required traffic types should be distributed between these networks, according to the following table:
Network | Traffic types |
---|---|
Private | Storage, Internal management, OSTOR private, ABGW private |
Overlay | VM private |
Public | Admin panel, SSH, SNMP, Compute API, Self-service panel, S3 public, iSCSI, NFS, ABGW public |
External VM | VM public |
Backup | VM backups, VM public |
To create the recommended network configuration for the compute cluster
- Add three more networks:
- Assign the required traffic types according to the recommended network setup:
- On the Infrastructure > Networks screen, click the pencil icon next to the traffic type in the Exclusive traffic types section or next to the Regular traffic types section.
- Add the needed traffic type to your network by selecting the corresponding radio button or check box.
- Click the check mark to apply the changes.
- Create and configure bonded and VLAN connections over node network interfaces.
- If you plan to use RDMA over InfiniBand, move the traffic type Storage to a dedicated network and assign that network to the IB interface.
- Create bonded and VLAN connections on the nodes that you plan to join the compute storage and connect the logical interfaces to your networks.