// removed jquery ui css and js

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
      /usr/local/cliqr/bin/db_config_wizard
    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.


  •  Database HA

    Database HA

    Proxy Settings

    If you need a proxy server to connect to the internet, be sure to configure the Proxy setting for the Tomcat service on the CCM and CCO servers.

    To connect to the Internet using a proxy server, follow this process:

    1. Modify your proxy environment to reflect your proxy settings.
    2. In the /usr/local/tomcat/bin/setenv.sh file, the CloudCenter platform requires you to add the following parameters to the existing JAVA_OPTS environment variable:

      REQUIRED for HTTP – Add the following parameters to the JAVA_OPTS environment variable
      -Dhttp.proxyHost=<proxy_hostname> -Dhttp.proxyPort=<port_number>

      or

      REQUIRED for HTTPS – Add the following parameters to the JAVA_OPTS environment variable
      -Dhttps.proxyHost=<proxy_hostname> -Dhttps.proxyPort=<port_number> 
      Sample /usr/local/tomcat/bin/setenv.sh with added parameters in JAVA_OPTS
      export LD_LIBRARY_PATH=/usr/local/apr/lib
      export CATALINA_PID=$CATALINA_HOME/catalina.pid
      export JPDA_ADDRESS=8000
      export JAVA_OPTS="-Djava.awt.headless=true -Dfile.encoding=UTF-8 -server -Xms1024m -Xmx2048m -XX:NewSize=512m -XX:MaxNewSize=512m -XX:PermSize=512m -Dhttp.proxyHost=proxy.cisco.com -Dhttp.proxyPort=80"
      export CATALINA_OUT=/dev/null
    3. Additional parameters may be required if the CCM or CCO servers need to reach network resources, bypassing the proxy.

      -Dhttp.nonProxyHosts=<bypass_hostname>
      OPTIONAL – Sample /usr/local/tomcat/bin/setenv.sh bypassing the proxy
      export LD_LIBRARY_PATH=/usr/local/apr/lib
      export CATALINA_PID=$CATALINA_HOME/catalina.pid
      export JPDA_ADDRESS=8000
      export JAVA_OPTS="-Djava.awt.headless=true -Dfile.encoding=UTF-8 -server -Xms1024m -Xmx2048m -XX:NewSize=512m -XX:MaxNewSize=512m -XX:PermSize=512m -Dhttp.proxyHost=proxy.cisco.com -Dhttp.proxyPort=80 -Dhttp.nonProxyHosts=10.1.1.1"
      export CATALINA_OUT=/dev/null
    4. Restart the Tomcat service.

      /etc/init.d/tomcat stop
      /etc/init.d/tomcat start
    5. Verify that the proxy settings are in effect by issuing the ps aux | grep java command.

      Output of the ps aux | grep java command
      cliqrus+ 25106 0.0 45.3 4368868 929000 ? Sl Mar02 54:15 /usr/lib/jvm/java-8-sun/bin/java -Djava.util.logging.config.file=/usr/local/tomcatgua/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.awt.headless=true -Dfile.encoding=UTF-8 -server -Xms1024m -Xmx2048m -XX:NewSize=512m -XX:MaxNewSize=512m -XX:PermSize=512m -XX:MaxPermSize=512m -Djav.endorsed.dirs=/usr/local/tomcatgua/endorsed -classpath /usr/local/tomcatgua/bin/bootstrap.jar:/usr/local/tomcatgua/bin/tomcat-juli.jar -Dcatalina.base=/usr/local/tomcatgua -Dcatalina.home=/usr/local/tomcatgua -Djava.io.tmpdir=/usr/local/tomcatgua/temp -Dhttp.proxyHost=proxy.cisco.com -Dhttp.proxyPort=80 -Dhttp.nonProxyHosts=10.1.1.1 org.apache.catalina.startup.Bootstrap start

      Ensure that line -Dhttp.proxyHost=proxy.cisco.com -Dhttp.proxyPort=80 -Dhttp.nonProxyHosts=10.1.1.1 is present in the output.

    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 id_rsa.pub >> authorized_keys
      chmod 600 authorized_keys
    2. Copy the id_rsa.pub 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.

      ssh root@<MGMTPOSTGRES_MASTER/MGMTPOSTGRES_SLAVE>

    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
      /usr/local/cliqr/bin/db_config_wizard.sh
    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.

      See Configure CCM Wizard Properties for other settings.

      Wizard Menu

      Field

      Description

      Configure_Postgres_HADB MasterThe hostname for the master database VM – not configurable.
      DB Master Private IPThe private IP address of the master database VM
      DB Slave HostnameThe hostname for the slave database VM
      DB Slave Private IPThe private IP address of the slave 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 PostgreSQL as an RDS service in the SA or HA modes, see Configuring HA for PostgreSQL Database on AWS. 

      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 the command line for each PostgreSQL server and enter the following command to review the status of the database and the HA connectivity:
      # pcs status

      1. Ensure that the PCSD Status for both database servers are Online.
      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.





  • No labels
© 2017-2018 Cisco Systems, Inc. All rights reserved