Install AMQP (Required)                                                                                                                                    

 AMQP NON-HA

AMQP NON-HA

The /tmp Alternative

You can download installation files to a directory of your choice. The procedure provided in the CloudCenter documents, recommend using the /tmp folder as the download folder. In some cases, you may not want to use /tmp folder as the temp location as this directory may not allow files to be executed in your environment.

To install CloudCenter on systems where /tmp is set to nosuid or noexec, issue the following command before downloading the component files:

export TEMP_DIR=<any_directory_with_exec_permission>

The /tmp alternative is available for the CCM, CCO, and AMQP components.

Process

  1.  AMQP - Run Core and Appliance Installers

    AMQP – Run Core and Appliance Installers

    1. Download package files:

      See Installer 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.

      2. Download the following required files for this component from software.cisco.com to the /tmp folder on that VM:

        • core_installer.bin
        • cco-installer.jar
        • conn_broker-response.xml
    2. Run the core installer to setup core system components using the following commands:

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

      For example:

      ./core_installer.bin centos7 amazon rabbit
      

      Syntax:

      <ostype>= centos6, centos7, rhel6, rhel7

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

    3. Remove the core_installer.bin file.

       

      rm core_installer.bin 
      
      
    4. Log off and log back in as the root user to ensure JAVA Home is set.

      exit
      sudo -i
    5. Change to the /tmp directory.

      cd /tmp


    6. Run the appliance installer to setup AMQP. 

      java -jar cco-installer.jar conn_broker-response.xml
    7. Reboot the AMQP VM.

  2.  AMQP - Configure CCM/CCO Properties for Guacamole Server

    Unable to render {include} The included page could not be found.

 AMQP HA

AMQP HA

The /tmp Alternative

You can download installation files to a directory of your choice. The procedure provided in the CloudCenter documents, recommend using the /tmp folder as the download folder. In some cases, you may not want to use /tmp folder as the temp location as this directory may not allow files to be executed in your environment.

To install CloudCenter on systems where /tmp is set to nosuid or noexec, issue the following command before downloading the component files:

export TEMP_DIR=<any_directory_with_exec_permission>

The /tmp alternative is available for the CCM, CCO, and AMQP components.

Process

  1.  AMQP_PRIMARY/SECONDARY – Exchange AMQP SSH Keys

     Provide a localhost and ensure that the hostname of the host is resolvable in the /etc/hosts file – see High Availability Best Practices for additional details.

     

    Unable to render {include} The included page could not be found.

  2.  AMQP_PRIMARY - Run Core and Appliance Installers

    AMQP_PRIMARY – Run Core and Appliance Installers
    1. Download package files:

      See Installer 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.

      2. Download the following required files for this component from software.cisco.com to the /tmp folder on that VM:

        • core_installer.bin
        • cco-installer.jar
        • conn_broker-response.xml
    2. Run the core installer to setup core system components using the following commands:

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

      For example:

      ./core_installer.bin centos7 amazon rabbit
      

      Syntax:

      <ostype>= centos6, centos7, rhel6, rhel7

      <cloudtype>= amazon, azureclassic, azurerm, azurepack, google, opsource, openstack, softlayer, vmware, and vcd (run the ./core_installer.bin help command for a complete list)

    3. Remove the core_installer.bin file.

      rm core_installer.bin 
      
    4. Log off and log back in as the root user to ensure JAVA Home is set.

      exit
      sudo -i
    5. Change to the /tmp directory.

      cd /tmp


    6. Run the appliance installer to setup AMQP. 

      java -jar cco-installer.jar conn_broker-response.xml
    7. Reboot the AMQP VM.

  3.  AMQP_PRIMARY - Configure CCM/CCO Properties for Guacamole Server

    Unable to render {include} The included page could not be found.

  4.  AMQP_SECONDARY - Run Core and Appliance Installers

    AMQP_SECONDARY – Run Core and Appliance Installers
    1. Download package files:

      See Installer 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.

      2. Download the following required files for this component from software.cisco.com to the /tmp folder on that VM:

        • core_installer.bin
        • cco-installer.jar
        • conn_broker-response.xml
    2. Run the core installer to setup core system components using the following commands:

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

      For example:

      ./core_installer.bin centos7 amazon rabbit
      

      Syntax:

      <ostype>= centos6, centos7, rhel6, rhel7

      <cloudtype>= amazon, azureclassic, azurerm, azurepack, google, opsource, openstack, softlayer, vmware, and vcd (run the ./core_installer.bin help command for a complete list)

    3. Remove the core_installer.bin file.

       

      rm core_installer.bin 
      
    4. Log off and log back in as the root user to ensure JAVA Home is set.

      exit
      sudo -i
    5. Change to the /tmp directory.

      cd /tmp
    6. Run the appliance installer to setup AMQP. 

      java -jar cco-installer.jar conn_broker-response.xml
    7. Reboot the AMQP VM.

  5.  AMQP_SECONDARY - Configure CCM/CCO Properties for Guacamole Server

    Unable to render {include} The included page could not be found.

  6.  AMQP_PRIMARY - Configure High Availability Properties

    Unable to render {include} The included page could not be found.

  7.  AMQP_LB

    Unable to render {include} The included page could not be found.

 

  • No labels
© 2017-2019 Cisco Systems, Inc. All rights reserved