ClusterControl Ops-C

ClusterControl Operations Center (CC Ops-C) is a platform management designed to simplify and enhance the management of database clusters, providing a single interface for multiple ClusterControl instances (controllers) for handling complex database operations and ensuring the reliability, performance, and security of database systems. You can use the ClusterControl Operation center to handle large-volume environments of 1000+ of nodes.

Horizontal scaling of ClusterControl is accomplished by registering or adding additional ClusterControl installations to the designated primary ClusterControl installation. CMON controllers are manually registered or added to this primary installation. It also provides multi-tenancy isolation where each tenant is assigned their own CMON Controller.

Single-Controller vs Multi-Controller

Mode	Description
Single-Controller	Traditional setup using a single CMON controller to manage clusters.
Multi-Controller (Ops-C)	Ops-C manages multiple CMON controllers via the ClusterControl Manager (cmon-proxy), providing consolidated control and visibility across different environments.

In a multi-controller architecture, each deployment can have its own isolated CMON controller, registered to a primary Ops-C instance.

Activating ClusterControl Ops-C

Since ClusterControl version 2.3.2, ClusterControl Ops-C is installed by default so you only need to enable it from ClusterControl -> Settings -> License -> Enable Multiple Controllers.

Info

When you enable ClusterControl Ops-C, it will ask you to create a root user and password. This root user is used only for managing CMON Controllers and serves as an extra layer of security.

After you enable it, you will see the corresponding UI.

Controller Management

Ops-C enables full lifecycle management of CMON controllers through the web UI.

Add Controller

Adding a new ClusterControl Controller into the ClusterControl Ops-C is straightforward. Below are the instructions:

1. Navigate to Manage Controllers -> Add new controller. It will ask you to authenticate with the root user password created when you enabled ClusterControl Ops-C.
2. Provide the controller name and Controller's Cmon API URL. For example, https://161.39.113.66/api/
3. Test the connection by using the Ping controller button, and press on Add.
4. The new controller will appear in the controller list.

Info

To display aggregated data from multiple controllers, Ops-C app will attempt to log in to all registered controllers using your current credentials upon login. For consistent access, ensure this user exists on all controllers with the same credentials and permissions.

Edit Controller

To update the configuration of an existing controller:

1. Go to Manage Controllers.
2. Click the Edit button in the Actions section.
3. Modify properties such as name or API URL.
4. Save changes.

Remove Controller

To remove a controller from Ops-C:

1. Navigate to Manage Controllers.
2. Click the Remove button in the Actions section.
3. Confirm removal.

The controller will be unlinked but not uninstalled from the remote host.

Monitoring Dashboard

The Controllers’ Overview dashboard provides a global view of: - Controller health and job status - Cluster alarms and backups - Node-level availability - Active jobs per controller

You cna filter by status Failed, Warning, Operational for both Clusters and Nodes.

Users can switch between controllers using the Active CMON Controller selector. The application context is scoped to the selected controller for all operations outside the overview.

Discover the status of Clusters and Nodes in specific controllers as shown below:

Go through the node list for specific clusters in the selected controller:

ClusterControl Manager

A new process, the ClusterControl Manager (cmon-proxy), is responsible for managing, collecting data, and monitoring the CMON controllers in this configuration:

• The Controllers’ Overview page features a dashboard that presents aggregated information on registered or managed CMON controllers, providing insights into the status of controllers, ongoing jobs, alarms, and backups, as well as the status of the database clusters and nodes.
• The web user interface allows users to select the “Active CMON Controller”, which determines the information displayed throughout the application (excluding the Controllers’ Overview) and directs user actions for clusters or nodes to the selected CMON Controller.

Attention

Starting from clustercontrol-mcc 2.2.4 (July 2024), clustercontrol-mcc web application doesn’t require an Apache server any longer. There is no dependency for the Apache server and the web application is served with the cmon-proxy process instead. So, with an existing ClusterControl environment/installation, the Apache server and the CCv2 UI can be completely uninstalled prior to installing ClusterControl Ops-C.

Functions of ClusterControl Manager include: - Routing API and UI traffic - Aggregating data from multiple controllers - Handling multi-tenant authentication - Exposing Ops-C UI on a configurable port (default: 19052)

Ensure the service is active:

systemctl status cmon-proxy

To restart after changes:

systemctl restart cmon-proxy