CCO (Required)                                                                                                                                       

 CCO NON-HA

CCO NON-HA                                                                       

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

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

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.

Purpose

  1.  CCO - Run Core and Appliance Installers

    CCO – 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
        • cco-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> cco

      For example:

      ./core_installer.bin centos7 amazon cco
      

      Syntax:

      <ostype>= centos6, centos7, rhel6, rhel7

      <cloudtype>= amazon, azureclassic, azurerm, azurepack, google, opsource, openstack, softlayer, vmware, or 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 the CCO. 

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

  2.  CCO - Configure CCO Properties

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

 CCO HA

Install CCO HA Using Installer                                                                                 

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

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

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.

Purpose

  1.  CCO HA - Run Core Installer and Setup SSH Communication

    CCO HA – Run Core Installer and Setup SSH Communication

    To run the core installer and setup SSH communication for CCO_PRIMARY, CCO_SECONDARY, and CCO_TERTIARY, follow this procedure.

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

      For example:

      ./core_installer.bin centos7 amazon cco 
      

      Syntax:

      <ostype>= centos6, centos7, rhel6, rhel7

      <cloudtype>= amazon, openstack, vmware (run the ./core_installer.bin help command for a complete list)

    3. Remove the core_installer.bin file.

      rm core_installer.bin 
      
    4. Perform Steps 1 to 4 (Steps a to d) on the CCO_SECONDARY instance.
    5. Perform Steps 1 to 4 (Steps a to d) on the CCO_TERTIARY instance.
    6. Exchange the SSH keys between the CCO_PRIMARY, CCO_SECONDARY, and CCO_TERTIARY instances.

      You do not need to repeat Step 7 for the CCO_SECONDARY and CCO_TERTIARY instances as the same SSH key is used for all three instances.

       

      1. On the CCO_PRIMARY instance, execute the following to generate a new SSH key. 

        sudo -i
        ssh-keygen -t rsa
        cd ~/.ssh
        cat id_rsa.pub >> authorized_keys
      2. Copy the id_rsa files (~/.ssh/id_rsa and ~/.ssh/id_rsa.pub) from CCO_PRIMARY to the same location on CCO_SECONDARY and CCO_TERTIARY. On CCO_SECONDARY and CCO_TERTIARY, if the .ssh directory does not exist, create it using the following commands before copying the files.

        sudo -i
        mkdir -p ~/.ssh
        chmod 700 ~/.ssh
      3. On the CCO_SECONDARY and CCO_TERTIARY, execute the following to add a new SSH key.

        sudo -i
        chmod 400 ~/.ssh/id_rsa*
        cat id_rsa.pub >> authorized_keys
      4. Verify mutual SSH access between the CCO_PRIMARY, CCO_SECONDARY, and CCO_TERTIARY by running the following command on each VM.

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

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

    7. Run the appliance installer to setup the CCO on the CCO_PRIMARY, CCO_SECONDARY, and CCO_TERTIARY by running the following command on each VM.

      cd /tmp
      java -jar cco-installer.jar cco-response.xml

       

    8. Reboot the CCO_PRIMARY, CCO_SECONDARY, and CCO_TERTIARY VMs.

  2.  CCO_PRIMARY - Configure CCO Properties

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

  3.  CCO_LB

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

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