// removed jquery ui css and js

Virtual Appliance Overview

 

CloudCenter Appliance Architecture

CloudCenter Architecture Overview

Virtual Appliance Files

The easiest way to install CloudCenter components is to use the Virtual Appliance method. A majority of our CloudCenter customers use Virtual Appliances to setup all CloudCenter components as customers can use pre-packaged and Cisco-certified virtual appliances

Virtual appliances are available for each CloudCenter component from software.cisco.com – see the README file to obtain instructions.

See Virtual Appliances for a complete list of supported components for each cloud.

To manually install CloudCenter using your own base operating system images and the CloudCenter installers, contact the CloudCenter Support team to obtain the manual installer instructions.

Modes

You can set up CloudCenter components in various modes based on scalability or high availability requirements. Each mode has its unique infrastructure requirements (VM, Load Balancer-LB, Virtual/Elastic IP address). Different CloudCenter components can be setup in different modes in the same deployment. For example, you can setup CCM in HA mode and the AMQP in Non-HA mode.

Sample network architectural diagrams for each mode are available at the end of this section.

  • NON-HA: This mode is only available for all components.

  • HA: This mode is only available for CCM, CCO, and AMQP servers.

    • Two separate VMs are required for the following components:

      • CCM web server (2) plus a load balancer

      • PostgreSQL database (2)

      • AMQP (2) plus a load balancer

    • Three separate VMs are required for the CCO (3) plus a load balancer

See the tables at the end of this page for a detailed breakdown of the number of servers required for each mode.

Network Architecture Diagrams

VA Buttons 4.8.2

Components

The CloudCenter platform is made up of 4 required components (CCM, CCO, AMPQ, and Log Collector) and multiple optional components. Each component VM is assigned a role depending on the mode (Non-HA or HA) in which you setup each component. For example:

  • CCM_SA and MGMTPOSTGRES roles for a Non-HA deployment

  • CCM_SA_PRIMARY, CCM_SA_SECONDARY, MGMTPOSTGRES_MASTER, MGMTPOSTGRES_SLAVE, CCM_LB roles for a HA deployment

The roles for each component and mode are described in the following sections.

Per CloudCenter Deployment

These components are setup on a per-deployment basis.

CCM (Required)

The CloudCenter Manager (CCM) is a centralized management console that allows users to model, deploy, and manage workloads on different clouds.

CCM ModesRole NameTypePurpose
NON-HA
CCM_SAVMNon-HA standalone CCM – web server only
NON-HA
MGMTPOSTGRESVMNon-HA standalone PostgreSQL database server only
HA
CCM_SA_PRIMARYVMNon-HA standalone Primary CCM – web server only
HA
CCM_SA_SECONDARYVMNon-HA standalone Secondary CCM – web server only
HA
MGMTPOSTGRES_MASTERVMPostgreSQL Master database server
HA
MGMTPOSTGRES_SLAVEVMPostgreSQL Slave database server
HA
CCM_LBLoad BalancerBalance incoming requests across both CCM VMs
HA
MGMTPOSTGRES_VIPVirtual IP (VIP) or Elastic IP (EIP)Attach to one of the PostgreSQL servers to enable dynamic switching to the active server if one of the servers go down

The Log Collector

The Log Collector server is a required, independent CloudCenter component that allows you to export and download the resulting log files when required.

The Elasticsearch, Logstash, and Kibana tools, collectively referred to as the ELK stack, are installed as part of the Log Collector installation procedure.

Log Collector ModesRoleTypePurpose
NON-HA
MONVMExport and download the resulting log files when required.

REPO Virtual Appliance

The REPO virtual appliance contains the virtual appliances for multiple software packages and smaller components (service bundles, software packages. binaries, scripts, Docker images, and so forth) used by the CloudCenter platform. Once you install and configure the REPO virtual appliance, the included components are installed and you can configure the associated properties when required in the CCM wizard, the CCO wizard, or the AMQP wizard.

This REPO appliance:

  • Uses Nginx on a CentOS7 server.
  • Is version specific to each CloudCenter Release.
Repository ModeRoleTypePurpose
NON-HAREPOVMFor service bundles, package store, scripts, and so forth


Per Cloud Region

Cloud Region refers to single public cloud region, private virtualized datacenter, or private cloud supported by CloudCenter. Each cloud region is identified in the CCM UI when you configure clouds. For every cloud region that needs to be managed by the CloudCenter platform, you must setup and configure the following CloudCenter components.

CCO (Required)

The CloudCenter Orchestrator (CCO) must be deployed to every cloud region. The CCO is a backend server that intelligently interacts with cloud endpoints to handle application deployment and runtime management. CCO decouples an application from its underlying cloud infrastructure in order to reduce the cloud deployment complexity.

  • CloudCenter requires one CCO per cloud region, unless the application network is completely isolated and does not have outgoing connections.
  • CloudCenter treats an isolated network (VPC) with VPN as a private cloud which requires a separate CCO.
  • Each CCO must register with a CCM. The CCO communicates directly with the CCM irrespective of the cloud on which the CCO is deployed.
CCOs Per Cloud Region

Depending on the cloud type, one CCO is required for each cloud region or private data center.

Cloud Type

Supports only one combination of these per CCO

Supports any number of these per CCO

AWSRegion
  • Accounts
  • Sub-Accounts
  • Identity and Access Management (IAM)

VMware vCenter

vCenter instance

  • Datacenter
  • Clusters
  • Resource pools
  • Accounts
  • Datastores
  • Datastore clusters
VMware vCD

vCD instance/endpoint

vCD

MicrosoftAzureRegion
  • Networks
  • Cloud services
  • Accounts
Google CloudRegion
  • Projects
  • Accounts
OpenStackRegion
  • Tenants
  • Networks
  • Accounts
SoftLayer (Bluemix)Region
  • Accounts
  • Networks
AlibabaRegion
  • Accounts

  • Networks

Dimension Data (DiData)

Region

  • Accounts

  • Networks

Cisco UCSD

UCSD instance

Not applicable


CCO ModesRoleTypePurpose
NON-HA
CCOVMThe Orchestrator
HA
CCO_PRIMARYVMThe Primary Orchestrator
HA
CCO_SECONDARYVMThe Secondary Orchestrator
HACCO_TERTIARYVMThe Tertiary Orchestrator
HA
CCO_LBLoad BalancerBalance incoming requests across all three CCO VMs

AMQP (Required)

The CloudCenter platform features Advanced Message Queuing Protocol (AMQP) based communication between the CCO and the Agent VM. The CloudCenter platform incorporates RabbitMQ as the open source message broker for AMQP implementation.

If your application VMs run in isolated networks (like Amazon's VPC), setup your NAT rules for only outgoing traffic so that your VMs can connect to RabbitMQ.

The following diagram shows the association between CloudCenter components and AMQP. Note that one AMQP instance is required for each CCO implementation. 482 Guac Amqp CCM

AMQP ModesRoleTypePurpose
NON-HA
AMQPVMRabbitMQ-based Message Queue
HA
AMQP_PRIMARYVMPrimary RabbitMQ-based Message Queue
HA
AMQP_SECONDARYVMSecondary RabbitMQ-based Message Queue
HA
AMQP_LBLoad BalancerBalance incoming messages across both AMQP VMs

Pre-Bootstrap Images (Required for Clouds that do not support Dynamic Bootstrapping)

Cloud Mappings for Images defined in CloudCenter determine the image/template that will be used to instantiate new virtual machines for specific clouds when launching user workloads. These cloud mappings are references to images in the public/private cloud (example ami for amazon or qcow/raw for OpenStack) or templates / snapshots in private datacenters like VMware.

Bootstrapping is a mechanism that enables the download and installation of the CloudCenter management agent on VM.

Images/templates/snapshots may be pre-bootstrapped or dynamically bootstrapped. Pre-bootstrapping involves installation of the scripts, packages etc required for bootstrapping of the image. On the other hand, in dynamic bootstrapping, these scripts and packages are dynamically injected into the VM. Dynamic bootstrapping is not supported on certain clouds like VMware and therefore the images need to be pre-bootstrapped. Users may choose to pre-bootstrap images even on clouds that do support dynamic bootstrapping for performance or other considerations. The CloudCenter platform ships with pre-bootstrapped CentOS6 image for clouds listed in the following table. For other OS or application images, users can pre-bootstrap the images using the relevant Linux or Windows installers.

OS TypeRoleOS OptionsPurpose
LINUX                       LINUX_WORKER_OS_VERSION
  • CentOS7
  • CentOS6
  • RHEL7
  • RHEL6
  • Ubuntu14.04
  • Ubuntu16.04
Machine image to be used when launching VMs during application orchestration.

VM image

WINDOWS_WORKER_OS_VERSION
  • Win2k8
  • Win2k12
  • Win2k16
Machine Image to be used for launching VMs during application orchestration.


Expected VM Count for CloudCenter Deployments

A basic deployment with 1 cloud region, typically requires the following VMs:

Required Components     

Non-HA
HANotes
CCM1 VM2 VMsAccess to the CCM UI
MGMTPOSTGRES1VM2 VMsCCM Database
CCM LB-1 VMLB in HA mode
CCO1VM3 VMs3 VMs per cloud region
CCO LB-1 VMsLB in HA mode – 1 VM per cloud region
AMQP1 VM2 VMsPer cloud region
AMQP LB-1 VM  LB in HA mode
Log Collector1 VM1 VMRequired for logs
Total5 VMs13 VMsTypical BASIC deployments

A basic deployment with 2 cloud regions, typically requires the following VMs:

Required Components    Non-HA
HANotes
CCM1 VM2 VMsAccess to the CCM UI
MGMTPOSTGRES1 VM2 VMsCCM Database
CCM LB-1 VMLB in HA mode
CCO2 VMs6 VMs3 VMs per cloud region for HA mode
CCO LB-2 VMsLB in HA mode – 1 VM per cloud region
AMQP2 VMs4 VMsPer cloud region
AMQP LB-2 VM  LB in HA mode
Log Collector1 VM1 VMRequired for logs
Total7 VMs20 VMsTypical BASIC deployments

© 2017-2018 Cisco Systems, Inc. All rights reserved