// removed jquery ui css and js

Upgrade CCM and Database in Non-HA Mode

Overview

Be sure to review Upgrade Overview before starting this procedure!

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 CCM Firewall Rules for additional context.

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

If you are upgrading a HA CloudCenter deployment, see CCM and Database HA Upgrade.

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.7.2, ensure that the corresponding version value is 4.7.2).

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

Backup Database

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
NOW=$(date +"%Y%m%d")
bakdir="/mnt/bak/$NOW"
mkdir -p $bakdir
cd $bakdir

cp -r /usr/local/tomcat/webapps/* . 

mysqldump -p -u root osmosixdb > osmosixdb.sql
# At the prompt, enter the password, osmosix
tar czvf osmosixdb.tar.gz osmosixdb.sql
rm osmosixdb.sql

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
NOW=$(date +"%Y%m%d")
bakdir="/mnt/bak/$NOW"
mkdir -p $bakdir
cd $bakdir

cp -r /usr/local/tomcat/webapps/* . 

pg_dump -U cliqr -d cliqrdb > cliqrdb.sql
# At the prompt, enter the password, cliqr
tar czvf cliqrdb.tar.gz cliqrdb.sql
rm cliqrdb.sql

Download Packages

Download package files:

See Virtual Appliance Overview to understand the required components.

See Virtual Appliance Process to understand the process.

See Phase 4 Overview  to understand the various types of software download files.

  1. SSH into the VM instance designated for this component by using the key pair that you used to launch the VM.

    Along with the key pair, you may need to use your login credentials for sudo or root access based on your environment.

  2. Download the following required files for this component from software.cisco.com:

    • ccm-installer.jar

    • ccm-response.xml

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

    sudo –i
    cd /tmp
    chmod 755 core_upgrade.bin
    ./core_upgrade.bin <ostype> <cloudtype> ccm
    
    
    #After the above process completes, remove the core_upgrade.bin file
    rm core_upgrade.bin
     Syntax

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

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

  2. Run the following commands from your download folder.

    java -jar ccm-installer.jar ccm-response.xml

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

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.

    sudo –i
    cd /tmp
    chmod 755 core_upgrade.bin
    ./core_installer.bin <ostype> <cloudtype> mgmtpostgres
    
    #After the above process completes, remove the core_upgrade.bin file
    rm core_upgrade.bin
     Syntax

    <ostype> = centos6, centos7, rhel6, rhel7 

    <cloudtype> = amazon, azureclassic, 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.

    bash /usr/local/osmosix/bin/db_config_wizard.sh
  4. Run the following commands on the CCM instance.

    sudo –i
    cd /tmp
    chmod 755 core_upgrade.bin
    ./core_upgrade.bin <ostype> <cloudtype> ccm_sa
    
    #After the above process completes, remove the core_upgrade.bin file
    rm core_upgrade.bin
     Syntax

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

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

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

    db_host --- IP or hostname of newly launched PostgreSQL instance
    mysql_host --- no change
  6. Run the following commands from your download folder.

    java -jar ccm-installer.jar ccm-response.xml

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.

    sudo –i
    cd /tmp
    chmod 755 core_upgrade.bin
    ./core_upgrade.bin <ostype> <cloudtype> mgmtpostgres
    
    #After the above process completes, remove the core_upgrade.bin file
    rm core_upgrade.bin
     Syntax

    <ostype> = centos6, centos7, rhel6, rhel7 

    <cloudtype> = amazon, azureclassic, 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.

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

    sudo –i
    cd /tmp
    chmod 755 core_upgrade.bin
    ./core_upgrade.bin <ostype> <cloudtype> ccm_sa
    
    #After the above process completes, remove the core_upgrade.bin file
    rm core_upgrade.bin
     Syntax

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

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

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

    db_host --- IP or hostname of newly launched PostgreSQL instance
    mysql_ip --- IP or hostname of the MySQL instance
  6. Run the following commands from your download folder.

    java -jar ccm-installer.jar ccm-response.xml
  7. On the MySQL instance use the database wizard to disable the MySQL database.

    bash /usr/local/osmosix/bin/db_config_wizard.sh
  8. Use the Disable MySQL Service option in the wizard to disable the MySQL database.

Scenario 4: All in Separate Instances

  1. Run the following commands on the MySQL instance.

    sudo –i
    cd /tmp
    chmod 755 core_upgrade.bin
    ./core_upgrade.bin <ostype> <cloudtype> mgmtpostgres
    
    #After the above process completes, remove the core_upgrade.bin file
    rm core_upgrade.bin
     Syntax

    <ostype> = centos6, centos7, rhel6, rhel7 

    <cloudtype> = amazon, azureclassic, 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.

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

    sudo –i
    cd /tmp
    chmod 755 core_upgrade.bin
    ./core_upgrade.bin <ostype> <cloudtype> ccm_sa
    
    #After the above process completes, remove the core_upgrade.bin file
    rm core_upgrade.bin
     Syntax

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

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

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

    db_host --- IP or hostname of newly launched PostgreSQL instance
    mysql_ip --- IP or hostname of the MySQL instance
  6. Run the following commands from your download folder.

  • No labels
© 2017 Cisco Systems