Disable Tungsten Fabric analytics services¶
Available since MOSK 23.3 TechPreview
By default, analytics services are part of basic setups for Tungsten Fabric deployments. To obtain a more lightweight setup, you can disable these services through the custom resource of the Tungsten Fabric Operator.
Warning
Disabling of the Tungsten Fabric analytics services requires
restart of the data plane services for existing environments and must be
planned in advance. While calculating the maintenance window for this
operation, take into account the deletion of the analytics DaemonSets
and automatic restart of the tf-config
, tf-control
, and
tf-webui
pods.
To disable Tungsten Fabric analytics services:
Open the
TFOperator
custom resource for editing:kubectl -n tf edit tfoperators.operator.tf.mirantis.com openstack-tf
Set
disableTFAnalytics
totrue
:spec: settings: disableTFAnalytics: true
Clean up the Kubernetes resources. To free up the space that has been used by Cassandra, ZooKeeper, and Kafka analytics storage, manually delete the related PVC:
kubectl -n tf delete pvc -l app=cassandracluster,cassandracluster=tf-cassandra-analytics kubectl -n tf delete pvc -l app=tf-zookeeper-nal kubectl -n tf delete pvc -l app=tf-kafka
Remove the
tfanalytics=enabled
andtfanalyticsdb=enabled
labels from nodes, as they are not required by the Tungsten Fabric Operator anymore.Manually restart the vRouter pods:
Note
To avoid network disruption, restart the vRouter pods in chunks.
kubectl -n tf get pod -l app=tf-vrouter-agent kubectl -n tf delete pod <POD_NAME>
Delete terminated nodes from the Tungsten Fabric configuration through the Tungsten Fabric web UI:
Caution
With disabled Tungsten Fabric analytics, the Tungsten Fabric web UI may not work properly.
Log in to the Tungsten Fabric web UI.
On Configure > Infrastructure > Nodes > Analytics Nodes, delete all terminated analytics nodes.
On Configure > Infrastructure > Nodes > Database Analytics Nodes, delete all terminated database analytics nodes.
Now, with the Tungsten Fabric analytics services successfully disabled, you have optimized resource utilization and system performance. While these services are deactivated, related alerts may still be present in StackLight. However, do not consider such alerts as indicative of the actual status of the analytics services.