OpenSDN cluster¶
All services of OpenSDN, formerly Tungsten Fabric (TF), are delivered as separate containers, which are deployed by the OpenSDN Operator (TFOperator). Each container has an INI-based configuration file that is available on the host system. The configuration file is generated automatically upon the container start and is based on environment variables provided by the Operator through Kubernetes ConfigMaps.
The main OpenSDN containers run with the host network as
DeploymentSet, without using the Kubernetes networking layer. The services
listen directly on the host network interface.
The following diagram describes the minimum production installation of OpenSDN with a Mirantis OpenStack for Kubernetes (MOSK) deployment.
For the details about the OpenSDN services included in MOSK deployments and the types of traffic and traffic flow directions, see the subsections below.