An online/cloud marketplace provides users with access to applications and services that are built on, integrated with, or complement the service provider’s offering. Most offer pre-configured one-click provisioning of applications and services.
ClusterControl will be offered on a number of marketplaces, allowing you to easily deploy a ClusterControl instance that you can use to manage your database nodes on that service provider’s platform. The marketplace requirements on how to create an application differ and in some cases this will require that a few extra steps are taken by you to get started.
Password-less SSH connections
ClusterControl requires password-less SSH access to the hosts where the database nodes will be managed. The ClusterControl application can in some marketplaces automatically generate a private and public SSH key for the root user while in others you will need to perform this step manually.
The public SSH key is needed when you launch your hosts to be used for the database nodes. It must be included/selected as one of the SSH keys that will be used when the cloud instances are created otherwise ClusterControl will not be able to connect and manage the database nodes.
Launching the ClusterControl Application
On all marketplaces, there is a 1-click button to launch ClusterControl. You are then presented with a launch form where you might need to provide the following:
- OS image to use – Only Ubuntu 18.04 and Ubuntu 20.04 is supported for the ClusterControl node.
- MySQL root user password – If there is no input field for it then a random password will be generated.
- CMON (DB) user password – If there is no input field for it then a random password will be generated.
- Public SSH key – The SSH key to use when launching the image. This is not the same SSH key that ClusterControl will need later.
- Enable private IP – Enable the use of private IP if that option is shown.
Getting the Public SSH Key
On some marketplaces, the ClusterControl image is allowed to generate a password-less SSH key automatically at boot up. You can then copy the SSH public key by SSH into the ClusterControl instance where the public SSH key is displayed on login.
If that is not the case you will need to generate the password-less SSH key for the default SSH user by SSH into the ClusterControl instance and perform the following (ex for a root user):
$ ssh-keygen -b 2048 -t rsa -f /root/.ssh/id_rsa -q -N "" $ ssh-keygen -y -f /root/.ssh/id_rsa > /root/.ssh/id_rsa.pub $ cat /root/.ssh/id_rsa.pub
Copy the public SSH key and use it later when the hosts/cloud instances for the database nodes are provisioned.
Launching the Hosts for the Database Nodes
Depending on the cloud provider that you are using, you can add the previously created public SSH key to your ‘security settings’ or add it when the cloud instances are launched. The selected public SSH key(s) will be inserted into the cloud instance’s
~/.ssh/authorized_keys file so that the ClusterControl instance is able to SSH into the host.
You will also need to make sure that the cloud instances are on the same private network as the ClusterControl instance and enable ‘private IPs’ if available when launching the cloud instances.
Deploying a Database Cluster
After you have launched your cloud instances for the database nodes then proceed to open your web browser to https://<clustercontrol instance ip> and enter the User registration information for the initial admin user.
Start to deploy a database cluster onto the previously launched hosts by following the deployment guide.