Tungsten Fabric deployment prerequisites¶
Before you proceed with the actual Tungsten Fabric (TF) deployment, verify that your deployment meets the following prerequisites:
Your MOSK OpenStack cluster is deployed as described in Deploy an OpenStack cluster with the Tungsten Fabric back end enabled for Neutron using the following structure:
spec: features: neutron: backend: tungstenfabric
Your MOSK OpenStack cluster uses the correct value of
openstackdeploymentobject. The TF Operator will consume this value through the shared secret and use it as a network interface from the underlay network to create encapsulated tunnels with the tenant networks.
Plan this interface as a dedicated physical interface for TF overlay networks. TF uses
features:neutron:tunnel_interfaceto create the
vhost0virtual interface and transfers the IP configuration from the
tunnel_interfaceto the virtual one.
Do not use
bridgesfrom L2 templates as
tunnel_interface. Such usage might lead to networking performance degradation and data plane downtime.
The Kubernetes nodes are labeled according to the TF node roles:
TF control plane
Hosts the TF control plane services such as
Hosts the TF analytics services.
Hosts the TF vRouter module and vRouter Agent.
TF vRouter DPDK Technical Preview
Hosts the TF vRouter Agent in DPDK mode.
TF supports only Kubernetes OpenStack workloads. Therefore, you should label OpenStack compute nodes with the
Do not specify the
openvswitch=enabledlabels for the OpenStack deployments with TF as a networking back end.