// removed jquery ui css and js

Upgrade CCO in HA Mode

Overview

Be sure to review Upgrade Overview before starting this procedure!

This section provides details on upgrading your CCO in HA mode.

Prerequisites

Be aware that the CCO servers 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:

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

  • See High Availability Best Practices for HA considerations.

  • Backup your database and applications before you begin this process. See HA Mode Backup and Recovery for additional context.

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

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

  • The upgrade procedure in this section assumes the following setup:

    • The MongoDB data is retained on the CCO_PRIMARY server – this is the initiating server.

    • The MongoDB data is deleted on the CCO_SECONDARY and CCO_TERTIARY – be sure to backup and delete the CloudCenter database (called cliqr) on these two servers.

      • The assumed path for this upgrade procedure is /var/lib/mongo

      • The mongodump directory is created as a dump sub-directory in  the specified directory: /var/lib/mongo/dump

      • To locate the path for your setup, see your /etc/mongod.conf file

    • The configuration files on the CCO_TERTIARY server must reflect the corresponding values for your deployment.

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:

    • cco-installer.jar 

    • cco-response.xml 

    • core_upgrade.bin

Upgrading CCO from HA to HA Mode

To upgrade the Primary, Secondary, and Tertiary CCO instances, follow this process on each server.

  1. Select and execute the required upgrade scenario as you would for a standalone CCO upgrade – see CCO Upgrade for additional details.
    1. Run the following commands on each CCO instance.

      sudo –i
      cd /tmp
      chmod 755 core_upgrade.bin
      ./core_upgrade.bin <ostype> <cloudtype> cco
      
      
      #After the above process completes, remove the core_upgrade.bin file
      rm core_upgrade.bin
      cd /tmp
       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.

      java -jar cco-installer.jar cco-response.xml
  2. 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.

  3. Verify the following configuration files to ensure that they reflect the right values for your deployment on the CCO_TERTIARY server:

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

  4. Set up SSH communication between the CCO_PRIMARY, CCO_SECONDARY, and CCO_TERTIARY instances
    1. Run the following commands on the CCO_PRIMARY to generate a new SSH key.

      sudo -i
      ssh-keygen -t rsa
      cd ~/.ssh
      cat id_rsa.pub>>authorized_keys
    2. Create the .ssh directory (if it does not exist) on the CCO_SECONDARY and CCO_TERTIARY instances.

      sudo -i
      mkdir -p ~/.ssh
      chmod 700 ~/.ssh
    3. Copy the id_rsa files (~/ssh/id_rsa and ~/ssh/id_rsa.pub) from the CCO_PRIMARY to the same location on the CCO_SECONDARY and CCO_TERTIARY instances.

      sudo -i
      chmod 700 ~/.ssh/id_rsa*
      cat id_rsa.pub>>authorized_keys
    4. Verify mutual SSH access between all three CCO instances by running the following commands on each CCO VM.

      sudo -i
      ssh root@<CCO_PRIMARY or CCO_SECONDARY or CCO_TERTIARY>

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

     
  5. Start the wizard in the primary server and configure the HA properties for all three CCO servers.

    • Required for all deployments

       CCO PRIMARY – Configure HA Properties

      CCO_PRIMARY – Configure CCO Properties

      You can configure the information for all three CCO servers by providing the following details ONLY in the CCO_PRIMARY wizard.

      To ensure that all three CCOs communicate with each other, you must configure the following HA-specific information in the CCO_PRIMARY wizard.

      Wizard MenuFieldNotes

      Configure_HA
      CCO HA Info – Specify the following details in the primary CCO server.

      Primary Node IP

      Enter the IP address of the Primary CCO instance.

      Secondary Node IPEnter the IP address of the Secondary CCO instance.
      Tertiary Node IPEnter the IP address of the Tertiary CCO instance

      In addition to the HA_specific information mentioned above, you must also configure the generic information in the CCO_PRIMARY wizard.

      Configure CCO Wizard Properties

      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:

          sudo -i
      • Invoke the CCO wizard.

        CCO Wizard Path
        /usr/local/cliqr/bin/cco_config_wizard.sh


        Configure the server properties.

        Write this down for future reference!

        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.


        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
        Docker Container Timeout

        Defaults to 10m (minutes)

        This field was moved to the External_Script_Executor screen in CloudCenter 4.8.1. In earlier releases, this field was part of the Docker screen (listed above).

        Config_CertsCerts Zip PathProvide the path for the certs.zip file. The default path is /tmp/certs.zip.

        Config_Duration

        (Only available in CloudCenter 4.8.1 and later releases)

        Bootstrap Wait TimeDefaults to 15 minutes
        Max Bootstrap Wait TimeDefaults to 3600 seconds
        Change the default value if this event takes a longer time to complete. The settings range is 3,600 to 2,000,000 seconds.
        Node Heartbeat TimeDefaults to 180000 milliseconds
        Change the default value if this event takes a longer time to complete. The settings range is 180,000 to 2,000,000 milliseconds.
        Node Cleanup TimeoutDefaults to 300 seconds
        Change the default value if this event takes a longer time to complete. The settings range is 300 to 2,000,000 seconds.
      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.

    • Required if your deployment uses the Monitor component.

       CCO SECONDARY and TERTIARY – Configure ELK Properties

      CCO_SECONDARY and CCO_TERTIARY – Configure ELK Properties

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

          sudo -i
      1. Invoke the CCO wizard.

        CCO Wizard Path
        /usr/local/cliqr/bin/cco_config_wizard.sh
      2. Configure the properties for the ELK Information:

        Wizard MenuFieldNotes

        ELK_Info

        ELK Host

        The IP address for the ELK/Monitor host. 

        Elasticsearch PortDisplays 8881 by default.
        Logstash PortDisplays 4560 by default.
        Host IdentifierA 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

        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.

        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.

Upgrading from Non-HA to HA Mode

See Migrate CCO from Non-HA to HA for details.


  • No labels
© 2017 Cisco Systems