Install CCM HA Using Appliance
CCM HA installation is tested and verified for AWS, OpenStack, and VMware clouds.
To configure CCM in HA mode, you must use the following roles:
Database: MGMTPOSTGRES_MASTER and MGMTPOSTGRES_SLAVE (and if required, MGMTPOSTGRES_VIP)
CCM: CCM_SA_PRIMARY and CCM_SA_SECONDARY
CCM_SA_PRIMARY/SECONDARY – Exchange CCM SSH Keys
To exchange the SSH keys between the CCM_SA_PRIMARY and CCM_SA_SECONDARY servers, follow this procedure using root permissions.
On the CCM_SA_PRIMARY and the CCM_SA_SECONDARY instances, execute the following commands to generate a new SSH key on each instance.
Copy the id_rsa.pub content from both the CCM instances and paste the content into the authorized_keys file.
Verify mutual SSH access between the CCM_SA_PRIMARY and CCM_SA_SECONDARY by running the following command on each VM.
CCM_PRIMARY – Configure HA Wizard Properties
To configure high availability for CCM_SA_PRIMARY, follow this procedure.
Invoke the CCM wizard as a root user (see Virtual Appliance Process > Cloud-Specific Setup Details for a sample setup).
Prior to CloudCenter 4.8.2, cliqruser credentials were used for SSH configuration.
Effective CloudCenter 4.8.2, root user credentials are used for SSH configuration.
Configure the HA properties.
Write this down for future reference!Write down the Field details in a printed version of thesection for later use.
DB – Configure Database
DB IP or Hostname
The VIP/EIP for the master database and slave database. See> Cloud Nuances for additional context.
When you configure the MGMTPOSTGRES_MASTER – Configure High Availability Properties, you would have configured the VIP/EIP address for the
db_config_wizardalready. Similarly, you must provide the EIP/VIP address for the CCM_SA_PRIMARY and the CCM_SA_SECONDARY servers.
The following credentials are pre-populated:
Default username = cliqr (can be changed – manually change the password on MGMTPOSTGRES VMs or RDS and then update the username in the CCM through the database config wizard.
Be sure to change the PostgresDB password and update the db.properties file to reflect the correct password.
Default password = cliqr (can be changed)
Be sure to change the default password immediately after your first login. See PostgreSQL Password for additional context.
Configure_HA Primary Node Private IP The IP address of the primary CCM VM Secondary Node Private IP The IP address of the secondary CCM VM
Mgmtserver DNS Name
Use the DNS or IP of the CCM_LB – Used by the CCO VM to communicate with the CCM VM.
Once the details are entered, the database server begins replication configuration between the database servers followed by HA configuration and finally presents the following status messages.
Configuring CCM HA ...
Restart server (with the progress bar)
Configured CCM HA successfully
- Restart the secondary CCM server and corresponding CloudCenter services.
- Exit the CCM configuration wizard.
Back to: CCM HA
CCM_LB – HAProxy Installers
Use a plain clean OS image (such as CentOS7) to install a load balancer.
See CCM and Database Firewall Rules > for the complete list of ports that need to be open for your deployment.
If you configure a load balancer for any CloudCenter component, be aware that the firewalId is enabled by default and you must explicitly disable it to ensure that the CloudCenter component(s) can communicate with the load balancer. See Firewall Rules Overview for additional context.
Here is a sample configuration to load balance a CentOS7.x VM with HAProxy for the CCM.
- SSH into the VM instance using the key pair that you used to launch the VM.
Install HAProxy as the root user.
- Create .pem files for haproxy configuration for CCM_LB in the CCM Primary server.
Run the following commands.
You can name the mgmtserver and ca pem files as required for your environment, however, be sure to append them with the .pem extension.
Place the mgmtserver.pem and ca.pem files created earlier to the CCM_LB server in the /etc/haproxy location.
Append the following details to the HAProxy config file.
Start the HAProxy service and verify that the status response is active.
At this point, you must use HTTPS to invoke the CCM server. For example:
The following option is an alternative step to the HTTPS step above
Optional. To view the HA proxy status use the following configuration to access the ha_proxy from a web browser. These stats allow you to view the status of the nodes from a web browser and allows admins to drain/stop nodes without accessing the VMs directly.
Back to: CCM (Required)
- No labels