CliQr is now part of Cisco Learn More About Cisco

Upgrade to CloudCenter in HA Mode              

Icon

Use this procedure to upgrade to:

  • CloudCenter 4.6.x from any lower 4.6.x or 4.5.x version.
  • CloudCenter 4.7.x from any 4.6.x version. CloudCenter installations of pre-4.6 releases cannot be directly upgraded to 4.7.x You must first upgrade to CloudCenter 4.6.x before upgrading to 4.7.x.

  • CloudCenter 4.7.x release from any lower 4.7.x version.

The core_upgrader.bin File

The core_upgrade.bin file has a different purpose depending on the following factors:

  • What is your current and target release?
  • On which component will you run this file? For example,  running the 4.6.2 version of this file on the CCO automatically installs the Docker enhancement.
  • From which release did you obtain this file? Be sure to use the file provided for the applicable release.

Your environment, your combination of releases and components, and when you obtained this file determine if and when to use this file.

Icon

While the upgrade procedure provided in this section includes instructions to run the core_upgrader.bin file, be aware that this file is ONLY required for specific versions and is specific to each component as identified in the following table.

FromToIs core_upgrader.bin Required?
4.7.04.7.1Not required
4.6.x4.7.1Required for all components
4.7.0Required for all components
4.6.1.x4.6.2

Required for the following components:

  • Docker External Scripts Executor (standalone)
  • Docker External Scripts Executor (co-located)
4.6.04.6.2

Required for the following components:

  • Docker External Scripts Executor (standalone)
  • Docker External Scripts Executor (co-located)
4.6.04.6.1.xNot required
4.5.x4.7.0Not possible. You must upgrade to 4.6 before upgrading to 4.7.
4.6.2

Required for all components

4.6.1Required for all components
4.6.0Required for all components

The HA Upgrade Procedure

  1.  CCM-DB Upgrade in HA Mode

    Upgrade CCM and Database in HA Mode

    Overview

    This section provides details on upgrading your CloudCenter 4.5.x deployment to CloudCenter 4.6.x in HA mode. 

    In HA Mode, the PostgreSQL DB should be setup on two standalone servers in a master-slave replication mode.

    Icon

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

    Icon

    Component Accountability

    See the following sections to upgrade instances in HA mode:

    1. Database and CCM: This page.
    2. CCO: See CCO Upgrade in HA Mode.
    3. AMQP: Does not need to be upgraded as part of the HA upgrade process.

    4. Guacamole: Be aware that Guacamole is a separate component. Currently, the CloudCenter platform does not support HA for Guacamole.

    Prerequisites

    Icon

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

    Verify these requirements before you begin the upgrade process:

    • See HA Best Practices for HA considerations.

    • For each CCM (CCM primary and CCM secondary) and each PostgreSQL (DB master and DB slave) instance that must be upgraded, verify the following prerequisites:

      • 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

    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 the Upgrade Packages

    Download the following files from software.cisco.com to the /tmp folder. See Installation Overview > Installation Download Details for additional context.

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

    Select Your Upgrade Scenario

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

    Scenario
    Existing Scenario
    Upgrade Scenario
    Follow the Process in this Section

    Scenario 1

    Icon

    Use if upgrading from CloudCenter 4.5.x to 4.6.x


     

    • Instance 1 = CCM primary
    • Instance 2 = CCM secondary
    • Instance 3 = MySQL
    • Instance 4 = MySQL
    • Instance 1 = CCM primary
    • Instance 2 = CCM secondary
    • Instance 3 = PostgreSQL master
    • Instance 4 = PostgreSQL slave
    Double CCM and Double PostgreSQL – A

    Scenario 2

    Icon

    Use if upgrading from CloudCenter 4.6.0 to a later version

    • Instance 1 = CCM primary
    • Instance 2 = CCM secondary
    • Instance 3 = PostgreSQL
    • Instance 4 = PostgreSQL
    • Instance 1 = CCM primary
    • Instance 2 = CCM secondary
    • Instance 3 = PostgreSQL master
    • Instance 4 = PostgreSQL slave
    Double CCM and Double PostgreSQL B
    Scenario 3
    • Instance 1 = CCM primary  
    • Instance 2 = CCM secondary   
    • MySql  in either or both CCM instances
    • Instance 1 = CCM primary  
    • Instance 2 = CCM secondary
    • Instance 3 = PostgreSQL master  
    • Instance 4 = PostgreSQL slave
    MySql in Either or Both CCM Instances
    Scenario 4
    • Instance 1 = CCM  
    • Instance 2 = MySQL  
    • Instance 3 = MySQL
    • Instance 1 = CCM  
    • Instance 2 = PostgreSQL master  
    • Instance 3 = PostgreSQL slave
    Single CCM and Double PostgreSQL
    Scenario 5
    • Instance 1 = CCM primary
    • Instance 2 = CCM secondary
    • Instance 3 = MySQL
    • Instance 1 = CCM primary
    • Instance 2 = CCM secondary
    • Instance 3 = PostgreSQL
    Double CCM and Single PostgreSQL

    Double CCM and Double PostgreSQL – A

     Scenario 1: Each in Separate Instances
    Icon

    Use this procedure if upgrading from CloudCenter 4.5.x to 4.6.x.

    Follow this process to upgrade the CCM-DB instances in HA mode.

    1. To upgrade both PostgreSQL database instances, follow this procedure.
      1. Install both database servers on the same cloud or datacenter.
      2. Ensure that the master and slave database servers are located on the same subnet. If the master and slave database servers are on different subnets (or VPCs) ensure that they are able to communicate with each other over private IP.

      3. Launch both instances using the master IP and slave IP.
      4. Set up SSH connectivity between the master and slave VMs. Exchange the SSH keys between the DB master and DB slave servers.

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

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

        3. On the DB slave, execute the following to generate a new SSH key.

        4. Verify mutual SSH access between the DB master and DB slave by running the following command on each VM.

      5. Create a security group with the specified ports and launch the instances using this security group.
      6. Run the following commands on each PostgreSQL instance.

         Syntax

        <ostype> = centos6, centos7, rhel6, rhel7 

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

      7. Use the following command to start the database wizard and allow the CCM to access the database. See CCM Installation (Required) for additional context.

      8. If your database upgrade was successful, be aware that you can now stop both instances of MySQL as you no longer need these instances.
    2. Upgrade the CCM primary server.

      1. Run the following commands on the CCM instance.

         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. Edit the ccm-response.xml file to include the following values:

      3. Run the following commands from your download folder.

    3. Upgrade the CCM secondary server.

      1. Run the following commands on the CCM instance.

         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. Edit the ccm-response.xml file to include the following values:

      3. Run the following commands from your download folder:

    Double CCM and Double PostgreSQL B

     Scenario 2: Each in Separate Instances
    Icon

    Use this procedure if upgrading from CloudCenter 4.6.0 to 4.6.x (once available).

    Follow this process to upgrade the CCM-DB instances in HA mode.

    1. Follow this procedure to upgrade both PostgreSQL database instances.
      1. Install both database servers on the same cloud or datacenter.
      2. Ensure that the master and slave database servers are located on the same subnet. If the master and slave database servers are on different subnets (or VPCs) ensure that they are able to communicate with each other over private IP.

      3. Launch both instances using the master IP and slave IP.
      4. Set up SSH connectivity between the master and slave VMs. Exchange the SSH keys between the DB master and DB slave servers.

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

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

        3. On the DB slave, execute the following to generate a new SSH key.

        4. Verify mutual SSH access between the DB master and DB slave by running the following command on each VM.

      5. Create a security group with the specified ports and launch the instances using this security group.
      6. Run the following commands on each PostgreSQL instance.

         Syntax

        <ostype> = centos6, centos7, rhel6, rhel7 

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

      7. Use the following command to start the database wizard and allow the CCM to access the database. See CCM Installation (Required) for additional context.

    2. Upgrade the CCM primary server.

      1. Run the following commands on the CCM instance.

         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. Edit the ccm-response.xml file to include the following values:

      3. Run the following commands from your download folder.

    3. Upgrade the CCM secondary server.

      1. Run the following commands on the CCM instance.

         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. Edit the ccm-response.xml file to include the following values:

      3. Run the following commands from your download folder:

    MySql in Either or Both CCM Instances

     Scenario 3: Each in a Separate Instance and MySQL with CCM

    Follow this process to upgrade the CCM-DB instances in HA mode.

    1. Follow this procedure to upgrade both PostgreSQL database instances.
      1. Install both database servers on the same cloud or datacenter.
      2. Ensure that the master and slave database servers are located on the same subnet. If the master and slave database servers are on different subnets (or VPCs) ensure that they are able to communicate with each other over private IP.

      3. Launch both instances using the master IP and slave IP.
      4. Set up SSH connectivity between the master and slave VMs. Exchange the SSH keys between the DB master and DB slave servers.

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

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

        3. On the DB slave, execute the following to generate a new SSH key.

        4. Verify mutual SSH access between the DB master and DB slave by running the following command on each VM.

      5. Create a security group with the specified ports and launch the instances using this security group.
      6. Run the following commands on each PostgreSQL instance.

         Syntax

        <ostype> = centos6, centos7, rhel6, rhel7 

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

      7. Use the following command to start the database wizard and allow the CCM to access the database. See CCM Installation (Required) for additional context.

    2. Upgrade the CCM primary server.

      1. Run the following commands on the CCM instance.

         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. Edit the ccm-response.xml file to include the following values:

      3. Run the following commands from your download folder.

    3. Upgrade the CCM secondary server.

      1. Run the following commands on the CCM instance.

         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. Edit the ccm-response.xml file to include the following values:

        Icon

        if you have two MySQL servers (in cased of high availability setup), the mysql_host=<mysql_ip> value displays as mysql_host=<default>. In this case, you do not need to change the default value to mysql_ip.

      3. Run the following commands from your download folder:

    Single CCM and Double PostgreSQL

     Scenario 4: DBs in Separate Instances

    Follow this process to upgrade the CCM-DB instances in HA mode.

    1. Follow this procedure to upgrade both PostgreSQL database instances.
      1. Install both database servers on the same cloud or datacenter.
      2. Ensure that the master and slave database servers are located on the same subnet. If the master and slave database servers are on different subnets (or VPCs) ensure that they are able to communicate with each other over private IP.

      3. Launch both instances using the master IP and slave IP.
      4. Set up SSH connectivity between the master and slave VMs. Exchange the SSH keys between the DB master and DB slave servers.

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

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

        3. On the DB slave, execute the following to generate a new SSH key.

        4. Verify mutual SSH access between the DB master and DB slave by running the following command on each VM.

      5. Create a security group with the specified ports and launch the instances using this security group.
      6. Run the following commands on each PostgreSQL instance.

         Syntax

        <ostype> = centos6, centos7, rhel6, rhel7 

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

      7. Use the following command to start the database wizard and allow the CCM to access the database. See CCM Installation (Required) for additional context.

    2. Upgrade the CCM server.

      1. Run the following commands on the CCM instance.

         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. Edit the ccm-response.xml file to include the following values:

      3. Run the following commands from your download folder.

      4. If your database upgrade was successful, be aware that you can now stop both instances of MySQL as you no longer need these instances.

    Double CCM and Single PostgreSQL

     Scenario 5: CCMs in Separate Instances

    Follow this process to upgrade the CCM-DB instances in HA mode.

    1. Upgrade the PostgreSQL instance.
      1. Create a security group with the specified ports and launch the instance using this security group.
      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. See CCM Installation (Required) for additional context.

      4. If your database upgrade was successful, be aware that you can now stop the MySQL instance as you no longer need it.
    2. Upgrade the CCM primary server.

      1. Run the following commands on the CCM instance.

         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. Edit the ccm-response.xml file to include the following values:

      3. Run the following commands from your download folder.

    3. Upgrade the CCM secondary server.

      1. Run the following commands on the CCM instance.

         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. Edit the ccm-response.xml file to include the following values:

      3. Run the following commands from your download folder:

    You have upgraded the CCM and PostgreSQL servers in HA mode.

     

    Verify Your Upgrade

    Ensure that the version file (/usr/local/osmosix/etc/version) reflects the new release in each VM.

    Reboot the CCM Servers

    Reboot the CCM servers.

    Start the CCM Wizard

    Use the following command to start the CCM wizard. See CCM Installation (Required) for additional context.

    REQUIRED! Pay particular attention to Step 8

    Icon

    You must configure the logo for the application profile template.

    Upgrade the CCO

    See CCO Upgrade in HA Mode  for additional context.

     

  2.  CCO Upgrade in HA Mode

     

    CCO Upgrade in HA Mode

    Overview

    This section provides details on upgrading your CloudCenter 4.5.x deployment to CloudCenter 4.6.x in HA mode.

    Icon

    The CCO HA procedure is intricate and requires deeper DevOps knowledge. First consult with your company's DevOps team and ensure that each requirement in this section is addressed.

    Icon

    Backup your database and applications before you begin this process (see Backup and Recovery in Non-HA Mode > CCO for additional context).

    Icon

    If you are upgrading a Non-HA CloudCenter deployment, see Upgrade in Non-HA Mode.

    Component Accountability

    See the following sections to upgrade instances in HA mode:

    1. Database and CCM: See CCM-DB Upgrade in HA Mode.
    2. CCO: This page.
    3. AMQP: Does not need to be upgraded as part of the HA upgrade process.

    4. Guacamole: Be aware that Guacamole is a separate component. Currently, the CloudCenter platform does not support HA for Guacamole.

    Prerequisites

    Icon

    Be aware that the CCO(s) will be offline during the upgrade process. Schedule some down time for your enterprise before starting this process.

    Verify these requirements before you begin the upgrade process:

    • For each CCO instance that must be upgraded, verify the following prerequisites:

      • See HA Best Practices for HA considerations.
      • 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.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 your database and applications before you begin this process. See Backup and Recovery in Non-HA Mode for additional context.

    Upgrading CCO from HA to HA Mode

    To upgrade HA CCOs, follow this process.

    1. Select your upgrade scenario as you would for a standalone CCO upgrade. See 2. CCO Upgrade for additional details.
    2. On all three CCO servers, configure the following procedure simultaneously. Complete every step of this procedure on all CCO servers and then move to the next step for all CCO servers.
      1. Configure CCO Spring application.

      2. Save the file.
    3. This step differs for CloudCenter 4.6 and 4.7:
      • CloudCenter 4.6:
        Start the CCO wizard, be sure to configure the Hazelcast IP List by providing a comma separated list of the CCO IP addresses in the primary CCO server. See Install Per CloudCenter Region Installation (Required)CCO HA (CloudCenter 4.6) > CCO_PRIMARY – Configure CCO Properties and CCO_SECONDARY – Configure CCO Properties for additional details.
      • CloudCenter 4.7:
        Start the CCO wizard and configure the HA information – See Install Per CloudCenter Region Installation (Required)CCO HA (CloudCenter 4.7)CCO HA – Run Core Installer and Setup SSH Communication for additional details.

    Upgrading from Non-HA to HA Mode

    If you are upgrading a non-HA CCO to a CCO HA scenario, follow this process.

    1. Perform the CCO Upgrade process in standalone mode for the Non-HA VM.
    2. Install another Standalone CCO VM.
    3. Follow the CCO HA process.

     

     

     

  • No labels