Skip to content

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.

Note

Starting from ClusterControl 2.5.0, the toggle for this feature in the GUI is labeled Ops-Center (previously Multi-controller).

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 the GUI.

  1. Go to ClusterControl GUI → Settings → Addons and toggle on Ops-Center. This opens the Enable Ops-Center wizard.
  2. Step 1, About: review the feature summary, optionally following Learn more about how Ops-Center works, then click Continue.
  3. Step 2, Set root user: enter a Root username and Root user password (email is optional), confirm the password, then click Enable.
  4. The page reloads in multi-controller mode.

See User Guide → Overview → Addons → Ops-Center for details.

Go to ClusterControl GUI → Settings → License and click 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.

Deactivating ClusterControl Ops-C

Disabling Ops-Center switches the console back to single-controller mode. Since more than one controller may be registered while Ops-Center is active, ClusterControl needs you to pick which one of the registered controllers stays as the single active controller before the switch completes.

  1. Go to ClusterControl GUI → Settings → Addons.
  2. Toggle off Ops-Center. This opens the Disable Ops-Center dialog, warning that the general overview across all controllers will no longer be available and that the Ops-Center root user will be deleted.
  3. Under Controller to keep, choose the controller that should remain as the single active controller (required).
  4. If more than one controller is registered, optionally check Remove the other controllers from the configuration to remove them now; leave it unchecked to keep them on record for re-enabling Ops-Center later without re-adding them.
  5. Click Disable. The page reloads in single-controller mode, pointed at the controller you picked. The other registered controllers are not uninstalled or otherwise affected on their own hosts.

See User Guide → Overview → Addons → Disable Ops-Center for the exact dialog wording.

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 (ccmgr), 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 by the ccmgr process (systemd unit is called cmon-proxy) instead. So, with an existing ClusterControl environment/installation, the Apache server and the CCv2 UI can be completely removed prior to installing ClusterControl Ops-C.

Functions of ClusterControl Manager (ccmgr) 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
Copyright © 2014-2026 Severalnines AB. All rights reserved.

Severalnines and ClusterControl are registered trademarks in the US, UK, and EU. The 3rd-party trademarks on this site are property of their respective owners and are used for referential purposes only.

Made with Material for MkDocs