// removed jquery ui css and js

Upgrade AMQP in Non-HA Mode

Overview

Be sure to review Upgrade Overview before starting this procedure!

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

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 completed the following  procedures:

    • CCM and Database Upgrade
    • CCO Upgrade

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

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

NOW=$(date +"%Y%m%d")
bakdir="/mnt/bak/$NOW"
mkdir -p $bakdir
cd $bakdir

cp -r /usr/local/tomcatgua/webapps/access .

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:

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

    cd $bakdir
    cp -r /usr/local/tomcatgua/webapps/access .
    cp -r /usr/local/tomcatgua/webapps/cliqr-connection-broker .
  2. Run the following commands on the AMQP server.

    sudo –i
    cd /tmp
    chmod 755 core_upgrade.bin
    
    #Set the following only if a local package store is setup:
    export CUSTOM_REPO=<http://local_package_store ip>
    
    ./core_upgrade.bin <ostype> <cloudtype> rabbit
    

    For example: ./core_upgrade.bin centos7 amazon rabbit

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

    rm core_upgrade.bin 
    
  4. Change to the /tmp directory.

    cd /tmp
  5. Run the following commands from your download folder.

    java -jar cco-installer.jar conn_broker-response.xml

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.

    cd $bakdir
    cp -r /usr/local/tomcatgua/webapps/access .
    cp -r /usr/local/tomcatgua/webapps/cliqr-connection-broker .
  2. Run the following commands on the AMQP server.

    sudo –i
    cd /tmp
    chmod 755 core_upgrade.bin
    
    #Set the following only if a local package store is setup:
    export CUSTOM_REPO=<http://local_package_store ip>
    
    ./core_upgrade.bin <ostype> <cloudtype> rabbit
    

    For example: ./core_upgrade.bin centos7 amazon rabbit

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

    rm core_upgrade.bin 
    
  4. Change to the /tmp directory.

    cd /tmp
  5. Run the following commands from your download folder.

    java -jar cco-installer.jar conn_broker-response.xml

Post Upgrade Tasks

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

    cat /usr/local/osmosix/etc/version
  2. Reboot the AMQP server – Be aware of the following consequences if/when you reboot the AMQP server.

    Reboot AMQP

    Reboot AMQP VM

    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:

      rm /usr/local/osmosix/etc/.RABBITINSTALLED
      /usr/local/osmosix/bin/rabbit_config.sh
      reboot
    • 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.

          rabbitmqctl list_users
          Listing users ...
          cliqr [administrator]
          cliqr_worker []
        • If you do not see these users in your database, run the following commands as root (to recreate the users in the AMQP configuration):

          rm /usr/local/osmosix/etc/.RABBITINSTALLED
          bash /usr/local/osmosix/bin/rabbit_config.sh

  3.  Configure the Properties in the GUAC Wizard.

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

    Dedicated Gucamole Setup

    This GUA config wizard step is not required if you have set up a Dedicated Guacamole Server (Optional) server – A self-signed Guacamole certificate is provided out-of-box for Appliance installations.

    AMQP – Configure CCM/CCO Properties for Guacamole Server

    Configure the following gua_config_wizard.sh procedure on both the AMQP PRIMARY server and the AMQP SECONDARY server.

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

        sudo -i
    1. Invoke the GUA wizard.

      GUA Wizard Path
      /usr/local/cliqr/bin/gua_config_wizard.sh
    2. Configure the CCM and CCO (once installed) 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.
    3. Configure the properties for the CCM and CCO (once installed) VMs:

      Wizard MenuFieldPossible 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
      Config_CertsCerts Zip PathProvide the path for the certs.zip file. The default path is /tmp/certs.zip.
    4. Verify your changes and Exit the GUA configuration wizard.

    5. Select Yes, to restart the Tomcat service for the changes to take effect.

      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:

      root> ls -alrt /usr/local/osmosix/etc/.RABBITINSTALLED
      -rw-r--r--. 1 root root o Feb 17 23:07 /user/local/osmosix/etc/.RABBITINSTALLED
      root> rabbitmqctl list_users
      Listing users ...
      cliqr   [administrator]
      cliqr_worker     []
      guest   [administrator]
      root>

      Reboot AMQP

      Reboot AMQP VM

      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:

        rm /usr/local/osmosix/etc/.RABBITINSTALLED
        /usr/local/osmosix/bin/rabbit_config.sh
        reboot
      • 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.

            rabbitmqctl list_users
            Listing users ...
            cliqr [administrator]
            cliqr_worker []
          • If you do not see these users in your database, run the following commands as root (to recreate the users in the AMQP configuration):

            rm /usr/local/osmosix/etc/.RABBITINSTALLED
            bash /usr/local/osmosix/bin/rabbit_config.sh

    You have successfully configured the AMQP instance! Proceed to the CCO (Required) section.

  4. Upgrade the Monitor VM – See Monitor Upgrade for additional context.
  • No labels
© 2017 Cisco Systems