Installation and Configuration Overview

Installation Approach

By this time, you should have completed Phases 1, 2, and 3 before starting Phase 4. If you have not completed these phases, go back to the Installation Approach and Workflow section and review where you are in this process.

Need instructions for a specific component?

If you need to view instructions for a specific component, see CloudCenter Installers. However, the CloudCenter platform requires you to install components in the order provided in the Installation Tasks section below.

Installation Tasks

This section walks through the installation process to ensure that you complete the following tasks for each CloudCenter component:

  1. Download the required files (identified in each component) from software.cisco.com to the /tmp folder. See Installer Overview > Installation Options for additional context.

  2. Run the installer for each component.

    If you prefer to run the virtual appliance, see Phase 4 Overview for Virtual Appliances for availability details.

    OrderComponentPer Cloud Region or Per Deployment?Required?
    1CCMPer DeploymentRequired
    2MonitorPer Deployment

    Required

    3Bundle StorePer Deployment

     

    Required if you do not have Internet access

    4Package StorePer Deployment
    5Dedicated Docker RegistryPer Deployment
    6CCOPer Cloud RegionRequired
    7AMQPPer Cloud RegionRequired
    8External Script ExecutorPer Cloud RegionRequired if
    RHEL/CentOS 6.x
    9Dedicated GuacamolePer Cloud RegionRequired to
    restrict AMQP server access
    10Custom Images for Application VMs (Worker)Per Cloud RegionRequired for Clouds that do not support Dynamic Bootstrapping (as identified in Base OS Images)
  3. Invoke the wizard to configure the component properties.

 

Understanding Installer and Upgrade Files

The following table explains the purpose of each installer file that is required to install the CloudCenter platform.

FileDescription
*_installer.bin

This file is used for one-time installation of OS-based components. It is a binary file that installs OS-related packages required for the CloudCenter platform to function. This file contains the Tomcat, OS packages, Java, Database, AMQP servers, and so forth.

*-response.xmlThis file is used during the installation process. It includes responses to installer questions (similar to the unattended response file for installers) for different CloudCenter components. This file allows you to customize specific details: for example, the database location.
*_installer.jarThis file is used during the installation and upgrade process. It includes product-specific WAR and CONFIG files like ROOT.war, config wizards, SSL certificates, and so forth.
*_upgrade.bin

This file is only used during an upgrade when a change is required to the underlying OS and OS packages. It is binary file that installs OS_related packages required required for the CloudCenter platform to function. This file contains release-specific dependencies. Be sure to review High Availability Best Practices and Upgrade Overview sections before using these files.

bundle_artifacts.zip

This file contains the Bundle files (agent and service files), the Package files (out-of-box services), the base Docker image (by default, CentOS 7 images), and numerous bootstrap and installer files. Be sure to review Virtual Appliance Overview for additional context.

agent-lite-linux-bundle.tar.gz

This file is release specific and is required to install the lightweight agent bundle (sometimes referred to as agent lite) on Linux VMs. Be sure to review Virtual Machine Management > Install CloudCenter Agent before using this file.

agent-lite-windows-bundle.zip

This file is release specific and is required to install the lightweight agent bundle (sometimes referred to as agent lite) on Windows VMs. Be sure to review Virtual Machine Management > Install CloudCenter Agent before using this file.

docker.tar

This file is specific to the Docker version and is require to upgrade the Docker image – it is not required with every release. If a version requires the CloudCenter-supported Docker image to be upgraded, use the procedure provided in this page. See Docker Image Upgrade for additional context.

 

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