Mirantis Container Cloud (MCC) becomes part of Mirantis OpenStack for Kubernetes (MOSK)!

Now, the MOSK documentation set covers all product layers, including MOSK management (formerly Container Cloud). This means everything you need is in one place. Some legacy names may remain in the code and documentation and will be updated in future releases. The separate Container Cloud documentation site will be retired, so please update your bookmarks for continued easy access to the latest content.

Disable Tungsten Fabric analytics services¶

By default, the Tungsten Fabric analytics services were included in basic Tungsten Fabric setups up to, but not including, MOSK 24.1. For deployments upgraded to series 24.1 and 25.1, which still provide analytics services, you can disable them through the custom resource of the Tungsten Fabric Operator as described in this section.

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.

Starting with MOSK 25.2, analytics services are no longer part of the product. On existing deployments, analytics services are automatically removed during cluster update to 25.2.

To disable Tungsten Fabric analytics services:

Open the TFOperator custom resource for editing:

kubectl -n tf edit tfoperators.tf.mirantis.com openstack-tf

Disable Tungsten Fabric analytics services in the TFOperator custom resource:
```
spec:
  services:
    analytics:
      enabled: false
```

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 and tfanalyticsdb=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.
1. Log in to the Tungsten Fabric web UI.
2. On Configure > Infrastructure > Nodes > Analytics Nodes, delete all terminated analytics nodes.
3. On Configure > Infrastructure > Nodes > Database Analytics Nodes, delete all terminated database analytics nodes.
Optional. Override the tungstenFabricMonitoring.analyticsEnabled setting that is automatically configured based on the state of the Tungsten Fabric analytics services, which are enabled or disabled.

If set manually, the configuration overrides the default behavior and does not reflect the actual state of Tungsten Fabric analytics.

To disable monitoring of the Tungsten Fabric analytics services in StackLight by setting the following parameter in StackLight values of the Cluster object to false:
```
tungstenFabricMonitoring:
  analyticsEnabled: false
```
When done, the monitoring of the Tungsten Fabric analytics components will become disabled and Kafka alerts along with the Kafka dashboard will disappear from StackLight.

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.

No results

An error occurred

Disable Tungsten Fabric analytics services¶