OpenSDN cluster
All services of OpenSDN, formerly Tungsten Fabric (TF), are delivered as
separate containers deployed by the OpenSDN Operator (TFOperator). Each
container generates its INI-based configuration file at startup from
environment variables. The Operator provides these variables through Kubernetes
ConfigMaps and Secrets. Service logs are written to the host under
/var/log/tf/<service>.
The OpenSDN control plane, configuration, vRouter, and web UI services run as DaemonSets with the host network, without using the Kubernetes networking layer. These services listen directly on the host network interfaces. The backing data stores, which include Cassandra, ZooKeeper, RabbitMQ, and Redis, are managed by dedicated operators that TFOperator deploys and run on the Kubernetes pod network.
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.