CliQr is now part of Cisco Learn More About Cisco

Upgrade CCO in Non-HA Mode

Overview

Icon

Be sure to review Upgrade Overview before starting this procedure!

This section provides details on upgrading your CloudCenter deployment in Non-HA mode. 

Icon

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.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 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 Virtual Appliance Overview to understand the required components.

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.

    Icon

    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:

    • cco-installer.jar 
    • cco-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 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.

     Syntax
    <ostype> = centos6, centos7, rhel6, rhel7
    <cloudtype
    > = amazon, azureclassic, 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.

     Syntax
    <ostype> = centos6, centos7, rhel6, rhel7
    <cloudtype
    > = amazon, azureclassic, 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, azureclassic, 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.

      Configure CCO Wizard Properties

      Icon

      This component is required for each cloud region (public cloud, private cloud, or datacenter).

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

      • Invoke the CCO wizard.

        CCO Wizard Path

         

        Configure the server 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.
        Wizard MenuFieldNotes

        Agent Bundle Parameters

        Linux Bundle URLThe Linux URL for the Management Agent bundle – Use the default or replace cdn.cliqr.com with the custom bundle store IP or DNS.
        Windows Bundle URLThe Windows URL for the Management Agent bundle –  Use the default or replace cdn.cliqr.com with the custom bundle store IP or DNS.
        Bootstrap js URL

        Required for Dynamic Bootstrapping information – Use the default or replace cdn.cliqr.com with the local repository IP or DNS.

        This field refers to three package store URLs:

        • The CloudCenter installer package: http://${s3Bucket}/${imageBootstrapperPath}/bundle/cliqrInstaller.zip

        • The core installer package: http://${s3Bucket}/${imageBootstrapperPath}/bundle/corePkg.tar.gz

        • The JSON package: http://${s3Bucket}/${imageBootstrapperPath}/bundle/simplejson.tar.gz

        Bootstrap py URLRequired for Dynamic Bootstrapping information called by Linux files– Use the default or replace cdn.cliqr.com with the custom bundle store IP or DNS.
        Bootstrap Linux URLRequired for Dynamic Bootstrapping information for Linux files– Use the default or replace cdn.cliqr.com with the custom bundle store IP or DNS.
        Bootstrap win URLRequired for Dynamic Bootstrapping information for Windows files– Use the default or replace cdn.cliqr.com with the custom bundle store IP or DNS.
        Linux Upgrade URLThe Linux URL for the Management Agent upgrade scripts – Use the default or replace cdn.cliqr.com with the custom bundle store IP or DNS.
        Windows Upgrade URLThe Windows URL for the Management Agent upgrade scripts  – Use the default or replace cdn.cliqr.com with the custom bundle store IP or DNS.
        Node Metadata URLThe Metadata (.jar file) URL for the Management Agent VM – Use the default or replace cdn.cliqr.com with the custom bundle store IP or DNS.
        Custom Repo URLThe CloudCenter custom artifacts repository URL – Use the default or replace repo.cliqrtech.com with the custom package store IP or DNS.
        Service URL

        The URL that points to the out-of-box services – Use the default or replace cdn.cliqr.com with the custom bundle store IP or DNS.

        Action URLThis URL should point to a VM location where you can download scripts (the HTTP URL must be accessible from this VM) when you perform a Service Lifecycle Action or a VM Action.
        AgentLite Linux URLThe location where the Linux-based agent-lite-linux-bundle.tar.gz resides. This URL is required to Install AgentLite on a Linux VM (see VM Management > Install Agent Manually for additional context).
        AgentLite Windows URLThe location where the Windows-based agent-lite-windows-bundle.zip resides. This URL is required to Install AgentLite on a Windows VM (see VM Management > Install Agent Manually for additional context).
        External Service URLThe path/URL to the external service bundle – Use the default or replace cdn.cliqr.com with the custom bundle store IP or DNS.

        AMQP_Server

        AMQP Server IP

        AMQP_IP or AMQP_LB_IP

        AMQP Port5671
        NetworkHostnameConfigure 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 Hos

        AMQP_IP or AMQP_LB_IP 

        Connection Broker Port7788
        Connection Broker Port27789

        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.

        See Certificate Authentication > Dedicated Components for additional context.

        ELK_Info

        ELK HostSpecify the IP address for the ELK/Monitor host.
        Elasticsearch PortDisplays 8881 by default.
        Logstash PortDisplays 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.

        External_Script_ExecutorDocker Server IPThe default IP is 127.0.0.1.
        Enter the IP address of a dedicated Docker server, if applicable.
        Docker Server PortDefaults to 2376
        Config_CertsCerts Zip PathProvide the path for the certs.zip file. The default path is /tmp/certs.zip.
      1. Verify your changes and Exit the CCO configuration wizard.

      2. 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 configuring CCO HA – see CCO_LB to complete the HA configuration.
      • If you are installing a dedicated Docker component – see Dedicated Docker Registry Installation (Optional).
      • If you are not installing a dedicated Docker component – see Configure the Admin Account and proceed with configuring and setting up CloudCenter.

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

 

  • No labels