CliQr is now part of Cisco Learn More About Cisco

Install CloudCenter Components

Package Store Installation (Conditional)

Internet Access!

Icon

The package store requires internet access to be able to periodically synchronize OS packages from the default package store (repo.cliqrtech.com).

Configure a Local Package Store

To configure a local package store, follow this procedure.

  1. SSH into the VM instance using the key pair that you used to launch the VM.

  2. Login and become the ROOT user.

  3. Change to the location where you want to download the installer.

  4. Download the following file from software.cisco.com to the /tmp folder. See Installation Overview for additional context.

    • repo_installer.bin

  5. If your system administrator has provided an image with a pre-installed Package Store Repository, export the variable that is used to configure this repository as your Master Repository location. By default, the CloudCenter platform uses repo.cliqrtech.com.

  6. Run the repository (repo) installer using the following commands:

    For example:

     

    • <ostype>= centos6, centos7, rhel6, rhel7, ubuntu1404

    • <cloudtype>= amazon, azure, azurerm, azurepack, google, opsource, openstack, softlayer, vmware, vcd (run the ./core_installer.bin help command for a complete list)

       

  7. Copy the SSH key that was output from the preceding step and contact the CloudCenter Support team so they can add the SSH key to the master repository.

  8. Invoke the repo config wizard and configure the basic properties.

    Config Wizard Path

    Write this down for future reference!

    Icon

     Write down the Field details in a printed version of the Your Notes section for later use.

    Local Package Store PropertiesDescription
    Change Master Repository URL:
    Configure a master repository for this repository to sync.
    The default master is repo.cliqrtech.com.
    Set_Master Change the local repo to a master repo. The local repo will no longer sync with other master repositories. In this case, you must maintain the repo (package update , image xml update, and so forth).
    Repo_SyncupSync up with the master repository and update all changes from the master repo if any.
    Add_ssh_keyIf this repo is used as a master repository, use this option to add the SSH keys of the local repositories that point to this repo.
  9. Exit the Repo wizard.

  10. Run the following command to verify if the repo sync is complete and the files are downloaded.

You have now configure the package store locally! You can now proceed to the next step.

 

Back to Phase 4: Install Components

 

 

 

Bundle Store Installation (Optional)

The Bundle Store is a repository that contains the agent and service bundles. You must download and install these bundles on the VMs (worker or application VMs) launched by CloudCenter as part of the application orchestration process.

  • With Internet Connection: The default bundle store is hosted at (cdn.cliqr.com) and CloudCenter deployments where the Application VMs have access to the internet can use the default bundle store.
  • Isolated Environments: For environments where connectivity to the internet is restricted, create a local bundle store and register it with the CCO(s).

Configure a Bundle Store

To configure a bundle store, follow this procedure.

Isolated Environments

Icon

For environments where connectivity to the internet is restricted, create a local bundle store and register it with the CCO(s).

  1. Set up the HTTP server.

    Icon

    This setup assumes Apache2 on a CentOS server. If you use a different OS/HTTP server, adjust the following commands accordingly.

  2. Locate the document root of the HTTP server

    1. Change directory to /etc/httpd/conf

    2. Check httpd.conf for site-available/default files.

    3. Locate the DocumentRoot in one of these configuration files. Typically, it will be either /var/www or /var/www/html.

  3. Change directory to DocumentRoot directory. 

  4. Create a directory to reflect the CloudCenter release you are installing (for example, 4.6.0) and create a bundle directory under the release folder level.

  5. Change to the bundle directory.

  6. Copy or download the bundle_artifacts.zip

  7. Unzip the bundle_artifacts.zip file

  8. Update the configuration files to set the repository location.

    For example:

    Icon

    If you do not include the trailing “/” in the command, you will receive errors at some point in the process.

You have successfully configured the bundle store! You can now proceed to the next step.

 

Back to Phase 4: Install Components

 

 

 

CCM Installation (Required)

CloudCenter Manager (Required)

The CloudCenter Manager (CCM) is a centralized management tier that acts as a dashboard for users to model, migrate, and manage deployments. It provides for the unified administration and governance of clouds and users.

The CCM interacts directly with each CloudCenter Orchestrator (CCO) based on your deployment's application profile(s). Users can access the CloudCenter features by either through the CCM UI or REST APIs:

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 – Add the following parameters to the JAVA_OPTS environment variable
    Sample /usr/local/tomcat/bin/setenv.sh with added parameters in JAVA_OPTS
  3. Additional parameters may be required if the CCM or CCO servers need to reach network resources, bypassing the proxy.

    OPTIONAL – Sample /usr/local/tomcat/bin/setenv.sh bypassing the proxy
  4. Restart the Tomcat service.

  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

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

The /tmp Alternative

You can download installation files to a directory of your choice. The procedure provided in the CloudCenter documents, recommend using the /tmp folder as the download folder. In some cases, you may not want to use /tmp folder as the temp location as this directory may not allow files to be executed in your environment.

To install CloudCenter on systems where /tmp is set to nosuid or noexec, issue the following command before downloading the component files:

Install CCM

  • CCM NON-HA                                                                                                                                                

    1.  CCM – Run Core and CCM Installer

      CCM – Run Core and CCM Installer

      To run the Core and CCM installers, follow this procedure.

      1. Download package files:

        Icon

        See Installation Overview to understand the required components and the installation options.

        See Installer Overview to understand the types of files.

        1. SSH into the VM instance designated for this component by using the key pair that you used to launch the VM.
        2. Download the following required files for this component from software.cisco.com to the /tmp folder on that VM:

          • core_installer.bin
          • ccm-installer.jar
          • ccm-response.xml
      2. Run the core installer to setup core system components using the following commands:

        For example:

        Syntax:

        <ostype>= centos6, centos7, rhel6, rhel7

        <cloudtype>= amazon, openstack, vmware (run the ./core_installer.bin help command for a complete list)

      3. Log off and log back in as the root user to ensure JAVA Home is set.

      4. Change to the /tmp directory.


      5. Run the appliance installer to setup the CCM. 

      6. Reboot the CCM VM.

    2.  CCM – Configure CCM Properties

      Configure CCM Wizard Properties

      To configure the CCM wizard properties, follow this procedure.

        1. SSH into the CCM instance as a CentOS user.
        2. Run the following command:

      1. Invoke the CCM wizard.

        CCM Wizard Path
      2. Configure the server properties.

        Write this down for future reference!

        Icon
        Write down the Field details in a printed version of the Your Notes section for later use.

        CCM Properties

        Description

        Mail

        SMTP server details to send mail notifications. If you retain the default settings, the SMTP sever details are not configured.

        • SMTP Host: smtp.gmail.com
        • SMTP Port: Defaults to 465
        • SMTP Auth: Boolean setting
          • True = Authentication is required for the SMTP server.
          • False = Authentication is not required for the SMTP server.

        Mail_User

        Mail authentication and configuration details to send mail notifications. If you retain the default settings, the mail functionality is not be configured and emails are not sent.

        • Mail User: Your email address for the SMTP server
        • Password: The password to log into the SMTP server
        • From User: The email address (no reply) to initiate emails from the CCM server
        • Display Name: The name to be displayed when you initiate emails from the CCM server
        Server_info (Required)

        Public DNS: DNS (or IP address) of the CCM – Used by the CCO VM to communicate with the CCM VM.

        Monitor URL: Monitor VM's complete URL. For example, https://<MON or MON_LB IP address>:8443.

        • Requires HTTPS protocol.
        • Used by the CCM VM to retrieve the health status from the Monitor VM.

        Hazelcast IP: Private IP address of the CCM VM – Used internally by the CloudCenter platform. Required for HA Mode.

        External URL: The CloudCenter External URL for the CCM server. Required for HA Mode.

        Config_App_Logo

        Used by the application profile templates.

        ESB_Info

        Required only if you installed Enterprise Service Bus (ESB), an optional component that is not installed in CloudCenter appliances by default.

        Network

        Use the defaults if you are not making any changes to these settings.

        • Hostname:
        • Interface:
        DB
        (Effective CloudCenter 4.7.0)
        • IP or Hostname: DNS or IP of the Database
          • Local host: Default, does not include the flyway migrate configuration
          • Remote host, includes the flyway migrate configuration – see the last bullet in this row.
        • Authentication credentials for the database (either local or remote).
          • Username:
          • Password:
        •  Flyway Migrate: Optional. Remote Host Configure the CCM to a remote database by providing the IP address of the remote database. When you provide the IP address, you see an additional screen to configure the flyway migrate process.
          • Yes: Flyway migration takes place.
          • No: Only the configuration files are updated.
          Icon

          DB configuration is required for standalone database deployments.

        ELK_Info
        (Effective CloudCenter 4.7.0)
        • ELK Host: Specify the IP address for the ELK host (Monitor VM).
        • Elasticsearch Port: Displays 8881 by default.
        • Logstash Port: Displays 4560 by default.
        • Kibana Port: Displays 8882 by default.
        • ELK User: The default ELK Username = logreader.
        • ELK Password: The default ELK Password is re@d0nly (zero between d and n) (change this password after the initial login – see Download Log File for additional context).
        • Host Identifier: A Unique ID for the server – be sure to prefix the unique identifier with CCM_ for example, CCM_1
        • Host Identifier List: Only applies to environments using the HA mode – provide a list of comma separated unique host identifiers for all ELK/Monitor hosts in a HA setup = for example, CCM_1,CCM_2,myCCM.

          Icon

          In an environment operating in HA mode, if you have two CCM instances with unique IDs configured as CCM_1,CCM_2 in their respective server.properties file, then this property should state CCM_1,CCM_2 in both CCM instances. Each CCM must be aware of the unique ID of the other CCM(s) when in HA mode.

      3. Exit the CCM configuration wizard.

      4. Select Yes, to restart the Tomcat service for the changes to take effect.

      You have successfully installed the CCM instance! You can now proceed to the next step:

      • If you are installing a Health Monitor component – see Health Monitor Installation (Optional)

  • CCM NON-HA-STANDALONE                                                                                                                      

    1.  MGMTPOSTGRES – Run Core Installer

      MGMTPOSTGRES - Run Core Installer

      To run the MGMTPOSTGRES Core Installer, follow this procedure.

      1. Download package files:

        Icon

        See Installation Overview to understand the required components and the installation options.

        See Installer Overview to understand the types of files.

        1. SSH into the VM instance designated for this component by using the key pair that you used to launch the VM.
        2. Download the following required files for this component from software.cisco.com to the /tmp folder on that VM:

          • core_installer.bin
          • ccm-installer.jar
          • ccm-response.xml
      2. Run the core installer to setup core system components using the following commands:

        For example:

        Syntax:

        <ostype>= centos6, centos7, rhel6, rhel7

        <cloudtype>= amazon, openstack, vmware

    2.  MGMTPOSTGRES – Configure DB Access from CCM_SA

      MGMTPOSTGRES – Configure DB Access from CCM_SA

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

        1. SSH into the CCM instance as a centos user.
        2. Run the following command:

      1. Invoke the CCM wizard and configure the CCM IP to enable database access to CCM_SA.

        CCM Wizard Path
      2. Enter the CCM_SA_IP in the CCM IP field to configure the PostgreSQL database access.
      3. Verify your changes and Exit the CCM configuration wizard.

    3.  CCM_SA – Run Core and Appliance Installers

      CCM_SA – Run Core and Appliance Installers

      To run the core and appliance installers for CCM_SA, follow this procedure.

      1. Download package files:

        Icon

        See Installation Overview to understand the required components and the installation options.

        See Installer Overview to understand the types of files.

        1. SSH into the VM instance designated for this component by using the key pair that you used to launch the VM.
        2. Download the following required files for this component from software.cisco.com to the /tmp folder on that VM:

          • core_installer.bin
          • ccm-installer.jar
          • ccm-response.xml
      2. Run the core installer to setup core system components using the following commands:

        For example:

        Syntax:

        <ostype> = centos6, centos7, rhel6, rhel7

        <cloudtype> = amazon, openstack, vmware

      3. Remove the core_installer.bin file.

      4. Log off and log back in as the root user to ensure JAVA Home is set.

      5. Change to the /tmp directory and modify the ccm-response.xml file as follows:

        Response File EntryValueNotes
        <entry key="db_host" value="localhost"/> Replace localhost with IP or DNS of the PostgreSQL database. (MGMTPOSTGRES_IP)Required for the standalone CCM (CCM_SA) to connect to the remote database
      6. Run the appliance installer to setup the CCM.

      7. Reboot the CCM VM.

    4.  CCM_SA – Configure CCM Properties

      Configure CCM Wizard Properties

      To configure the CCM wizard properties, follow this procedure.

        1. SSH into the CCM instance as a CentOS user.
        2. Run the following command:

      1. Invoke the CCM wizard.

        CCM Wizard Path
      2. Configure the server properties.

        Write this down for future reference!

        Icon
        Write down the Field details in a printed version of the Your Notes section for later use.

        CCM Properties

        Description

        Mail

        SMTP server details to send mail notifications. If you retain the default settings, the SMTP sever details are not configured.

        • SMTP Host: smtp.gmail.com
        • SMTP Port: Defaults to 465
        • SMTP Auth: Boolean setting
          • True = Authentication is required for the SMTP server.
          • False = Authentication is not required for the SMTP server.

        Mail_User

        Mail authentication and configuration details to send mail notifications. If you retain the default settings, the mail functionality is not be configured and emails are not sent.

        • Mail User: Your email address for the SMTP server
        • Password: The password to log into the SMTP server
        • From User: The email address (no reply) to initiate emails from the CCM server
        • Display Name: The name to be displayed when you initiate emails from the CCM server
        Server_info (Required)

        Public DNS: DNS (or IP address) of the CCM – Used by the CCO VM to communicate with the CCM VM.

        Monitor URL: Monitor VM's complete URL. For example, https://<MON or MON_LB IP address>:8443.

        • Requires HTTPS protocol.
        • Used by the CCM VM to retrieve the health status from the Monitor VM.

        Hazelcast IP: Private IP address of the CCM VM – Used internally by the CloudCenter platform. Required for HA Mode.

        External URL: The CloudCenter External URL for the CCM server. Required for HA Mode.

        Config_App_Logo

        Used by the application profile templates.

        ESB_Info

        Required only if you installed Enterprise Service Bus (ESB), an optional component that is not installed in CloudCenter appliances by default.

        Network

        Use the defaults if you are not making any changes to these settings.

        • Hostname:
        • Interface:
        DB
        (Effective CloudCenter 4.7.0)
        • IP or Hostname: DNS or IP of the Database
          • Local host: Default, does not include the flyway migrate configuration
          • Remote host, includes the flyway migrate configuration – see the last bullet in this row.
        • Authentication credentials for the database (either local or remote).
          • Username:
          • Password:
        •  Flyway Migrate: Optional. Remote Host Configure the CCM to a remote database by providing the IP address of the remote database. When you provide the IP address, you see an additional screen to configure the flyway migrate process.
          • Yes: Flyway migration takes place.
          • No: Only the configuration files are updated.
          Icon

          DB configuration is required for standalone database deployments.

        ELK_Info
        (Effective CloudCenter 4.7.0)
        • ELK Host: Specify the IP address for the ELK host (Monitor VM).
        • Elasticsearch Port: Displays 8881 by default.
        • Logstash Port: Displays 4560 by default.
        • Kibana Port: Displays 8882 by default.
        • ELK User: The default ELK Username = logreader.
        • ELK Password: The default ELK Password is re@d0nly (zero between d and n) (change this password after the initial login – see Download Log File for additional context).
        • Host Identifier: A Unique ID for the server – be sure to prefix the unique identifier with CCM_ for example, CCM_1
        • Host Identifier List: Only applies to environments using the HA mode – provide a list of comma separated unique host identifiers for all ELK/Monitor hosts in a HA setup = for example, CCM_1,CCM_2,myCCM.

          Icon

          In an environment operating in HA mode, if you have two CCM instances with unique IDs configured as CCM_1,CCM_2 in their respective server.properties file, then this property should state CCM_1,CCM_2 in both CCM instances. Each CCM must be aware of the unique ID of the other CCM(s) when in HA mode.

      3. Exit the CCM configuration wizard.

      4. Select Yes, to restart the Tomcat service for the changes to take effect.

      You have successfully installed the CCM instance! You can now proceed to the next step:

      • If you are installing a Health Monitor component – see Health Monitor Installation (Optional)

  • CCM HA                                                                                                                                                           

    1.  MGMTPOSTGRES_MASTER and SLAVE – Run Core Installer and Setup SSH Communication

      MGMTPOSTGRES_MASTER and SLAVE – Run Core Installer and Setup SSH Communication

      1. Download package files:

        Icon

        See Installation Overview to understand the required components and the installation options.

        See Installer Overview to understand the types of files.

        1. SSH into the VM instance designated for this component by using the key pair that you used to launch the VM.
        2. Download the following required files for this component from software.cisco.com to the /tmp folder on that VM:

          • core_installer.bin
          • ccm-installer.jar
          • ccm-response.xml
      2. Run the core installer to setup core system components using the following commands:

        For example:

        Syntax:

        <ostype> = centos6, centos7, rhel6, rhel7

        <cloudtype> = amazon, openstack, vmware

      3. Remove the core_installer.bin file.

      4. Perform Steps 1 to 4 (a to e) on the MGMTPOSTGRES_SLAVE.
      5. Exchange the SSH keys between the MGMTPOSTGRES_MASTER and MGMTPOSTGRES_SLAVE

        1. On the MGMTPOSTGRES_MASTER, execute the following to generate a new SSH key. 

        2. On MGMTPOSTGRES_SLAVE, if the .ssh directory does not exist, create it using the following commands before copying the files.

        3. Copy the id_rsa files (~/.ssh/id_rsa and ~/.ssh/id_rsa.pub) from MGMTPOSTGRES_MASTER to the same location on MGMTPOSTGRES_SLAVE.

        4. On the MGMTPOSTGRES_SLAVE, execute the following to generate a new SSH key.

        5. Verify mutual SSH access between the MGMTPOSTGRES_MASTER and MGMTPOSTGRES_SLAVE by running the following command on each VM.

    2.  MGMTPOSTGRES_MASTER – Configure High Availability

      MGMTPOSTGRES_MASTER – Configure High Availability

      To configure high availability for MGMTPOSTGRES_MASTER, follow this procedure.

        1. SSH into the DB instance as a centos user.
        2. Run the following command:

        Invoke the wizard.

        CCM Wizard Path

         

        Configure Postgres HA to ensure the PostgreSQL database HA and enter the information in each field as follows:

        Write this down for future reference!

        Icon
        Write down the Field details in a printed version of the Your Notes section for later use.

        Database Properties

        Description

        Configure_Postgres_HAMaster Hostname: The host name for the master database VM
        Master Private IP: The private IP address of the master database VM
        Slave Hostname: The host name for the slave database VM
        Slave Private IP: The private IP address of the slave database VM

         

        VIP or EIP: The VIP/EIP IP for the database

        Icon

        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

      1. Exit the configuration wizard.

      2. 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 pcsd are active/disabled.

    3.  CCM_SA_PRIMARY and CCM_SA_SECONDARY – Run Core Installer and Setup SSH Communication

      CCM_SA_PRIMARY and SECONDARY – Run Core Installer and Setup SSH Communication

      1. Download package files:

        Icon

        See Installation Overview to understand the required components and the installation options.

        See Installer Overview to understand the types of files.

        1. SSH into the VM instance designated for this component by using the key pair that you used to launch the VM.
        2. Download the following required files for this component from software.cisco.com to the /tmp folder on that VM:

          • core_installer.bin
          • ccm-installer.jar
          • ccm-response.xml
      2. Run the core installer to setup core system components using the following commands:

        For example:

        Syntax:

        <ostype> = centos6, centos7, rhel6, rhel7

        <cloudtype> = amazon, openstack, vmware

      3. Remove the core_installer.bin file.

      4. Log off and log back in as the root user to ensure JAVA Home is set.

      5. Exchange the SSH keys between the CCM_SA_PRIMARY and CCM_SA_SECONDARY

        1. On the CCM_SA_PRIMARY, execute the following to generate a new SSH key. 

        2. Copy the id_rsa files (~/.ssh/id_rsa and ~/.ssh/id_rsa.pub) from CCM_SA_PRIMARY to the same location on CCM_SA_SECONDARY. On CCM_SA_SECONDARY, if the .ssh directory does not exist, create it using the following commands before copying the files!

        3. On the CCM_SA_SECONDARY, execute the following to add a new SSH key.

        4. Verify mutual SSH access between the CCM_SA_PRIMARY and CCM_SA_SECONDARY by running the following command on each VM.

       

    4.  CCM_SA_PRIMARY – Run Appliance Install

      CCM_SA_PRIMARY – Run Appliance Install  

      To run the appliance install for the CCM_SA_PRIMARY, follow this procedure.

      1. SSH into the VM instance using the key pair that you used to launch the VM.
      2. Change to the /tmp directory and modify the ccm-response.xml file as follows:

        Response File EntryValueNotes
        <entry key="db_host" value="default"/>The db_host IP address depends on the database set up for the CCM:
        • Standalone DB: Use the instance IP address
        • HA DB: Use the VIP address

        Required
      3. Run the appliance installer to setup the CCM.

      4. Reboot the CCM VM.

    5.  CCM_SA_SECONDARY – Run Appliance Install

      CCM_SA_SECONDARY – Run Appliance Install  

      To run the appliance install for the CCM_SA_SECONDARY, follow this procedure.

      1. SSH into the VM instance using the key pair that you used to launch the VM.

      2. Change to the /tmp directory and modify the ccm-response.xml file as follows:

        Response File EntryValueNotes
        <entry key="db _enable" value="true "/> Change the value to false.

        In the HA setup, the appliance installer on the secondary instance should not update the database.

        <entry key="db_host" value="default"/>

        The db_host IP address depends on the database set up for the CCM.

        1. Standalone DB:  Use the instance IP address.

        2. HA DB: Use the VIP address

        Required.
      3. Run the appliance installer to setup the CCM.

      4. Reboot the CCM VM.

    6.  CCM_SA_PRIMARY – Configure High Availability

      CCM_SA_PRIMARY – Configure High Availability

      To configure high availability for CCM_SA_PRIMARY, follow this procedure.

        1. SSH into the CCM instance as a centos user.
        2. Run the following command:

         

      1. Invoke the CCM wizard.

        CCM Wizard Path
      2. Configure the properties.

        Write this down for future reference!

        Icon
        Write down the Field details in a printed version of the Your Notes section for later use.

        CCM Properties

        Description

        Configure_HAPrimary Node Private IP: The IP address of the primary CCM VM
        Secondary Node Private IP: The IP address of the secondary CCM VM

        Public DNS: Use the DNS or IP of the CCM_LB – Used by the CCO VM to communicate with the CCM VM.

        Hazelcast IP: Provide either Public or Private IP address of the both primary and secondary CCM VM separated by comma. If the two CCM VMs are configured on:

        • The same network, then use the Private IPs.
        •  Different networks, then use the Public IPs.

        External URL: Optional for non-HA CCM scenarios – Use the CCM_LB_IP

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

        After configuring HA on the CCM primary server, the following message is displayed:
        Restarting secondary ccm tomcat failed due to cliqruser may not have sudo permission.

        At this point, you must manually restart tomcat on the secondary CCM server.

      4. Run the following command on the CCM secondary server to restart the Tomcat server.


      5. Exit the CCM configuration wizard.

    7.  CCM_SA_PRIMARY and CCM_SA_SECONDARY – Configure Basic Properties

      Configure CCM Wizard Properties

      To configure the CCM wizard properties, follow this procedure.

        1. SSH into the CCM instance as a CentOS user.
        2. Run the following command:

      1. Invoke the CCM wizard.

        CCM Wizard Path
      2. Configure the server properties.

        Write this down for future reference!

        Icon
        Write down the Field details in a printed version of the Your Notes section for later use.

        CCM Properties

        Description

        Mail

        SMTP server details to send mail notifications. If you retain the default settings, the SMTP sever details are not configured.

        • SMTP Host: smtp.gmail.com
        • SMTP Port: Defaults to 465
        • SMTP Auth: Boolean setting
          • True = Authentication is required for the SMTP server.
          • False = Authentication is not required for the SMTP server.

        Mail_User

        Mail authentication and configuration details to send mail notifications. If you retain the default settings, the mail functionality is not be configured and emails are not sent.

        • Mail User: Your email address for the SMTP server
        • Password: The password to log into the SMTP server
        • From User: The email address (no reply) to initiate emails from the CCM server
        • Display Name: The name to be displayed when you initiate emails from the CCM server
        Server_info (Required)

        Public DNS: DNS (or IP address) of the CCM – Used by the CCO VM to communicate with the CCM VM.

        Monitor URL: Monitor VM's complete URL. For example, https://<MON or MON_LB IP address>:8443.

        • Requires HTTPS protocol.
        • Used by the CCM VM to retrieve the health status from the Monitor VM.

        Hazelcast IP: Private IP address of the CCM VM – Used internally by the CloudCenter platform. Required for HA Mode.

        External URL: The CloudCenter External URL for the CCM server. Required for HA Mode.

        Config_App_Logo

        Used by the application profile templates.

        ESB_Info

        Required only if you installed Enterprise Service Bus (ESB), an optional component that is not installed in CloudCenter appliances by default.

        Network

        Use the defaults if you are not making any changes to these settings.

        • Hostname:
        • Interface:
        DB
        (Effective CloudCenter 4.7.0)
        • IP or Hostname: DNS or IP of the Database
          • Local host: Default, does not include the flyway migrate configuration
          • Remote host, includes the flyway migrate configuration – see the last bullet in this row.
        • Authentication credentials for the database (either local or remote).
          • Username:
          • Password:
        •  Flyway Migrate: Optional. Remote Host Configure the CCM to a remote database by providing the IP address of the remote database. When you provide the IP address, you see an additional screen to configure the flyway migrate process.
          • Yes: Flyway migration takes place.
          • No: Only the configuration files are updated.
          Icon

          DB configuration is required for standalone database deployments.

        ELK_Info
        (Effective CloudCenter 4.7.0)
        • ELK Host: Specify the IP address for the ELK host (Monitor VM).
        • Elasticsearch Port: Displays 8881 by default.
        • Logstash Port: Displays 4560 by default.
        • Kibana Port: Displays 8882 by default.
        • ELK User: The default ELK Username = logreader.
        • ELK Password: The default ELK Password is re@d0nly (zero between d and n) (change this password after the initial login – see Download Log File for additional context).
        • Host Identifier: A Unique ID for the server – be sure to prefix the unique identifier with CCM_ for example, CCM_1
        • Host Identifier List: Only applies to environments using the HA mode – provide a list of comma separated unique host identifiers for all ELK/Monitor hosts in a HA setup = for example, CCM_1,CCM_2,myCCM.

          Icon

          In an environment operating in HA mode, if you have two CCM instances with unique IDs configured as CCM_1,CCM_2 in their respective server.properties file, then this property should state CCM_1,CCM_2 in both CCM instances. Each CCM must be aware of the unique ID of the other CCM(s) when in HA mode.

      3. Exit the CCM configuration wizard.

      4. Select Yes, to restart the Tomcat service for the changes to take effect.

      You have successfully installed the CCM instance! You can now proceed to the next step:

      • If you are installing a Health Monitor component – see Health Monitor Installation (Optional)

    8.  CCM_LB

      CCM_LB 

       

      Icon

      See CCM_LB Ports for the complete list of ports that need to be open for your deployment.


      Here is a sample configuration to load balance a CentOS7.x VM with HAProxy for the CCM.

      1. SSH into the VM instance using the key pair that you used to launch the VM.
      2. Install HAProxy as the root user. 


         

      3. Create .pem files for haproxy configuration for CCM_LB in the CCM Primary server.
        1. Run the following commands.

          Icon

          You can name the mgmtserver and ca pem files as required for your environment, however, be sure to append them with the .pem extension.

           

        2. Place the mgmtserver.pem and ca.pem files created earlier to the CCM_LB server in the  /etc/haproxy location.

         

      4. Modify the HAProxy config file as displayed below.

      5. Start the HAProxy service and verify that the status response is active.

       

Cloud Health Monitor (Optional)

The Cloud Health Monitor (monitor) is an optional, independent CloudCenter component that monitors the cloud and CCO health status. The monitor performs the following functions:

  • Periodically checks the health status of the CCO for each cloud.
  • Persists cloud health status change events.
  • Displays results from these checks on the CCM UI Dashboard.

The Elasticsearch, Logstash, and Kibana, collectively referred to as the ELK stack, are installed by default when you install the Health Monitor. To be able to Download Log Files, be sure to install this component, even if it is optional.

Install Monitor

  • MONITOR NON-HA                                                                                                                                           

    1.  Monitor – Run Core and Monitor Installer

      Monitor – Run the Monitor Installer

      To configure a health monitor, follow this procedure.

      1. Download package files:

        Icon

        See Installation Overview to understand the required components and the installation options.

        See Installer Overview to understand the types of files.

        1. SSH into the VM instance designated for this component by using the key pair that you used to launch the VM.
        2. Download the following required files for this component from software.cisco.com to the /tmp folder on that VM:

          • core_installer.bin
          • monitor-installer.jar
          • monitor-response.xml
      2. Run the core installer to setup core system components using the following commands:

        For example:

        Syntax:

        <ostype>= centos6, centos7, rhel6, rhel7

        <cloudtype>= amazon, azure, azurerm, azurepack, google, opsource, openstack, softlayer, vmware, or vcd (run the ./core_installer.bin help command for a complete list)

      3. Log off and log back in as the root user to ensure JAVA Home is set.

      4. Change to the /tmp directory.


      5. Run the appliance installer to setup the Monitor.

      6. Reboot the Monitor VM.

    2.  Monitor – Configure Monitor Properties

      Monitor – Configure Monitor Properties

        1. SSH into the MONITOR instance as a centos user.
        2. Run the following command:

      1. Invoke the wizard.

        Monitor Wizard Path
      2. Configure the properties for the Monitor instance.

        Write this down for future reference!

        Icon

         Write down the Field details in a printed version of the Your Notes section for later use.

        GroupNotes
        CCM_Info
        • Monitor ID – A unique (alphanumeric) identifier used for the health check instance.
        • CCM Hostname/URL (Required)
          • CCM_IP or 
          • CCM_SA_IP or
          • CCM_LB_IP
        • Monitor User – The User ID configured on the CCM server to enable health check for cloud  regions.
          • To perform a health check on all activated cloud regions, set this value as 2 (2 is the CloudCenter’s root administrator’s User ID).
          • To perform a health check on specific cloud regions, create and activate a new user with those specific regions and use that user’s User ID as value for this property. To get the User ID, use the v1 User Management APIs.
        ELK_LoginFor the ELK/Monitor host.
        • ELK User: The default ELK Username = logreader.
        • ELK Password: The default ELK Password is re@d0nly (zero between d and n) (change this password after the initial login – see Download Log File for additional context).
      3. Verify your changes and Exit the Monitor configuration wizard.

      4. Select Yes, to restart the Tomcat service for the changes to take effect.

      You have successfully configured the Monitor instance! You can now proceed to the Per CloudCenter Region Installation section and install the CloudCenter components for each Cloud.


      Back to Phase 4: Install Components

  • MONITOR HA                                                                                                                                                  

    1.  MON_PRIMARY – Run Core and Monitor Installer

      MON_PRIMARY – Run Core Installer

      1. Download package files:

        Icon

        See Installation Overview to understand the required components and the installation options.

        See Installer Overview to understand the types of files.

        1. SSH into the VM instance designated for this component by using the key pair that you used to launch the VM.
        2. Download the following required files for this component from software.cisco.com to the /tmp folder on that VM:

          • core_installer.bin
          • monitor-installer.jar
          • monitor-response.xml
      2. Run the core installer to setup core system components using the following commands:

        For example:

        Syntax:

        <ostype>= centos6, centos7, rhel6, rhel7

        <cloudtype>= amazon, azure, azurerm, azurepack, google, opsource, openstack, softlayer, vmware, or vcd
        (run the ./core_installer.bin help command for a complete list)

      3. Log off and log back in as the root user to ensure JAVA Home is set.

      4. Change to the /tmp directory.


      5. Run the appliance installer to setup the Monitor.

      6. Reboot the primary Monitor VM.

    2.  MON_SECONDARY – Run Core and Monitor Installer

      MON_SECONDARY – Run Core Installer

      To configure a primary health monitor, follow this procedure.

      1. Download package files:

        Icon

        See Installation Overview to understand the required components and the installation options.

        See Installer Overview to understand the types of files.

        1. SSH into the VM instance designated for this component by using the key pair that you used to launch the VM.
        2. Download the following required files for this component from software.cisco.com to the /tmp folder on that VM:

          • core_installer.bin
          • monitor-installer.jar
          • monitor-response.xml
      2. Run the core installer to setup core system components using the following commands:

        For example:

        Syntax:

        <ostype>= centos6, centos7, rhel6, rhel7

        <cloudtype>= amazon, azure, azurerm, azurepack, google, opsource, openstack, softlayer, vmware, or vcd
        (run the ./core_installer.bin help command for a complete list)

      3. Log off and log back in as the root user to ensure JAVA Home is set.

      4. Change to the /tmp directory.


      5. Run the appliance installer to setup the Monitor.

      6. Reboot the secondary Monitor VM.

    3.  Monitor – Configure Monitor Properties

      Monitor – Configure Monitor Properties

        1. SSH into the MONITOR instance as a centos user.
        2. Run the following command:

      1. Invoke the wizard.

        Monitor Wizard Path
      2. Configure the properties for the Monitor instance.

        Write this down for future reference!

        Icon

         Write down the Field details in a printed version of the Your Notes section for later use.

        GroupNotes
        CCM_Info
        • Monitor ID – A unique (alphanumeric) identifier used for the health check instance.
        • CCM Hostname/URL (Required)
          • CCM_IP or 
          • CCM_SA_IP or
          • CCM_LB_IP
        • Monitor User – The User ID configured on the CCM server to enable health check for cloud  regions.
          • To perform a health check on all activated cloud regions, set this value as 2 (2 is the CloudCenter’s root administrator’s User ID).
          • To perform a health check on specific cloud regions, create and activate a new user with those specific regions and use that user’s User ID as value for this property. To get the User ID, use the v1 User Management APIs.
        ELK_LoginFor the ELK/Monitor host.
        • ELK User: The default ELK Username = logreader.
        • ELK Password: The default ELK Password is re@d0nly (zero between d and n) (change this password after the initial login – see Download Log File for additional context).
      3. Verify your changes and Exit the Monitor configuration wizard.

      4. Select Yes, to restart the Tomcat service for the changes to take effect.

      You have successfully configured the Monitor instance! You can now proceed to the Per CloudCenter Region Installation section and install the CloudCenter components for each Cloud.


      Back to Phase 4: Install Components

    4.  MON_LB

      MON_LB 

      Load balancing can be done through HAProxy, NGiNX, Apache2, or a cloud that is natively available to services, like AWS Elastic Load Balancer (ELB). To configure the load balancer service and ensure Monitor load balancing, be sure to listen on port 8443 and balance the request at 8443 on both the MON_PRIMARY and MON_SECONDARY servers.

      Icon

      See MON_LB Ports for the complete list of ports that need to be open for your deployment.

       

      The following load balancing configuration was performed on CentOS7.x VM with HAProxy for the Monitor VM.

      1. SSH into the VM instance using the key pair that you used to launch the MON VM.
      2. Install HAProxy as the root user.

      3. Modify HAProxy config file as below

      4. Start the HAProxy service and check the status, it should be active

         

       

      Back to Phase 4: Install Components

     

 

Per Cloud Region Installation (Required)

For Each Region

Be sure to set up the following components that are to be managed by a CloudCenter deployment for each cloud region (public cloud, private cloud, or datacenter).

  1.  Dedicated External Script Executor

    Dedicated External Script Executor (Conditional)

    The CloudCenter platform provides the ability to use custom scripts that are executed during various phases of the application lifecycle. These custom scripts run inside a Docker-based script executor and depend on the OS in use by each CCO.

    OS VersionInstallation Nuances

    RHEL 7.x

    and

    CentOS 7.x

    By default, these custom scripts are embedded in the CCO OS(s) by CloudCenter.

    See EXT_SCRIPT_EXECUTOR Ports for networking nuances.

    Icon

    If you opt to setup a dedicated script executor (standalone Docker container) for regions using RHEL 7x or CentOS 7x for the CCO server to address increased scalability considerations, follow the procedure specified below in the Install Dedicated External Script Executor section below.

    EXT_SCRIPT_EXECUTOR – Run Core Installers

    1. Download package files:

      Icon

      See Installation Overview to understand the required components and the installation options.

      See Installer Overview to understand the types of files.

      1. SSH into the VM instance designated for this component by using the key pair that you used to launch the VM.
      2. Download the following required files for this component from software.cisco.com to the /tmp folder on that VM:

        • core_installer.bin

    2. Verify that Port 2376 is open on the standalone Docker instance and restricted ONLY to the CCO IP so the CCO can access the Docker server. See Phase 2: Configure Network Rules for additional details.
    3. Run the core installer to setup core system components using the following commands:

      For example:

      Syntax:

      • <ostype>= centos7, rhel7

      • <cloudtype>= amazon, azure, azurerm, azurepack, google,  opsource, openstack , softlayer, vmware, vcd (run the ./core_installer.bin help command for a complete list)

    4. Remove the core_installer.bin file.

    5.  This step is only required for CloudCenter 4.6.x

      Manually edit the /user/local/osmosix/etc/container.properties file to update the Docker host location and the HTTPS port number.

      Icon

      Effective CloudCenter 4.7.0, you do not need to perform this step as the container.properties file is independent of the CCO server and the Primary CCO wizard handles the changes when you Configure CCO Properties.

    6. Reboot the Docker VM.

    You have successfully configured the external script executor! You can now proceed to the next step:

    • If you are installing a dedicated Guacamole server – see Dedicated Guacamole Server (Optional)

     

     

  2.  Dedicated Gucamole Server

    Dedicated Guacamole Server (Optional)

    This is an optional component that you may choose to deploy if you do not want to expose the AMQP servers to end users. By default, the Guacamole server is installed on the same VM as AMQP.

    • The CloudCenter platform use a Guacamole server to enable web based SSH/VNC/RDP to Virtual Machines (VMs) launched during the application lifecycle process. The Guacamole component is embedded, by default, in the AMQP server.

    • If you do not want the AMQP IP address to be routable by the end user, you may opt to setup a dedicated (standalone) Guacamole server for a cloud region.

    1. GUAC NON-HA

      1.  GUAC – Run Core Installers

        GUAC – Run Core Installers

        1. Download package files:

          Icon

          See Installation Overview to understand the required components and the installation options.

          See Installer Overview to understand the types of files.

          1. SSH into the VM instance designated for this component by using the key pair that you used to launch the VM.
          2. Download the following required files for this component from software.cisco.com to the /tmp folder on that VM:

            • core_installer.bin

            • cco-installer.jar

            • conn_broker-response.xml

        2. Run the core installer to setup core system components using the following commands:

          For example:

          Syntax:

          • <ostype>= centos7, rhel7

          • <cloudtype>= amazon, azure, azurerm, azurepack, google,  opsource, openstack, softlayer, vmware, vcd

        3. Remove the core_installer.bin file.

        4. Log off and log back in as the root user to set the JAVA home.


        5. Change to the /tmp directory. 


        6. Run the appliance installer to setup GUAC.


        7. Reboot the GUAC VM.
      2.  GUAC – Configure CCM/CCO Properties for Guacamole

        GUAC – Configure CCM/CCO Properties for Guacamole

          1. SSH into the GUA instance as a centos user.
          2. Run the following command:

        1. Invoke the GUA wizard.

          GUA Wizard Path
        2. Configure the CCO and CCM properties.

          Write this down for future reference!

          Icon
          Write down the Field details in a printed version of the Your Notes section for later use.
        3. Configure the properties for the CCM and CCO VMs:

          Group

          Possible IP Addresses

          CCM_Info

          CCM Host:

          CCM_IP or  CCM_SA_IP or CCM_LB_IP

          CCO_InfoCCO Host:
          CCO_IP
          or CCO_LB_IP
        4. Verify your changes and Exit the GUA configuration wizard.

        You have successfully configured a Guacamole server! You can now proceed to the AMQP (Required) section.

    2. GUAC HA (CloudCenter 4.7.0)                                                                                                                         

      1.  GUAC_PRIMARY – Run Core and Appliance Installers

        GUAC_PRIMARY – Run Core and Appliance Installers

        1. Download package files:

          Icon

          See Installation Overview to understand the required components and the installation options.

          See Installer Overview to understand the types of files.

          1. SSH into the VM instance designated for this component by using the key pair that you used to launch the VM.
          2. Download the following required files for this component from software.cisco.com to the /tmp folder on that VM:

            • core_installer.bin 

            • cco-installer.jar

            • conn_broker-response.xml

        2. Run the core installer to setup core system components using the following commands:

          For example:

          Syntax:

          • <ostype>= centos7, rhel7

          • <cloudtype>= amazon, azure, azurerm, azurepack, google,  opsource, openstack, softlayer, vmware, vcd (run the ./core_installer.bin help command for a complete list)

        3. Remove the core_installer.bin file.

        4. Log off and log back in as the root user to set the JAVA home.


        5. Change to the /tmp directory. 


        6. Run the appliance installer to setup GUAC.


        7. Reboot the GUAC_PRIMARY VM.

      2.  GUAC_SECONDARY – Run Core and Appliance Installers

        GUAC_SECONDARY – Run Core and Appliance Installers

        1. Download package files:

          Icon

          See Installation Overview to understand the required components and the installation options.

          See Installer Overview to understand the types of files.

          1. SSH into the VM instance designated for this component by using the key pair that you used to launch the VM.
          2. Download the following required files for this component from software.cisco.com to the /tmp folder on that VM:

            • core_installer.bin

            • cco-installer.jar

            • conn_broker-response.xml

        2. Run the core installer to setup core system components using the following commands:

          For example:

          Syntax:

          • <ostype>= centos7, rhel7

          • <cloudtype>= amazon, azure, azurerm, azurepack, google,  opsource, openstack, softlayer, vmware, vcd (run the ./core_installer.bin help command for a complete list)

        3. Remove the core_installer.bin file.

        4. Log off and log back in as the root user to set the JAVA home.


        5. Change to the /tmp directory. 


        6. Run the appliance installer to setup GUAC.


        7. Reboot the GUAC_SECONDARY VM.

      3.  GUAC_PRIMARY – Configure CCM/CCO Properties for Guacamole

        GUAC_PRIMARY – Configure CCM/CCO Properties for Guacamole

          1. SSH into the GUA instance as a centos user.
          2. Run the following command:

        1. Invoke the GUA wizard.

          GUA Wizard Path
        2. Configure the CCO and CCM properties.

          Write this down for future reference!

          Icon
          Write down the Field details in a printed version of the Your Notes section for later use.
        3. Configure the properties for the CCM and CCO VMs:

          Group

          Possible IP Addresses

          CCM_Info

          CCM Host:

          CCM_IP or  CCM_SA_IP or CCM_LB_IP

          CCO_InfoCCO Host:
          CCO_IP
          or CCO_LB_IP
        4. Verify your changes and Exit the GUA configuration wizard.

        You have successfully configured the Guacamole server! You can now proceed to the next step.

      4.  GUAC_SECONDARY – Configure CCM/CCO Properties for Guacamole

        GUAC_SECONDARY – Configure CCM/CCO Properties for Guacamole

          1. SSH into the GUA instance as a centos user.
          2. Run the following command:

        1. Invoke the GUA wizard.

          GUA Wizard Path
        2. Configure the CCO and CCM properties.

          Write this down for future reference!

          Icon
          Write down the Field details in a printed version of the Your Notes section for later use.
        3. Configure the properties for the CCM and CCO VMs:

          Group

          Possible IP Addresses

          CCM_Info

          CCM Host:

          CCM_IP or  CCM_SA_IP or CCM_LB_IP

          CCO_InfoCCO Host:
          CCO_IP
          or CCO_LB_IP
        4. Verify your changes and Exit the GUA configuration wizard.

        You have successfully configured the Guacamole server! You can now proceed to the next step.

      5.  GUAC_LB

        GUAC_LB

        The GUAC load balancing can be done through HAProxy, NGiNX, Apache2, or a cloud that is natively available to services, like AWS Elastic Load Balancer (ELB). To configure the load balancer service and ensure GUAC load balancing, be sure to listen on port 5671 and balance the request at 443 on both the GUAC_PRIMARY and GUAC_SECONDARY servers.

        The following load balancing configuration was performed on CentOS7.x VM with HAProxy for the GUAC VM.

        1. SSH into the VM instance using the key pair that you used to launch the VM.
        2. Install HAProxy as the root user.

        3. Modify HAProxy config file as below

        4. To bind to 443 port you must disable SELinux – run the following command to disable SELinux.

        5. Start the HAProxy service and check the status, it should be active

           

       

       

  3.  AMQP (Required)

    AMQP (Required)

    The CloudCenter platform features Advanced Message Queuing Protocol (AMQP) based communication between the CCO and the Agent VM. The CloudCenter platform incorporates RabbitMQ as the open source message broker for AMQP implementation.

    Icon

    If the application VM (worker) runs in isolated networks (like Amazon's VPC), ensure that the application VM has outbound connectivity to the AMQP server.

    The following diagram shows the association between CloudCenter components and AMQP. Note that one AMQP instance is required for each CCO implementation.

    amqp

     

    The /tmp Alternative

    You can download installation files to a directory of your choice. The procedure provided in the CloudCenter documents, recommend using the /tmp folder as the download folder. In some cases, you may not want to use /tmp folder as the temp location as this directory may not allow files to be executed in your environment.

    To install CloudCenter on systems where /tmp is set to nosuid or noexec, issue the following command before downloading the component files:

    Install AMQP

    1. AMQP NON-HA                                                                                                                                                   

      1.  AMQP – Run Core and Appliance Installers

        AMQP – Run Core and Appliance Installers

        1. Download package files:

          Icon

          See Installation Overview to understand the required components and the installation options.

          See Installer Overview to understand the types of files.

          1. SSH into the VM instance designated for this component by using the key pair that you used to launch the VM.
          2. Download the following required files for this component from software.cisco.com to the /tmp folder on that VM:

            • core_installer.bin
            • cco-installer.jar
            • conn_broker-response.xml
        2. Run the core installer to setup core system components using the following commands:

          For example:

          Syntax:

          <ostype>= centos6, centos7, rhel6, rhel7

          <cloudtype>= amazon, azure, azurerm, azurepack, google, opsource, openstack, softlayer, vmware, vcd

        3. Remove the core_installer.bin file.

           

        4. Log off and log back in as the root user to ensure JAVA Home is set.

        5. Change to the /tmp directory.


        6. Run the appliance installer to setup AMQP. 

        7. Reboot the AMQP VM.

           

      2.  AMQP – Configure CCM/CCO Properties for Guacamole Server

        AMQP  – Configure CCM/CCO Properties for Guacamole Server

        Dedicated GUAC Setup?

        Icon

        This GUA config wizard step is not required if you have set up a dedicated Guacamole server.

          1. SSH into the GUA instance as a centos user.
          2. Run the following command:

        1. Invoke the GUA wizard.

          GUA Wizard Path
        2. Configure the CCM and CCO (once installed) properties.

          Write this down for future reference!

          Icon
          Write down the Field details in a printed version of the Your Notes section for later use.
        3. Configure the properties for the CCM and CCO (once installed) VMs:

          GroupPossible IP Addresses

          CCM_Info

          CCM Host:

          CCM_IP or  CCM_SA_IP or CCM_LB_IP

          CCO_InfoCCO Host (once installed):
          CCO_IP or  CCO_LB_IP
        4. Verify your changes and Exit the GUA configuration wizard.

        5. Select Yes, to restart the Tomcat service for the changes to take effect.

          Icon

          If you are installing the AMQP instance for the first time, then you may need to wait for a few minutes to ensure that all users are listed. You can verify that all users are listed by running the following commands:

        You have successfully configured the AMQP instance! Proceed to the CCO (Required) section.


    2. AMQP HA                                                                                                                                                         

      1.  AMQP_PRIMARY – Run Core and Appliance Installers

        AMQP_PRIMARY – Run Core and Appliance Installers

        1. Download package files:

          Icon

          See Installation Overview to understand the required components and the installation options.

          See Installer Overview to understand the types of files.

          1. SSH into the VM instance designated for this component by using the key pair that you used to launch the VM.
          2. Download the following required files for this component from software.cisco.com to the /tmp folder on that VM:

            • core_installer.bin
            • cco-installer.jar
            • conn_broker-response.xml
        2. Run the core installer to setup core system components using the following commands:

          For example:

          Syntax:

          <ostype>= centos6, centos7, rhel6, rhel7

          <cloudtype>= amazon, azure, azurerm, azurepack, google, opsource, openstack, softlayer, vmware, and vcd (run the ./core_installer.bin help command for a complete list)

        3. Remove the core_installer.bin file.

        4. Log off and log back in as the root user to ensure JAVA Home is set.

        5. Change to the /tmp directory.


        6. Run the appliance installer to setup AMQP. 

        7. Reboot the AMQP VM.

      2.  AMQP_PRIMARY – Configure CCM/CCO Properties for Guacamole Server

        AMQP_PRIMARY – Configure CCM/CCO Properties for Guacamole Server

        Dedicated GUAC Setup?

        Icon

        This GUA config wizard step is not required if you have set up a dedicated Guacamole server.

          1. SSH into the GUA instance as a centos user.
          2. Run the following command:

        1. Invoke the GUA wizard.

          GUA Wizard Path
        2. Configure the CCO and CCM properties.

          Write this down for future reference!

          Icon
          Write down the Field details in a printed version of the  Your Notes section for later use.
        3. Configure the properties for the CCM and CCO VMs:

          GroupHostPossible IP Addresses

          CCM_Info

          CCM Host

          CCM Host: (Required)

          CCM_IP or  CCM_SA_IP or CCM_LB_IP

          CCO_InfoCCO HostCCO Host: (Required)
          CCO_IP or  CCO_LB_IP
        4. Verify your changes and Exit the GUA configuration wizard.

        5. Reboot the AMQP_PRIMARY VM.

         

      3.  AMQP_SECONDARY – Run Core and Appliance Installers

        AMQP_SECONDARY – Run Core and Appliance Installers

        1. Download package files:

          Icon

          See Installation Overview to understand the required components and the installation options.

          See Installer Overview to understand the types of files.

          1. SSH into the VM instance designated for this component by using the key pair that you used to launch the VM.
          2. Download the following required files for this component from software.cisco.com to the /tmp folder on that VM:

            • core_installer.bin
            • cco-installer.jar
            • conn_broker-response.xml
        2. Run the core installer to setup core system components using the following commands:

          For example:

          Syntax:

          <ostype>= centos6, centos7, rhel6, rhel7

          <cloudtype>= amazon, azure, azurerm, azurepack, google, opsource, openstack, softlayer, vmware, and vcd (run the ./core_installer.bin help command for a complete list)

        3. Remove the core_installer.bin file.

           

        4. Log off and log back in as the root user to ensure JAVA Home is set.

        5. Change to the /tmp directory.

        6. Run the appliance installer to setup AMQP. 

        7. Reboot the AMQP VM.

      4.  AMQP_SECONDARY – Configure CCM/CCO Properties for Guacamole Server

        AMQP_SECONDARY – Configure CCM/CCO Properties for Guacamole Server

        Dedicated GUAC Setup?

        Icon

        This GUA config wizard step is not required if you have set up a dedicated Guacamole server.

          1. SSH into the GUA instance as a centos user.
          2. Run the following command:

        1. Invoke the GUA wizard.

          GUA Wizard Path
        2. Configure the CCO and CCM properties.

          Write this down for future reference!

          Icon
          Write down the Field details in a printed version of the Installation Approach > Your Notes section for later use.
        3. Configure the properties for the CCM and CCO VMs:

          GroupFieldPossible IP Addresses

          CCM_Info

          CCM Host

          CCM Host: (Required)

          CCM_IP or  CCM_SA_IP or CCM_LB_IP

          CCO_InfoCCO HostCCO Host: (Required)
          CCO_IP or CCO_LB_IP
        4. Verify your changes and Exit the GUA configuration wizard.

        5. Reboot the AMQP_SECONDARY VM.

        You have successfully configured the AMQP server! You can now proceed to the next step.

      5.  AMQP_PRIMARY and AMQP_SECONDARY – Cluster Configuration

        AMQP_PRIMARY and AMQP_SECONDARY – Cluster Configuration

        1. SSH into both VM instances (AMQP_PRIMARY and AMQP_SECONDARY) using the key pair that you used to launch each VM.
        2. Verify that the .erlang.cookie (a hidden file located at /var/lib/rabbitmq) are same on both the AMQP servers.

          1. If they are not the same, copy the .erlang.cookie file from the AMQP primary server to the AMQP secondary server in the /var/lib/rabbitmq location or vice-versa.
          2. After copying the .erlang.cookie file from the primary to the secondary AMQP server or vice-versa, change the owner and permission for the .erlang.ccokie file. Run the following commands to change the owner and permission of the file on server where it is copied.

             

          3. After copying the .erlang cookie file:

            1. Reboot the Secondary AMQP VM.

            2. Run the following commands on both the AMQP Primary and AMQP Secondary servers.

        3. Detach the AMQP servers using the following command.

           

        4. On the AMQP_SECONDARY server, run the following commands.

          Hostname NOT the IP!

          Icon

          Verify your DNS resolution, if required, as you must provide the hostname at this point – not the IP address for the AMQP primary isntance.

        5. Verify the AMQP cluster status on both AMQP servers.

        6. Set the mirroring policy by issuing the following command on either of the AMQP servers.

           

        7. Verify the policy change by issuing the following command.

        8. Modify the rabbitmq config file (located at /etc/rabbitmq) on both the AMQP servers by adding a line to the rabbit array (for autoheal).

        9. Restart rabbitmq on both AMQP servers.

      6.  AMQP_LB

        AMQP_LB

        The AMQP load balancing can be done through HAProxy, NGiNX, Apache2, or a cloud that is natively available to services, like AWS Elastic Load Balancer (ELB). To configure the load balancer service and ensure AMQP load balancing, be sure to listen on port 5671 and balance the request at 443 on both the AMQP_PRIMARY and AMQP_SECONDARY servers.

        Icon

        See AMQP_LB Ports for the complete list of ports that need to be open for your deployment.

        The following load balancing configuration was performed on CentOS7.x VM with HAProxy for the AMQP VM.

        1. SSH into the VM instance using the key pair that you used to launch the VM.
        2. Install HAProxy as the root user.

        3. Modify HAProxy config file as below

        4. To bind to 5671 port you must disable SELinux – run the following command to disable SELinux.

        5. Start the HAProxy service and check the status, it should be active

           

  4.  CCO (Required)

    CCO (Required)

    The transparent to users CloudCenter Orchestrator (CCO) is deployed to every supported cloud region. The CCO is a backend server that intelligently interacts with cloud endpoints to handle application deployment and runtime management. CCO decouples an application from its underlying cloud infrastructure in order to reduce the cloud deployment complexity.

    A single CCO can manage up to 10,000 Virtual Machines (VMs) in a cloud region.

     Cloud-Specific References
    Cloud Type

    Supports One (Only one combination of these per CCO)

    Supports Multiple (Any number of these per CCO)

    AWSRegion
    • Accounts
    • Sub-Accounts
    • Identity and Access Management (IAM)

    vCenterOne vCenter
    • Datacenter objects
    • Clusters
    • Resource pools
    • Accounts
    • Datastores
    • Datastore clusters
    OpenStackRegion
    • Tenants
    • Networks
    AzureRegion  
    • Networks
    • Cloud services
    SoftLayerRegion
    • Accounts
    • Networks
    GCERegionProjects

    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 – Add the following parameters to the JAVA_OPTS environment variable
      Sample /usr/local/tomcat/bin/setenv.sh with added parameters in JAVA_OPTS
    3. Additional parameters may be required if the CCM or CCO servers need to reach network resources, bypassing the proxy.

      OPTIONAL – Sample /usr/local/tomcat/bin/setenv.sh bypassing the proxy
    4. Restart the Tomcat service.

    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

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

    The /tmp Alternative

    You can download installation files to a directory of your choice. The procedure provided in the CloudCenter documents, recommend using the /tmp folder as the download folder. In some cases, you may not want to use /tmp folder as the temp location as this directory may not allow files to be executed in your environment.

    To install CloudCenter on systems where /tmp is set to nosuid or noexec, issue the following command before downloading the component files:

    Install CCO

    1. CCO NON-HA                                                                                                                                                     

      1.  CCO – Run Core and Appliance Installers

        CCO – Run Core and Appliance Installers

        1. Download package files:

          Icon

          See Installation Overview to understand the required components and the installation options.

          See Installer Overview to understand the types of files.

          1. SSH into the VM instance designated for this component by using the key pair that you used to launch the VM.
          2. Download the following required files for this component from software.cisco.com to the /tmp folder on that VM:

            • core_installer.bin
            • cco-installer.jar
            • cco-response.xml
        2. Run the core installer to setup core system components using the following commands:

          For example:

          Syntax:

          <ostype>= centos6, centos7, rhel6, rhel7

          <cloudtype>= amazon, azure, azurerm, azurepack, google, opsource, openstack, softlayer, vmware, or vcd (run the ./core_installer.bin help command for a complete list)

        3. Remove the core_installer.bin file.

        4. Log off and log back in as the root user to ensure JAVA Home is set.

        5. Change to the /tmp directory.


        6. Run the appliance installer to setup the CCO. 

        7. Reboot the CCO VM.

      2.  CCO – Configure CCO Properties

        CCO – Configure CCO Wizard Properties

          1. SSH into the CCO instance as a centos user.
          2. Run the following command:

        1. Invoke the CCO wizard.

          CCO Wizard Path
        2. Configure the server properties.

          Write this down for future reference!

          Icon
          Write down the Field details in a printed version of the Your Notes section for later use.
          GroupNotes

          AgentBundle

          Use the defaults.

          • If you are using the custom bundle, replace cdn.cliqr.com with the custom bundle store IP or DNS
          • If you are using the package store, replace repo.cliqrtech.com with the custom package store IP or DNS

          AMQP_Server

          • AMQP Server IP: AMQP_IP or AMQP_LB_IP
          • AMQP Port: 5671
          NetworkHostname: Configure the Network details for your CCO environment. This is an optional step to configure the Private IP of the VM. You can generally configure this information if the VM does not have preset IP or hostname or if you need to override an existing IP or Hostname.

          Guacamole

           

          • Connection Broker Host: AMQP_IP or AMQP_LB_IP 
          • Connection Broker Port1: 7788
          • Connection Broker Port2: 7789

          Docker

          • Docker Registry URL: Set only if custom docker registry is used.
          • Docker CACert URL: Set only if docker registry uses SSL with custom CA Certificates.

          ELK_Info

          (Effective CloudCenter 4.7.0)

          • ELK Host: Specify the IP address for the ELK/Monitor host.
          • Elasticsearch Port: Displays 8881 by default.
          • Logstash Port: Displays 4560 by default.
          • Host Identifier: The Unique ID for the server – be sure to prefix the unique identifier with CCO_ for example, CCO_Openstack_regionOne or CCO_Amazon_east.
          • Host Identifier List: This field only applies to environments using the HA mode – provide a list of comma separated unique host Identifiers for all ELK/Monitor hosts in a HA setup = for example, CCO1,CCO2,myCCO.

            Icon

            In an environment operating in HA mode, if you have three CCO instances with unique IDs configured as CCO_1,CCO_2,CCO_3 in their respective server.properties file, then this property should state CCO_1,CCO_2,CCO_3 in each CCO instance. Each CCO must be aware of the unique ID of the other CCO(s) when in HA mode.

        3. Verify your changes and Exit the CCO configuration wizard.

        4. Select Yes, to restart the Tomcat service for the changes to take effect.

        You have successfully configured the CCO instance! You can now proceed to the next step:

        • If you are installing a dedicated Docker component – see Dedicated Docker Registry Installation (Optional)
        • If you are not installing a dedicated Docker component – see Setup the Admin Account and proceed with configuring and setting up CloudCenter.


    2. CCO HA                                                                                                                                                           

      •  CCO HA (CloudCenter 4.6)
        1.  CCO_PRIMARY – Run Core and Appliance Installers

          CCO_PRIMARY – Run Core and Appliance Installers

          1. Download package files:

            Icon

            See Installation Overview to understand the required components and the installation options.

            See Installer Overview to understand the types of files.

            1. SSH into the VM instance designated for this component by using the key pair that you used to launch the VM.
            2. Download the following required files for this component from software.cisco.com to the /tmp folder on that VM:

              • core_installer.bin
              • cco-installer.jar
              • cco-response.xml
          2. Run the core installer to setup core system components using the following commands:

            For example:

            Syntax:

            <ostype>= centos6, centos7, rhel6, rhel7

            <cloudtype>= amazon, azure, azurerm, azurepack, google, opsource, openstack, softlayer, vmware, or vcd (run the ./core_installer.bin help command for a complete list)

          3. Remove the core_installer.bin file.

          4. Log off and log back in as the root user to ensure JAVA Home is set.

          5. Change to the /tmp directory.


          6. Run the appliance installer to setup the CCO. 

          7. Reboot the CCO VM.

        2.  CCO_PRIMARY – Configure CCO Properties

          CCO_PRIMARY – Configure CCO Properties

          Icon

          You can configure the information for all three CCO servers when you invoke the CCO_PRIMARY wizard.

            1. SSH into the CCO instance as a centos user.
            2. Run the following command:

          1. Invoke the CCO wizard.

            CCO Wizard Path
          2. Configure the server properties.

            Write this down for future reference!

            Icon
            Write down the Field details in a printed version of the Your Notes section for later use.
            GroupNotes

            AgentBundle

            Use the defaults.

            • If you are using the custom bundle, replace cdn.cliqr.com with the custom bundle store IP or DNS
            • If you are using the package store, replace repo.cliqrtech.com with the custom package store IP or DNS

            AMQP_Server

            • AMQP Server IP: AMQP_IP or AMQP_LB_IP
            • AMQP Port: 5671
            NetworkHostname: Configure the Network details for your CCO environment. This is an optional step to configure the Private IP of the VM. You can generally configure this information if the VM does not have preset IP or hostname or if you need to override an existing IP or Hostname.

            Guacamole

             

            • Connection Broker Host: IP address of the both Primary and Secondary AMQP VMs separated by commas
            • Connection Broker Port1: 7788
            • Connection Broker Port2: 7789

            Docker

            • Docker Registry URL: Set only if custom docker registry is used
            • Docker CACert URL: Set only if docker registry uses SSL with custom CA Certificates

            Configure_HA (CloudCenter 4.6.x)

             

            Icon

            This configuration is only applicable for CloudCenter 4.6.x


            Hazelcast IP List: Comma separated list of CCO_PRIMARY_IP and CCO_SECONDARY_IP

            Configure_HA (CloudCenter 4.7.x)

            CCO HA Info: Specify the following details in the primary CCO server.

            Icon

            This configuration is only applicable for CloudCenter 4.7.x

            • Primary Node IP: Enter the IP address of the Primary CCO instance.
            • Secondary Node IP: Enter the IP address of the Secondary CCO instance.
            • Tertiary Node IP: Enter the IP address of the Tertiary CCO instance.

            ELK_Info

            (Effective CloudCenter 4.7.0)

            • ELK Host: Specify the IP address for the ELK/Monitor host.
            • Elasticsearch Port: The Elasticearch Port displays 8881 by default.
            • Logstash Port: The Logstash Port displays 4560 by default.
            • Host Identifier: The Host Identifier is a Unique ID for the server – be sure to prefix the unique identifier with CCO_ for example, CCO_Openstack_regionOne or CCO_Amazon_east.
            • Host Identifier List: The Host Identifier List field only applies to environments using the HA mode – provide a list of comma separated unique host Identifiers for all ELK/Monitor hosts in a HA setup = for example, CCO1,CCO2,myCCO.

              Icon

              In an environment operating in HA mode, if you have three CCO instances with unique IDs configured as CCO_1,CCO_2,CCO_3 in their respective server.properties file, then this property should state CCO_1,CCO_2,CCO_3 in each CCO instances. Each CCO must be aware of the unique ID of the other CCO(s) when in HA mode.

          3. Verify your changes and Exit the CCO configuration wizard.

          You have successfully configured the CCO! You can now proceed to the next step.

           

          Back to Phase 4: Install Components

        3.  CCO_SECONDARY – Run Core and Appliance Installers

          CCO_SECONDARY – Run Core and Appliance Installers

          1. Download package files:

            Icon

            See Installation Overview to understand the required components and the installation options.

            See Installer Overview to understand the types of files.

            1. SSH into the VM instance designated for this component by using the key pair that you used to launch the VM.
            2. Download the following required files for this component from software.cisco.com to the /tmp folder on that VM:

              • core_installer.bin
              • cco-installer.jar
              • cco-response.xml
          2. Run the core installer to setup core system components using the following commands:

            For example:

            Syntax:

            <ostype>= centos6, centos7, rhel6, rhel7

            <cloudtype>= amazon, azure, azurerm, azurepack, google, opsource, openstack, softlayer, vmware, or vcd (run the ./core_installer.bin help command for a complete list)

          3. Remove the core_installer.bin file.

          4. Log off and log back in as the root user to ensure JAVA Home is set.

          5. Change to the /tmp directory.


          6. Run the appliance installer to setup the CCO. 

          7. Reboot the CCO VM.

        4.  CCO_SECONDARY – Configure CCO Properties

          CCO_SECONDARY – Configure CCO Properties

            1. SSH into the CCO instance as a centos user.
            2. Run the following command:

          1. Invoke the CCO wizard.

            CCO Wizard Path
          2. Configure the server properties.

            Write this down for future reference!

            Icon
            Write down the Field details in a printed version of the Your Notes section for later use.
            GroupNotes

            AgentBundle

            Use the defaults.

            • If you are using the custom bundle, replace cdn.cliqr.com with the custom bundle store IP or DNS
            • If you are using the package store, replace repo.cliqrtech.com with the custom package store IP or DNS

            AMQP_Server

            • AMQP Server IP: AMQP_IP or AMQP_LB_IP
            • AMQP Port: 5671
            NetworkHostname: Configure the Network details for your CCO environment. This is an optional step to configure the Private IP of the VM. You can generally configure this information if the VM does not have preset IP or hostname or if you need to override an existing IP or Hostname.

            Guacamole

             

            • Connection Broker Host: AMQP_IP or AMQP_LB_IP
            • Connection Broker Port1: 7788
            • Connection Broker Port2: 7789

            Docker

            • Docker Registry URL: Set only if custom docker registry is used
            • Docker CACert URL: Set only if docker registry uses SSL with custom CA Certificates

            Configure_HA

             

            Hazelcast IP List:Comma separated list of CCO_PRIMARY_IP and CCO_SECONDARY_IP
          3. Verify your changes and Exit the CCO configuration wizard.

          You have successfully configured the CCO! You can now proceed to the next step.

        5.  CCO_LB

          CCO_LB

          Load balancing can be done through HAProxy, NGiNX, Apache2, or a cloud that is natively available to services, like AWS Elastic Load Balancer (ELB). To configure the load balancer service and ensure CCO load balancing, be sure to listen on port 8443 and balance the request at 8443 on both the CCO_PRIMARY and CCO_SECONDARY servers.

          Icon

          See  CCO_LB Ports for the complete list of ports that need to be open for your deployment.

          The following load balancing configuration was performed on CentOS7.x VM with HAProxy for the CCO VM.

          1. SSH into the VM instance using the key pair that you used to launch the CCO VM.
          2. Install HAProxy as the root user.

          3. Modify HAProxy config file as follows.

          4. Start the HAProxy service and check the status to ensure that it is active

             

           

          Back to Phase 4: Install Components

      •  CCO HA (CloudCenter 4.7)
        1.  CCO HA – Run Core Installer and Setup SSH Communication

          CCO HA – Run Core Installer and Setup SSH Communication

          To run the core installer and setup SSH communication for CCO_PRIMARY, CCO_SECONDARY, and CCO_TERTIARY, follow this procedure.

          1. Download package files:

            Icon

            See Installation Overview to understand the required components and the installation options.

            See Installer Overview to understand the types of files.

            1. SSH into the VM instance designated for this component by using the key pair that you used to launch the VM.
            2. Download the following required files for this component from software.cisco.com to the /tmp folder on that VM:

              • core_installer.bin
              • cco-installer.jar
              • cco-response.xml
          2. Run the core installer to setup core system components using the following commands:

            For example:

            Syntax:

            <ostype>= centos6, centos7, rhel6, rhel7

            <cloudtype>= amazon, openstack, vmware (run the ./core_installer.bin help command for a complete list)

          3. Remove the core_installer.bin file.

          4. Perform Steps 1 to 4 (Steps a to d) on the CCO_SECONDARY instance.
          5. Perform Steps 1 to 4 (Steps a to d) on the CCO_TERTIARY instance.
          6. Exchange the SSH keys between the CCO_PRIMARY, CCO_SECONDARY, and CCO_TERTIARY instances.

            Icon

            You do not need to repeat Step 7 for the CCO_SECONDARY and CCO_TERTIARY instances as the same SSH key is used for all three instances.

             

            1. On the CCO_PRIMARY instance, execute the following to generate a new SSH key. 

            2. Copy the id_rsa files (~/.ssh/id_rsa and ~/.ssh/id_rsa.pub) from CCO_PRIMARY to the same location on CCO_SECONDARY and CCO_TERTIARY. On CCO_SECONDARY and CCO_TERTIARY, if the .ssh directory does not exist, create it using the following commands before copying the files.

            3. On the CCO_SECONDARY and CCO_TERTIARY, execute the following to add a new SSH key.

            4. Verify mutual SSH access between the CCO_PRIMARY, CCO_SECONDARY, and CCO_TERTIARY by running the following command on each VM.

              You have now set up SSH on all three CCO instances.

          7. Run the appliance installer to setup the CCO on the CCO_PRIMARY, CCO_SECONDARY, and CCO_TERTIARY by running the following command on each VM.

             

          8. Reboot the CCO_PRIMARY, CCO_SECONDARY, and CCO_TERTIARY VMs.

           

        2.  CCO_PRIMARY – Configure CCO Properties

          CCO_PRIMARY – Configure CCO Properties

          Icon

          You can configure the information for all three CCO servers when you invoke the CCO_PRIMARY wizard.

            1. SSH into the CCO instance as a centos user.
            2. Run the following command:

          1. Invoke the CCO wizard.

            CCO Wizard Path
          2. Configure the server properties.

            Write this down for future reference!

            Icon
            Write down the Field details in a printed version of the Your Notes section for later use.
            GroupNotes

            AgentBundle

            Use the defaults.

            • If you are using the custom bundle, replace cdn.cliqr.com with the custom bundle store IP or DNS
            • If you are using the package store, replace repo.cliqrtech.com with the custom package store IP or DNS

            AMQP_Server

            • AMQP Server IP: AMQP_IP or AMQP_LB_IP
            • AMQP Port: 5671
            NetworkHostname: Configure the Network details for your CCO environment. This is an optional step to configure the Private IP of the VM. You can generally configure this information if the VM does not have preset IP or hostname or if you need to override an existing IP or Hostname.

            Guacamole

             

            • Connection Broker Host: IP address of the both Primary and Secondary AMQP VMs separated by commas
            • Connection Broker Port1: 7788
            • Connection Broker Port2: 7789

            Docker

            • Docker Registry URL: Set only if custom docker registry is used
            • Docker CACert URL: Set only if docker registry uses SSL with custom CA Certificates

            Configure_HA (CloudCenter 4.6.x)

             

            Icon

            This configuration is only applicable for CloudCenter 4.6.x


            Hazelcast IP List: Comma separated list of CCO_PRIMARY_IP and CCO_SECONDARY_IP

            Configure_HA (CloudCenter 4.7.x)

            CCO HA Info: Specify the following details in the primary CCO server.

            Icon

            This configuration is only applicable for CloudCenter 4.7.x

            • Primary Node IP: Enter the IP address of the Primary CCO instance.
            • Secondary Node IP: Enter the IP address of the Secondary CCO instance.
            • Tertiary Node IP: Enter the IP address of the Tertiary CCO instance.

            ELK_Info

            (Effective CloudCenter 4.7.0)

            • ELK Host: Specify the IP address for the ELK/Monitor host.
            • Elasticsearch Port: The Elasticearch Port displays 8881 by default.
            • Logstash Port: The Logstash Port displays 4560 by default.
            • Host Identifier: The Host Identifier is a Unique ID for the server – be sure to prefix the unique identifier with CCO_ for example, CCO_Openstack_regionOne or CCO_Amazon_east.
            • Host Identifier List: The Host Identifier List field only applies to environments using the HA mode – provide a list of comma separated unique host Identifiers for all ELK/Monitor hosts in a HA setup = for example, CCO1,CCO2,myCCO.

              Icon

              In an environment operating in HA mode, if you have three CCO instances with unique IDs configured as CCO_1,CCO_2,CCO_3 in their respective server.properties file, then this property should state CCO_1,CCO_2,CCO_3 in each CCO instances. Each CCO must be aware of the unique ID of the other CCO(s) when in HA mode.

          3. Verify your changes and Exit the CCO configuration wizard.

          You have successfully configured the CCO! You can now proceed to the next step.

           

          Back to Phase 4: Install Components

        3.  CCO_LB

          CCO_LB

          Load balancing can be done through HAProxy, NGiNX, Apache2, or a cloud that is natively available to services, like AWS Elastic Load Balancer (ELB). To configure the load balancer service and ensure CCO load balancing, be sure to listen on port 8443 and balance the request at 8443 on both the CCO_PRIMARY and CCO_SECONDARY servers.

          Icon

          See  CCO_LB Ports for the complete list of ports that need to be open for your deployment.

          The following load balancing configuration was performed on CentOS7.x VM with HAProxy for the CCO VM.

          1. SSH into the VM instance using the key pair that you used to launch the CCO VM.
          2. Install HAProxy as the root user.

          3. Modify HAProxy config file as follows.

          4. Start the HAProxy service and check the status to ensure that it is active

             

           

          Back to Phase 4: Install Components

         

         


     

Back to Phase 4: Install Components

Dedicated Docker Registry Installation (Optional)

If your worker image has the Docker engine installed (by default, CentOS 7 images), the following out-of-box (OOB) CloudCenter services will be run as containers inside the Application VM (worker):

Docker Registry – Run Core and Appliance Installer

To configure a Docker Registry, follow this procedure.

  1. Download package files:

    Icon

    See Installation Overview to understand the required components and the installation options.

    See Installer Overview to understand the types of files.

    1. SSH into the VM instance designated for this component by using the key pair that you used to launch the VM.
    2. Download the following required files for this component from software.cisco.com to the /tmp folder on that VM:

      • repo_installer.bin  

  2. Run the core installer to setup core system components using the following commands:

    For example:

    Syntax:

    <ostype>= centos7, rhel7

    <cloudtype>= amazon, azure, azurerm, azurepack, google, opsource, openstack, softlayer, vmware, or vcd
    (run the ./core_installer.bin help command for a complete list)

  3. Remove the core_installer.bin file.

  4. Reboot the Docker VM.

You have successfully configured the Docker Registry! You can now proceed to the next step.

 

 

Custom Image Installation                                                           

  •  Verify the Compatibility of the Java Version for the Management Agent

    Management Agent Java Version Compatibility

    Overview

    Each VM that is managed by CloudCenter requires a Management Agent Bundle (agent) component to run on it. The CloudCenter platform installer files includes the management agent in each VM image. The CloudCenter platform detects that the agent is not installed and automatically pushes the agent to each VM as part of the deployment process.

    The CCO receives monitoring information from the management agent and in turn provides instructions to the agent for the following tasks:

    • Complete application deployment tasks
    • Perform provisioning tasks (for example running configuration scripts)
    • Run custom cleanup scripts (for example to de-provision or shutdown applications)
    • Enforce policies (for example, to reconfigure middle ware service during auto-scaling)
    • Collect system metrics based on policy requirements
    • Monitor data, provide status updates, and keep alive system heartbeats.

    Java Version

    CloudCenter VersionJava Version
    CloudCenter 4.0.0Java 1.7 Update 75
    CloudCenter 4.5.3Java 1.7 Update 80
    CloudCenter 4.6.0Java 1.8 Update 102
    CloudCenter 4.7.0Java 1.8 Update 102

  •  Install a Custom Linux Image

    Installing CloudCenter Tools on a Custom Linux Image

    Overview

    Use the CloudCenter installer binary (LINUX_WORKER_OS_VERSION) to create CloudCenter-enabled images on different clouds and regions.

    Icon

    When you modify a pre-built image (for example, when performing an OS update, installing a new tool, upgrading the Management Agent, and so forth), be aware that the pre-built image already has CloudCenter Tools installed.

    When updating an image that already has CloudCenter Tools installed, you must delete this file (/usr/local/osmosix/etc/hostid) prior to taking the final snapshot.

    Icon

    Use this procedure to also install CloudCenter Tools on CentOS 7 and RHEL-7.

    Icon

    When installing the Management Agent on Linux machines, you will need to provide information on the OS and platform being used.

     VMware VMs

    To use VMware VMs, you should have already installed VMware tools on the Linux machine.

    Installation Process

    To install CloudCenter tools (see Key Components) on a Linux image, follow this procedure:

    1. Contact CloudCenter Support to obtain the installer binary and the path. Download the installer package (worker_installer.bin) to the CCM VM’s /tmp folder.
    2. SSH into the application VM instance using the key pair that you used to launch the VM.
    3. Run the following commands to install CloudCenter Tools:

    4. Download the installer package to the application VM’s /tmp folder.
    5. Change permissions and use the application VM (worker) installer file to install CloudCenter Tools:

       Syntax

      ostype = rhel6, rhel7, oel6, centos6, centos7, ubuntu10, ubuntu1204, ubuntu1404, and amazon (see the section below to identify your OS type)

      cloudtype = amazon, azure, azurepack, azurerm, google, opsource, openstack, softlayer, vmware, and vcd

       Skip Module Installation?
      The following modules are installed as part of the installation process for Base OS images.
      Module KeywordDescriptionRequired?
      sysupdateBasic RPM filesYes
      worker
      Icon

      The VNC and Interactive modules are not installed by default. If you require VNC access in the Application VM instance, set the following environment variable before running worker_installer.bin:

      export gui_enable=true
      Yes
      vncVirtual Network Computing (VNC) binaries for VNC accessOptional
      interactiveInteractive VNC-related binaries for VNC accessOptional
      dockerOptional

      You can skip the module installation process by running the following command before (re)running the installer:

      For example: To skip the Docker module, run the following command:

      Icon

      The installer tracks installation process and the modules installed during this process. If the installation fails while a particular module is being installed, you can rerun the installer after skipping the failed module(s) or after resolving any issues that cause a failure.


    6. Clean up and exit the VM instance:

    Cloud Nuances

    • Azure

       Azure Installation Nuances
      1. Install CliQr Tools on the application VM.
      2. Run the following command after the installation is completed
        waagent -deprovision+user
      3. Stop the VM.
      4. Capture the image.
    • vCD

       vCD Installation Nuances
      1. Install CliQr Tools on the application VM.
      2. Stop the VM.
      3. Edit the settings for this VM and be sure to remove the NIC(s).
      4. Save the VM as a template into the vCD catalog of your choice.

    Identifying the OS Type

    To verify or identify the OS type, follow this procedure:

    1. In your terminal, issue one of the following commands (based on your Linux implementation):
      1. $ cat /etc/issue
        Ubuntu 14.04.2 LTS \n \l

        or

      2. $ cat /etc/*-release
        CentOS release 6.3 (Final)
    2. Based on the response to one of these commands, you can identify if your OS type.

    Successful Installation

    After you run the installer commands, the installation results are displayed on the screen as follows:

    • Successful scenarios: Identifies a list of successfully installed components in green text.
    • Failure scenarios: Provides a path to the log file that provides details of each failure.

     

  •  Install a Custom Windows Image

    Installing CloudCenter Tools on a Windows Image

    Icon

    This procedure may differ based on your cloud and your Windows version. This procedure provides a point of reference to install the WINDOWS_WORKER_OS_VERSION image.

    Installation Process

    To install CloudCenter Tools on a Windows image, follow this procedure:

    1. Contact CloudCenter Support to obtain the installer package (cliqr_installer.exe).

    2. Launch a base Windows image from the Cloud Provider Console. The following image is an example for OpenStack.

    3. Configure and save the User Account Control Level to Never Notify.
    4. CloudCenter requires Powershell 4.0. Verify that you are running this version of Powershell:
      PS C:\> $PSVersionTable.PSVersion

      Major Minor Build Revision 
      -----
       ----- ----- -------- 
      4
        0  -1  -1
    5. In the Powershell command line window, issue the command to bypass the Powershell ExecutionPolicy.

      Set-ExecutionPolicy -ExecutionPolicy Bypass
       
    6. Verify that the C:\PROGRA~1 path is resolvable to C:\Program Files.
      dir "C:\PROGRA~1"

      Otherwise, you must create the corresponding link:
      mklink /J "C:\PROGRA~1" "C:\Program Files"

    7. Download CloudCenter Tools as directed by CloudCenter Support.

    8. Go to the command prompt window and run the downloaded file:
      C:\Downloads cliqr_installer.exe /CLOUDTYPE= openstack (or other cloud)/CLOUDREGION=default
      (The other cloud options are: amazon, azure, azurepack, google, openstack, opsource, softlayer, vcd, vmware, cisco)
    9. Run the Installer. You may add the IIS installation (depends on your deployment).

       Additional steps if using a Windows Azure Image
      • The following extra steps are required if configuring a Windows 2012 R2 application VM image in Azure.

         Windows 2012 R2 worker image in Azure
        1. Open Server Manager and start/open the Add Roles and Features Wizard.

        2. Click Next at the Before you begin pane.

        3. Select Role-based or feature-based installation on the Installation type pane and click Next .

        4. Select the Select a server from the server pool option in the Server Selection pane.

        5. In the Server Roles pane, select Web Server (IIS), and add all roles under Application Development.

        6. Click Next to proceed to the Features pane.

        7. In the Internet Information Services pane, expand Web Management Tools, and select IIS Management Console.

        8. Select Add Features and select:
          1. .NET Framework 3.5 Features, add .NET Framework 3.5
          2. .NET Framework 4.5 Features, add ASP.NET 4.5
      • Remove the installer.exe file.
      • Go to Control Panel > System and Security > System > Allow Remote Access. Uncheck the check box to Allow connections only from computers running Remote Desktop with Network Level Authentication. This action allows you to RDP into the VM from the CloudCenter UI.
      • In the file explorer go to C:\Windows\System32\Sysprep. Double click on sysprep. Make sure you choose the options displayed in the image below. Once sysprep is done, your RDP session will terminate

         

      • Go to the Azure Management UI and shutdown the application VM image.

    10. Create a snapshot of the image from your cloud console.
    11. After creating the snapshot, include the Image ID in the CloudCenter logical image (CCM UI > Admin > Images > Manage Cloud Mapping > Edit Mapping). See Cloud Mapping for Images for additional context).

      You have now mapped your Windows image to the cloud.

    Cloud Nuance

    vCD

     vCD Installation Nuances
    1. Install CliQr Tools on the application VM.
    2. Stop the VM.
    3. Edit the settings for this VM and be sure to remove the NIC(s).
    4. Save the VM as a template into the vCD catalog of your choice.

    Post-Installation Verification

    After installing the agent, verify the following information:

    • If the CliQr Startup Services are set to Automatic:

    • If the Jetty Service is up and running:

    If this information remains unverified, be aware that the agent may not be successfully installed.

     

     

  •  Customize Docker Image (External Scripts Executor)

    Customize Docker Image

    Overview

    1. Login to server where you have installed the External Script Executor.

    2. Create a new folder in any location within this server and navigate to that folder.

    3. Create a file within this folder and name it Dockerfile.

    4. Add the following content to this file:

    5. Save this file and run the following commands:

 

 

 

 

  • No labels