CCM Installers are only available for AWS, OpenStack, and VMware clouds.
Exchange MGMTPOSTGRES SSH Keys
To exchange the SSH keys between the MGMTPOSTGRES_MASTER and MGMTPOSTGRES_SLAVE instances, follow this procedure.
On the MGMTPOSTGRES_MASTER and MGMTPOSTGRES_SLAVE instances, execute the following commands to generate a new SSH key on each instance.
Copy the id_rsa.pub content from both MGMTPOSTGRES instances and paste the content into the authorized_keys file.
Verify mutual SSH access between the MGMTPOSTGRES_MASTER and MGMTPOSTGRES_SLAVE by running the following command on each VM.
MGMTPOSTGRES_MASTER – Configure High Availability Properties
To configure high availability for MGMTPOSTGRES_MASTER, follow this procedure.
Invoke the database wizard as a root user (see Virtual Appliance Process > Cloud-Specific Setup Details for a sample setup).
Configure Postgres HA to ensure the PostgreSQL database HA and enter the information in each field as follows:
Write this down for future reference!Write down the Field details in a printed version of thesection for later use.
HA-Specific Wizard Setting
DB Master This value reflects the node1 or node2 details – this constant cannot be modified (not configurable). DB Master Private IP The private IP address of the primary database VM DB Slave Hostname This value reflects the node1 or node2 details – this constant cannot be modified (not configurable). DB Slave Private IP The private IP address of the replica database VM
VIP or EIPThe VIP/EIP IP for the database.
Use your mouse to select this option.AWS Cloud Nuances for EIPTo setup the CloudCenter database to be an RDS instance, see
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 database for HA ...
Configuring database for replication
Exit the configuration wizard.
Go to eachserver and enter the following command to review the status of the database and the HA connectivity:
You can use the pcs cluster status command listed above or the pcs status command for both Steps 4a and 4b below. See https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/high_availability_add-on_reference/s1-clusterstat-haar for additional details on each command.
Ensure that the PCSD Status for both database servers display Online in response to this command
Ensure that the Daemon Status for Corosync, Pacemaker and the PCSD service are active/disabled. The active/disabled status indicates that PCS and Corosync services will be started on bootup as part of the cluster configuration process. This status ensures that the services start even if the Pacemaker service does not start the dependent services.
Back to: Database (Required)
- No labels