Database (Required)

  •  Optional. Setup the CloudCenter Database to be an RDS Instance

    Configuring an AWS Database


    To setup the CloudCenter database to be an RDS instance, you must configure an AWS database as identified in this section.


    Be sure to configure the following dependencies before starting the HA configuration procedure.

    • The required IAM policies – see AWS Configurations (this page) > IAM and STS for additional context. Verify that the IAM policy and role has been used and has worked prior to starting this procedure. See IAM Role for additional context.

    • The roles and modes for the components used in your environment – see Virtual Appliance Overview > Modes and Roles.

    • This procedure assumes that you are using:

      • Hardware Requirements as specified

      • If the PostgreSQL RDS master instance fails, the PostgreSQL RDS replica instance remains in read-only mode

        After this switch, you must configure the CCM server by invoking the config wizard and provide the new master details. See Configure CCM Wizard Properties > DB > IP or Hostname row in the table.

        Read replicas are used to ensure a healthy replica set of the database at all times – in case the RDS crashes at any point.

        Manual CCM wizard changes are required when you have read replicas, but are not required for Multi-AZ. 

    • You can define additional deployment parameters by name (vpcId and dbSubnetGroup) for the RDS service and pass the values for the VPC ID and DB Subnet Group at deployment time. The CloudCenter platform uses these values while provisioning the RDS instance. See Services > PaaS Support for additional context.

    Process to Create cliqrdb

    Here you create cliqrdb as part of the setup and provide the hostname in the CCM.

    This procedure may differ based on your AWS version and is intended to provide a point of reference.

    1. Launch a RDS database Instance and select the PostgreSQL Engine.

      1. Access your AWS RDS console.

      2. Launch a database instance.

      3. Select the PostgreSQL Engine.

      4. Select PostgreSQL with Multi-AZ Deployment, and click on Next Step.

      5. Provide the following values along with the pre-populated values:

        1. DB Instance Identifier – A unique name to identify the AWS database instance account.

        2. Master Username – cliqr (The username for this account – you must use cliqr for this field)

        3. Master Password – The password for this account (8 characters, case insensitive).

        4. Confirm Password – Repeat the master password.

      6. Configure the Advanced Settings for the cliqrdb configuration:

        1. Change the Backup, Monitoring & Maintenance configuration based on your usage requirements.

        2. Select the VPC Security Group(s) to allow Port 5432 and ensure Database connection.

        3. In the Database Name field, enter cliqrdb.

        4. Click Launch DB Instance.
          You have now launched the database instance. The RDS instance takes some time to come up as it involves creating, modifying > backing-up process on the backend.

        5. Once the instance is up and available, view the cliqrdb instance using the PSQL remote host command. Here is a sample command:

          Sample Command
          psql -h -U cliqr -d cliqrdb

    2. Launch an instance for CCM, download the installer artifacts, and run the core_installer.

    3. To install DB in remote host, change the ccm-response.xml for CCM and provide the RDS canonical name for the following items and run the appliance installer:

      • db_host = the remote host name

      • db_user = cliqr

      • db_pass = the password used to launch the RDS instance

    4. Configure the RDS instance.

    HA – Multi-AZ Option

    For High Availability, launch the RDS instance using the Multi-AZ option – When you provision a Multi-AZ DB instance, Amazon RDS automatically creates a primary DB instance and synchronously replicates the data to a standby instance in a different Availability Zone (AZ).

    In case of an infrastructure failure, Amazon RDS performs an automatic failover to the standby database instance. Since the endpoint for the CloudCenter database instance remains the same after a failover, the database operation resumes without the need for manual administrative intervention.

    You can also  Create read replica for the instances launched with/without the Multi-AZ option as seen in the following image.

    Process to Create and Connect to the Replica DB Instance

    1. Create the read replica of the master RDS instance by providing the required details.

      1. DB Instance Identifier – The master RDS instance

      2. Destination Region –  Within the same region or a different region

      3. Availability Zone – Any availability zone

    2. Click Create Read Replica to launch the replica.

    3. Once launched, the instances are displayed on the RDS console with the replication role master and replica.

    4. Connect to the replica instance, and verify that the data is synchronized.

    Approaches to Configure an AWS capacitydb

    To configure an AWS capacitydb for the CloudCenter platform, you have the following options:

    Approach 1

    Create a separate Database

    Create capacitydb as part of the cliqrdb database.

    Approach 2

    Configure a Combined Database

    Use cliqrdb for capacity management as well

    Approach 1: Create a Separate Database for capacitydb

    To create a separate database for capacitydb after the RDS instance is up and running with the cliqrdb and before you access the CCM server.

    1. Access the RDS instance by remotely logging into the cliqrdb database.

      psql -h <RDS_HOST_NAME> -U cliqr -d cliqrdb
    2. Create another database called capacitydb.

      CREATE DATABASE capacitydb;
    3. Restart the Management server so it can access the capacitydb.

    Approach 2: Create a Combined Database

    Edit the file /etc/sysconfig/capacity-manager.conf file and add the following entry to use the same cliqrdb to generate the capacity-manager database's related tables without explicitly creating a separate capacitydb – perform this step after the RDS instance is up and running with the cliqrdb and before you access the CCM server.


    Back to Database (Required)

  •  Database NON-HA

    Database NON-HA

    CCM Installers are only available for AWS, OpenStack, and VMware clouds.

    MGMTPOSTGRES – Configure DB Access

    To configure database access from the CCM for MGMTPOSTGRES, follow this procedure.

    1. Invoke the DB wizard as a root user (see Virtual Appliance Process > Cloud-Specific Setup Details for a sample setup).

    2. Configure the CCM IP to enable database access to CCM.

      Wizard Path
    3. Enter the CCM_IP in the CCM IP field to configure the PostgreSQL database access.

    4. Verify your changes and Exit the DB configuration wizard.

    Back to: Database (Required)

  •  Database HA

    Database HA

    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.

    1. On the MGMTPOSTGRES_MASTER and MGMTPOSTGRES_SLAVE instances, execute the following commands to generate a new SSH key on each instance. 

      ssh-keygen -t rsa
      cd ~/.ssh
      cat >> authorized_keys
      chmod 600 authorized_keys
    2. Copy the content from both MGMTPOSTGRES instances and paste the content into the authorized_keys file.

    3. 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.

    1. Invoke the database wizard as a root user (see Virtual Appliance Process > Cloud-Specific Setup Details for a sample setup).

      MGMTPOSTGRES Wizard Path
    2. 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 the Installation Approach > Your Notes section for later use.

      HA-Specific Wizard Setting




      DB MasterThis value reflects the node1 or node2 details – this constant cannot be modified (not configurable).
      DB Master Private IPThe private IP address of the primary database VM
      DB Slave HostnameThis value reflects the node1 or node2 details – this constant cannot be modified (not configurable).
      DB Slave Private IPThe private IP address of the replica database VM

      VIP or EIP 

      The VIP/EIP IP for the database.

      Use your mouse to select this option.

       AWS Cloud Nuances for EIP
      To setup the CloudCenter database to be an RDS instance, see Configuring an AWS Database.

      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
    3. Exit the configuration wizard.

    4. Go to each PostgreSQL server and enter the following command to review the status of the database and the HA connectivity:

      pcs cluster status

      You can use the pcs cluster status command listed above or the pcs status command for both Steps 4a and 4b below. See for additional details on each command.

      1. Ensure that the PCSD Status for both database servers display Online in response to this command

      2. 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
Terms & Conditions Privacy Statement Cookies Trademarks