Network types

Network types

When planning your OpenStack environment, consider what types of traffic your workloads generate and design your network accordingly. If you anticipate that certain types of traffic, such as storage replication, will likely consume a significant amount of network bandwidth, you may want to move that traffic to a dedicated network interface to avoid performance degradation.

A Mirantis OpenStack for Kubernetes (MOS) deployment typically requires the following networks:

L3 networks for Kubernetes

Network

Description

Common/PXE network

The network used for the provisioning of bare metal servers.

Management network

The network used for managing of bare metal servers.

Kubernetes workloads network

The network used for communication between containers in Kubernetes.

Storage access network (Ceph)

The network used for accessing the Ceph storage. We recommended that it is placed on a dedicated hardware interface.

Storage replication network (Ceph)

The network used for the storage replication (Ceph). To ensure low latency and fast access, place the network on a dedicated hardware interface.

External networks (MetalLB)

The routable network used for external IP addresses of the Kubernetes LoadBalancer services managed by MetalLB.

Note

When selecting subnets, ensure that the subnet ranges do not overlap with the internal subnets’ ranges. Otherwise, the users’ internal resources will not be available from the deployed Container Cloud managed cluster.

The MOS deployment additionally requires the following networks:

L3 networks for MOS

Service name

Network

Description

Networking

Provider networks

Typically, a routable network used to provide the external access to OpenStack instances (a floating network). Can be used by the OpenStack services such as Ironic, Manila, and others, to connect their management resources.

Networking

Overlay networks (virtual networks)

The network used to provide denied, secure tenant networks with the help of the tunneling mechanism (VLAN/GRE/VXLAN). If the VXLAN and GRE encapsulation takes place, the IP address assignment is required on interfaces at the node level.

Compute

Live migration network

The network used by the OpenStack compute service (Nova) to transfer data during live migration. Depending on the cloud needs, it can be placed on a dedicated physical network not to affect other networks during live migration. The IP address assignment is required on interfaces at the node level.

The way of mapping of the logical networks described above to physical networks and interfaces on nodes depends on the cloud size and configuration. We recommend placing OpenStack networks on a dedicated physical interface (bond) that is not shared with storage and Kubernetes management network to minimize the influence on each other.