Before you proceed with the actual Tungsten Fabric (TF) deployment, verify that your deployment meets the following prerequisites:
Your MOS OpenStack cluster is deployed as described in
Deploy OpenStack with the compute-tf
preset enabled.
Your MOS OpenStack cluster uses the correct value of
features:neutron:tunnel_interface
in the openstackdeployment
object.
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.
Warning
TF uses features:neutron:tunnel_interface
to create the vhost0
virtual interface and transfers the IP configuration from the
tunnel_interface
to the virtual one. Therefore, plan this interface
as a dedicated physical interface for TF overlay networks.
The Kubernetes nodes are labeled according to the TF node roles:
Node role |
Description |
Kubernetes labels |
Minimal count |
---|---|---|---|
TF control plane |
Hosts the TF control plane services such as |
tfconfig=enabled tfcontrol=enabled tfwebui=enabled tfconfigdb=enabled |
3 |
TF analytics |
Hosts the TF analytics services. |
tfanalytics=enabled tfanalyticsdb=enabled |
3 |
TF vRouter |
Hosts the TF vRouter module and vRouter agent. |
tfvrouter=enabled |
Varies |
TF vRouter DPDK Technical Preview |
Hosts the TF vRouter agent in DPDK mode. |
tfvrouter-dpdk=enabled |
Varies |
Note
TF supports only Kubernetes OpenStack workloads.
Therefore, you should label OpenStack compute nodes with
the tfvrouter=enabled
label.
Note
Do not specify the openstack-gateway=enabled
and openvswitch=enabled
labels for the MOS deployments
with TF as a networking back end for OpenStack.