2. Home
  4. Docs
  6. ClusterControl
  8. Getting Started
  10. Next Generation of ClusterControl’s Web Application

Next Generation of ClusterControl’s Web Application

We are transitioning the ClusterControl web application to a new web framework. This new application will continue to improve on the user experience and ease of use that our users are accustomed to and we hope to further improve the quality and workflows.

These technical previews are intended to be released frequently and show the progress and design choices that we currently are making. It will take some time in order to become feature-complete compared with the current released version of ClusterControl v1.9.x.

We appreciate and welcome any feedback for changes or features requests!

Features

In this first technical preview, we have added initial support to deploy and manage Redis Sentinel clusters. Redis Sentinel is a high availability option when using Redis and provides better fault tolerance and uptime.

Use CCv2 to deploy Redis database nodes with co-located Sentinels. You can also schedule and restore from backups.

Installation

Prerequisites: ClusterControl Controller 1.9.x (cmon) is installed and an admin user created with RPCv2 – New User Management.

Follow below steps to install ClusterControl v2:

RedHat/CentOSDebian/Ubuntu

1. Clean yum’s cache:

yum clean all

2. Install ClusterControl v2 package:

yum install clustercontrol2

3. Restart Apache web service:

systemctl restart httpd

4. Open the web browser and go to https://{ClusterControl_host}:9443

5. Login with a user created by the New User Management.

1. Clean APT repository:

apt update

2. Install ClusterControl v2 package:

apt install clustercontrol2

3. Restart Apache web service:

systemctl restart apache2

4. Open the web browser and go to https://{ClusterControl_host}:9443

5. Login with a user created by the New User Management.

Note

If Apache fails to restart then check that there are rpc_tls files in /var/lib/cmon/ca/cmon. If those files are missing then just restart cmon by systemctl restart cmon and restart Apache again.

Firewall and CORS

The frontend application sends requests back to the web server via port 19501 which is then proxied to the CMON controller process via Apache2.

This requires that the firewall is open for at least these ports:

  • 9443 – web frontend

  • 19501 – CMON proxied api calls from the frontend application

Cross-Origin Resource Sharing (CORS) is a security mechanism to prevent malicious web applications from sending requests to other origins than it was loaded from.

ClusterControl2’s proxied requests must be sent to the same origin which is configurable via the /var/www/html/clustercontrol2/config.js file.

The configuration parameter CMON_API_URL sets the URL that the frontend application will call for proxied CMON RPCv2 requests. If you experience issues with CORS error then please double check the config.js file and make sure the IP/hostname is identical to what you see in your web browser.

For example with a URL set to CMON_API_URL: 'https://cc.mydomain.com:19501/v2' you will need to access the application using the URL https://cc.mydomain.com:19501 and not for example its public IP.

Limitations

In this initial release, you will only be able to deploy and manage Redis Sentinel and not any other database technologies that we currently support in ClusterControl 1.9.x. You can switch between these two web applications by using different URLs, as below:

  • ClusterControl v1: https://{ClusterControl_host}/clustercontrol
  • ClusterControl v2: https://{ClusterControl_host}:9443

These are some features/functionality that will be available in upcoming releases.

  • Global filtering
  • Cluster overview/details
  • Performance monitoring/dashboards
  • Deployments, imports and backup management for MySQL Replication, MySQL Galera, PostgreSQL, MongoDB and MySQL (NDB) Cluster
  • Advanced backup options
  • Cluster and node actions
  • Agent-based query monitoring
Was this article helpful to you? Yes 1 No 3