1. Home
  2. Docs
  3. ClusterControl
  4. Components
  5. ClusterControl Ops Center

ClusterControl Ops Center

Introduction

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.

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.

Deployment of ClusterControl Operations Center

Below are the step-by-step instructions for installing the ClusterControl Operations Center on an existing clusterControl environment:

Red Hat/CentOS/RockyLinux/Alma LinuxDebian/Ubuntu

1. Uninstall CCv2 UI (clustercontrol2) and Apache server:

yum remove clustercontrol2
yum remove httpd

2. Install CC Ops Center:

yum install clustercontrol-mcc

The command will install two packages, clustercontrol-proxy and clustercontrol-mcc.

3. Register the local cmon controller and setup the UI to be accessible on port 19052:

ccmgradm init --local-cmon -p 19052 -f /var/www/html/clustercontrol-mcc

4. Restart cmon-proxy:

systemctl restart cmon-proxy

1. Uninstall CCv2 UI (clustercontrol2) and Apache server:

apt purge clustercontrol2
apt purge apache2

2. Install CC Ops Center:

apt install clustercontrol-mcc

The command will install two packages, clustercontrol-proxy and clustercontrol-mcc.

3. Register the local cmon controller and setup the UI to be accessible on port 19052:

ccmgradm init --local-cmon -p 19052 -f /var/www/html/clustercontrol-mcc

4. Restart cmon-proxy:

systemctl restart cmon-proxy

Finally, access the ClusterControl Operations Center using the following URL https://{cmon controller host}:19052 (or any other port passed during setup). Use one of your ClusterControl users from the existing ClusterControl installation/environment to Login:

 

Add Controller to the ClusterControl Operations Center

Adding a new ClusterControl Controller into the ClusterControl Operations Center is straightforward. Below are the instructions:

1. After logging into ClusterControl Operations Center, go to Manage Controllers → Add new controller. Fill in the name of the controller and the ClusterControl UI as shown below:

2. On the next page, fill in the username and password to connect to the ClusterControl. It is necessary to switch ClusterControl’s user authentication to LDAP authentication, ensuring that all CMON controllers operate using the same user authentication database:

3. Test the authentication by clicking on the Test Connection button. After the connection is successful, press the Finish button.

4. A new controller will be shown in the list of managed controllers:

Managing Multiple Controllers

After all the ClusterControl has been added to the ClusterControl Operations Center, the Operations Center can give information about the status related to the Clusters, Nodes, and controllers in the Overview Page:

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:

Was this article helpful to you? Yes No