CliQr is now part of Cisco Learn More About Cisco

Upgrade CloudCenter in Non-HA Mode                                     

Icon

Be sure to review Upgrade Overview before starting this procedure!

  1.  Bundle Server Upgrade

    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.

     

     

     

  2.  CCM-Database Upgrade

    Upgrade CCM and Database in Non-HA Mode

    Overview

    This section provides details on upgrading your deployment to CloudCenter 4.6.x in Non-HA mode. In Non-HA mode, the database may be installed with the CCM or as a standalone server. To have PostgreSQL installed in a standalone VM, you must open Port 5432 to the CCM. See Networking Requirements > Standalone PostgreSQL (Optional) for additional context.

    Icon

    The database back up procedure for this upgrade are provided later in this section. Backup your database and applications before you begin this process (see the Backup Database section below).

    Icon

    If you are upgrading a HA CloudCenter deployment, see CCM-DB Upgrade in HA Mode for additional context.

    Prerequisites

    For each CloudCenter deployment that needs to be upgraded, verify the following prerequisites:

    • Review the information provided in the Upgrade Overview section and validate the following requirements for the release to which you are upgrading:

      • Is an upgrade path available?
      • Is the core_upgrade.bin file required?
    • Ensure that a version file (/usr/local/osmosix/etc/version) exists in both CCMs to be upgraded.

    • Verify that the version file contains the correct version number (for example, if your current CloudCenter release version is 4.5.5, ensure that the corresponding version value is 4.5.5).

    • See the corresponding release notes for release-specific information on the CloudCenter version to which you are upgrading. For example, the CloudCenter 4.6.0 Release Notes.

    Backup Database

    Icon

    Be aware that the CCM and DB servers will be offline during the upgrade process. Schedule some down time for your enterprise before starting this process.

    Backup your database and application (the following example uses /mnt, you can change this directory as applicable).

    Backup from 4.5.x
    Icon

    Osmosix users do not have permission to use the -R option. CloudCenter uses the GetVendorList routine. To backup this routine along with the rest of the database, you must provide the -R option using your root user credentials.

    Backup from 4.6.x

    Download Packages

    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:

      • ccm-installer.jar

      • ccm-response.xml

      • core_upgrade.bin

        Icon

        Ensure (by reviewing Upgrade Overview) that this file is required for your release upgrade path.

    Select and Execute Your Upgrade Scenario

    Your upgrade process differs depending on your instance setup. Ascertain the following considerations before you begin the CloudCenter upgrade.

    ScenarioInstance SetupRelated Section
    1
    • Instance 1 = CCM + MySQL + PostGreSQL
    All in the Same Instance
    2
    • Instance 1 = CCM + MySQL
    • Instance 2 = PostgreSQL
    Standalone CCM with Databases on Separate Instances
    3
    • Instance 1 = CCM
    • Instance 2 = MySQL + PostgreSQL
    Standalone CCM with Databases on the Same Instance
    4
    • Instance 1 = CCM
    • Instance 2 = MySQL
    • Instance 3 = PostgreSQL
    All in Separate Instances
    Scenario 1: All in the Same Instance
     All in the Same Instance
    1. Run the following commands on the CCM instance.

      Icon

      Ensure (by reviewing Upgrade Overview) that this step is required for your release upgrade path.

       Syntax

      <ostype> = centos6, centos7, rhel6, rhel7, ubuntu1204 (Ubuntu12.04 is not recommended for a new install)

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

    2. Run the following commands from your download folder.

      Be aware that no changes are required to the ccm-response.xml file.

    3. If MySQL is running on a standalone instance, you can stop the database manually at this point as the database must be operational until your migration to PostgreSQL is complete.

    Scenario 2: Standalone CCM with Databases on Separate Instances
     MySQL and PostgreSQL Databases are on Separate Instances
    1. Launch an instance for the PostgreSQL database.
    2. Run the following commands on the PostgreSQL instance.

       Syntax

      <ostype> = centos6, centos7, rhel6, rhel7 

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

    3.  Use the following command to start the database wizard and allow the CCM to access the database.

    4. Run the following commands on the CCM instance.

      Icon

      Ensure (by reviewing Upgrade Overview) that this step is required for your release upgrade path.

       Syntax

      <ostype> = centos6, centos7, rhel6, rhel7, ubuntu1204 (Ubuntu12.04 is not recommended for a new install)

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

    5. Edit the ccm-response.xml file to include the following values:

    6. Run the following commands from your download folder.

    7. If MySQL is running on a standalone instance, you can stop the database manually at this point as the database must be operational until your migration to PostgreSQL is complete.

    Scenario 3: Standalone CCM with Databases on the Same Instance
     MySQL and PostgreSQL Databases Share the Same Instance
    1. Run the following commands on the MySQL instance.

      Icon

      Ensure (by reviewing Upgrade Overview) that this step is required for your release upgrade path.

       Syntax

      <ostype> = centos6, centos7, rhel6, rhel7 

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

    2. Use the following command to start the database wizard and allow the CCM server to access the PostgreSQL database.

    3. Use the Manage Access to Postgres Database option in the wizard to allow the CCM server to access the PostgreSQL database.

    4. Run the following commands on the CCM instance.

      Icon

      Ensure (by reviewing Upgrade Overview) that this step is required for your release upgrade path.

       Syntax

      <ostype> = centos6, centos7, rhel6, rhel7, ubuntu1204 (Ubuntu12.04 is not recommended for a new install)

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

    5. Edit the ccm-response.xml file to include the following values:

    6. Run the following commands from your download folder.

    7. On the MySQL instance use the database wizard to disable the MySQL database.

    8. Use the Disable MySQL Service option in the wizard to disable the MySQL database.
    9. If MySQL is running on a standalone instance, you can stop the database manually at this point as the database must be operational until your migration to PostgreSQL is complete.
    Scenario 4: All in Separate Instances
     All in Separate Instances
    1. Run the following commands on the MySQL instance.

      Icon

      Ensure (by reviewing Upgrade Overview) that this step is required for your release upgrade path.

       Syntax

      <ostype> = centos6, centos7, rhel6, rhel7 

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

    2. Use the following command to start the database wizard and allow the CCM server to access the PostgreSQL database.

    3. Use the Manage Access to Postgres Database option in the wizard to allow the CCM server to access the PostgreSQL database.

    4. Run the following commands on the CCM instance.

      Icon

      Ensure (by reviewing Upgrade Overview) that this step is required for your release upgrade path.

       Syntax

      <ostype> = centos6, centos7, rhel6, rhel7, ubuntu1204 (Ubuntu12.04 is not recommended for a new install)

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

    5. Edit the ccm-response.xml file to include the following values:

    6. Run the following commands from your download folder.

    7. No changes are required on the MySQL instance.

    Post Upgrade Tasks

    1. Verify Your Upgrade – Ensure that the version file (/usr/local/osmosix/etc/version) reflects the new release.

    2. Reboot the CCM server.

    3.  Configure the Properties in the CCM Wizard.

      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)

    4. Upgrade the CCO VM – See 2. CCO Upgrade for additional context.

     

     

  3.  CCO Upgrade

    Upgrade CCO

    Prerequisites

    For each CloudCenter deployment that needs to be upgraded, verify the following prerequisites:

    • You should have already performed the CCM-Database Upgrade procedure.
    • Backup your database and applications before you begin this process.
    • Review the information provided in the Upgrade Overview section and validate the following requirements for the release to which you are upgrading:
      • Is an upgrade path available?
      • Is the core_upgrade.bin file required?
    • Ensure that a version file (/usr/local/osmosix/etc/version) exists in both CCOs to be upgraded.

    • Verify that the version file contains the correct version number (for example, if your current CloudCenter release version is 4.6.0, ensure that the corresponding version value is 4.6.0).

    • See the corresponding release notes for release-specific information on the CloudCenter version to which you are upgrading. For example, the CloudCenter 4.6.0 Release Notes.

    Backup Webapp Folder

    Backup the exploded war files to a backup folder (the following example uses /mnt, you can change this directory as applicable).

    Download Packages

    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:

      • cco-installer.jar 
      • cco-response.xml 
      • core_upgrade.bin

        Icon

        Ensure (by reviewing Upgrade Overview) that this file is required for your release upgrade path.


    Select and Execute Your Upgrade Scenario

    Your upgrade process differs depending on your instance setup. Ascertain the following considerations before you begin the CCO upgrade.

    ScenarioInstance SetupRelated Section
    1
    • Instance 1 = CCO + External Script Executor (Docker Container)
    (Default) CCO and the Docker container on the same Instance
    2
    • Instance 1 = CCO
    • Instance 2 = External Script Executor (Docker Container)
    CCO and the Docker container on Separate Instances
    Scenario 1: DEFAULT – CCO and the Docker Container on the Same Instance
     CCO and the Docker Container are Co-Located (DEFAULT)

    1. Run the following commands on the CCO instance.

      Icon

      Ensure (by reviewing Upgrade Overview) that this step is required for your release upgrade path.

       Syntax
      <ostype> = centos6, centos7, rhel6, rhel7
      <cloudtype
      > = amazon, azure, azurepack, google, opsource, openstack, softlayer, vmware, vcd
    2. Run the following commands from your download folder.

    Scenario 2: CCO and the Docker Container on Separate Instances
     CCO and the Docker Container are Not Co-Located
    1. Run the following commands on the CCO instance.

      Icon

      Ensure (by reviewing Upgrade Overview) that this step is required for your release upgrade path.

       Syntax
      <ostype> = centos6, centos7, rhel6, rhel7
      <cloudtype
      > = amazon, azure, azurepack, google, opsource, openstack, softlayer, vmware, vcd
    2. Run the following command from your download folder on the CCO instance.

    3. Run the following commands on the Docker Container instance.

       Syntax

      <ostype> = centos7, rhel7

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

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

    5. Reboot the CCO VM to ensure that the Docker IP is accepted by the CCO VM.

    Post Upgrade Tasks

    1. Verify Your Upgrade – Ensure that the version file (/usr/local/osmosix/etc/version) reflects the new release.

    2. Reboot the CCO server.

    3. In some cases, your deployment settings may need to be updated in the CCO server. Reassign the IP address information by running the wizard for both the CCO server.

    4. Verify the following configuration files to ensure that they reflect the right values for your deployment:

      • /usr/local/tomcat/webapps/ROOT/WEB-INF/rabbit-gateway.properties on the CCO server (verify the gatewayHost value in particular).

      • /usr/local/tomcat/webapps/ROOT/WEB-INF/gateway.properties on the CCO server (verify the rabbit.gateway.brokerHost and rabbit.gateway.cluster.addresses values in particular).

      •  Configure the Properties in the CCO Wizard.

        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.

    5. Upgrade the AMQP VM – See 3. AMQP Upgrade for additional context.

     

     

  4.  AMQP Upgrade

    AMQP Upgrade

    Prerequisites

    For each CloudCenter deployment that needs to be upgraded, verify the following prerequisites:

    • Backup your database and applications before you begin this process.

    • You should have already performed the CCM-Database Upgrade procedure.

    • You should have already performed the CCO Upgrade procedure.

    • Review the information provided in the Upgrade Overview section and validate the following requirements for the release to which you are upgrading:

      • Is an upgrade path available?
      • Is the core_upgrade.bin file required?
    • Ensure that a version file (/usr/local/osmosix/etc/version) exists in both AMQP VMs that need to be upgraded.

    • Verify that the version file contains the correct version number (for example, if your current CloudCenter release version is 4.7.0, ensure that the corresponding version value is 4.7.0).

    • See the corresponding release notes for release-specific information on the CloudCenter version to which you are upgrading. For example, the CloudCenter 4.7.0 Release Notes.

    • Do not change the AMQP server's host name, once configured. See the Post Upgrade Setup section below for implications.

     

    Backup Webapp Folder

    Backup the exploded war files to a backup folder (the following example uses /mnt, you can change this directory as applicable). This backup only applies to the Guacamole server, not the AMQP server.

    Download Packages

    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:

        • conn_broker-response.xml

        • cco-installer.jar

        • core_upgrade.bin

    Select and Execute Your Upgrade Scenario

    Your upgrade process differs depending on your instance setup. Ascertain the following considerations before you begin the CCO upgrade.

    ScenariosInstance SetupRelated Section
    1                  
                      • Instance 1 = AMQP + Guacamole      
    AMQP and Guacamole on the Same Instance
    2
                      • Instance 1 = AMQP
                      • Instance 2 = Guacamole
    AMQP and Guacamole on Separate Instances

     

    Scenario 1: AMQP and Guacamole on the Same Instance
     AMQP and Guacamole are Co-Located
    1. Login to the AMQP server and back up the data.

    2. Run the following commands on the AMQP server.

      Icon

      Ensure (by reviewing Upgrade Overview) that this step is required for your release upgrade path.

      For example: ./core_upgrade.bin centos7 amazon rabbit

      • <ostype>= centos6, centos7, rhel6, rhel7
      • <cloudtype>= amazon, azure, azurerm, azurepack, google, opsource, openstack, softlayer, vmware, and vcd
    3. Remove the core_upgrade.bin file.

    4. Change to the /tmp directory.

    5. Run the following commands from your download folder.

    Scenario 2: AMQP and Guacamole on Separate Instances
     AMQP and Guacamole are not Co-Located

    Perform the following procedure on each server – the AMQP server and the Guacamole server.

    1. Login to the AMQP server and back up the data.

    2. Run the following commands on the AMQP server.

      Icon

      Ensure (by reviewing Upgrade Overview) that this step is required for your release upgrade path.

      For example: ./core_upgrade.bin centos7 amazon rabbit

      • <ostype>= centos6, centos7, rhel6, rhel7
      • <cloudtype>= amazon, azure, azurerm, azurepack, google, opsource, openstack, softlayer, vmware, and vcd
    3. Remove the core_upgrade.bin file.

    4. Change to the /tmp directory.

    5. Run the following commands from your download folder.

    Post Upgrade Tasks

    1. Verify Your Upgrade – Ensure that the version file (/usr/local/osmosix/etc/version) reflects the new release.

    2. Reboot the AMQP server – Be aware of the following consequences if/when you reboot the AMQP server.

      Reboot AMQP VM

      Icon

      If you change the AMQP server's host name, the local AMQP database is renamed and you must reboot the AMQP VM.

      • To reboot the AMQP VM, run the following commands as root:

      • If you reboot the VM, be aware of the following details:
        • You may end up with a new host name and database name after the reboot.

        • Some clouds set the host name automatically for each new instance or reboot – RabbitMQ uses a preset host name to set the database name.

        • If a database user exists and a login is not associated, this user may not be able to log into the AMQP server.

          • Ensure that the required users (cliqr and cliqr_worker) are setup in your database. If you have additional users in your database, they will also be displayed when you run the rabbitmqctl command.

          • If you do not see these users in your database, run the following commands as root (to recreate the users in the AMQP configuration):

    3.  Configure the Properties in the GUAC Wizard.

      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.

    4. Upgrade the Monitor VM – See 4. Health Monitor Upgrade for additional context.

     

  5.  Health Monitor Upgrade

    Health Monitor Upgrade

    Prerequisites

    For each CloudCenter deployment that needs to be upgraded, verify the following prerequisites:

    • Backup your database and applications before you begin this process.

    • You should have already performed the CCM-Database Upgrade procedure.

    • You should have already performed the CCO Upgrade procedure.

    • Review the information provided in the Upgrade Overview section and validate the following requirements for the release to which you are upgrading:

      • Is an upgrade path available?
      • Is the core_upgrade.bin file required?
    • Ensure that a version file (/usr/local/osmosix/etc/version) exists in both Monitors to be upgraded.

    • Verify that the version file contains the correct version number (for example, if your current CloudCenter release version is 4.6.0, ensure that the corresponding version value is 4.6.0).

    • See the corresponding release notes for release-specific information on the CloudCenter version to which you are upgrading. For example, the CloudCenter 4.6.0 Release Notes.

    Backup Database

    Backup the exploded war files to a backup folder (the following example uses /mnt, you can change this directory as applicable)

    Download Packages

    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:

      • monitor-installer.jar
      • monitor-response.xml
      • core_upgrade.bin

        Icon

        Ensure (by reviewing Upgrade Overview) that this file is required for your release upgrade path.

    Upgrade

    1. Run the following commands:

      Icon

      Ensure (by reviewing Upgrade Overview) that this step is required for your release upgrade path.

      For example: ./core_upgrade.bin centos7 amazon monitor

      • <ostype> = centos6, centos7, rhel6, rhel7 (Ubuntu12.04 is not recommended for a new install)

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

    2. Run the following command from your download folder.

    Post Upgrade Tasks

    1. Verify Your Upgrade – Ensure that the version file (/usr/local/osmosix/etc/version) reflects the new release.

    2. Reboot the Monitor server.

    3.  Configure the Properties in the Monitor Wizard.

      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.

  6.  Docker Image Upgrade

    Docker Image Upgrade

    Overview

    A Docker image upgrade is not required with every release. If a version requires the CloudCenter-supported Docker image to be upgraded, use the procedure provided in this page. 

    When using External Services, the CloudCenter platform launches a Docker container to run the scripts. You may also need to customize this container using the applicable packages.

    The Docker image can reside in one of two places:

    • In the CCO VM (default, co-located)
    • In a Standalone Docker VM

    Versions Requiring a Docker Image Upgrade

    If you upgrade to CloudCenter 4.4.x or 4.5.x from any earlier CloudCenter version, you must upgrade the CloudCenter supported Docker image.

    CloudCenter 4.4.x and later includes the following Docker image enhancements:

    See External Service > Error Handling for additional context.

    Prerequisites

    For each CloudCenter deployment that needs to be upgraded, verify the following prerequisites:

    • Backup your database and applications before you begin this process.
    • Verify that the Docker version is ≤ Docker 1.11. Issue the following command on your Docker server: docker version
      You only need to upgrade your Docker image if your Docker image is not at Docker 1.11.

    • Review the information provided in the Upgrade Overview section and validate the following requirements for the release to which you are upgrading:

      • Is an upgrade path available?
      • Is the core_upgrade.bin file required?
    • Ensure that a version file (/usr/local/osmosix/etc/version) exists in both CCOs that need to be upgraded.

    • Verify that the version file contains the correct version number (for example, if your current CloudCenter release version is 4.5.1, ensure that the corresponding version value is 4.5.1).

    • See the corresponding release notes for release-specific information on the CloudCenter version to which you are upgrading. For example, the CloudCenter 4.6.0 Release Notes.

    Backup Database

    Backup the exploded war files to a backup folder (the following example uses /mnt, you can change this directory as applicable).

    Download Packages

    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:

      • cco-installer.jar 
      • docker.tar
      • Dockerfile

    Select and Execute Your Upgrade Scenario

    Your upgrade process differs depending on your instance setup. Ascertain the following considerations before you begin the CCO upgrade.

    ScenarioInstance SetupRelated Section
    1
    • Instance 1 = CCO + Docker
    CCO and Docker on the Same Instance
    2
    • Instance 1 = CCO
    • Instance 2 = Docker
    CCO and Docker on Separate Instances
    Scenario1: CCO and Docker on the same Instance
     CCO and Docker are Co-Located
    1. Run the following commands on the CCO-Docker Instance:

      Icon

      Ensure (by reviewing Upgrade Overview) that this step is required for your release upgrade path.

    2. Run the following commands from your download folder.

    3. Run the following commands to update the Docker image file.

     

    Scenario 2: CCO and Docker on Separate Instances
     CCO and Docker are not Co-Located
    1. Upgrade your CCO instance. See 2. CCO Upgrade for additional context.
    2. Run the following commands on the Docker Instance:

      Icon

      Ensure (by reviewing Upgrade Overview) that this step is required for your release upgrade path.

    3. Run the following commands from your download folder.

    4. Run the following commands to update the Docker image file.

    Post Upgrade Tasks

    1. Verify Your Upgrade – Verify that the Docker version is ≤ Docker 1.11. Issue the following command on your Docker server:

    2. Issue the following command and verify that the output is as follows:

     

  • No labels