CliQr is now part of Cisco Learn More About Cisco

Component Modes and Roles

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 installed in different modes in the same installation. For example, you can install 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  = A single VM is required for each component while both the web server and database for the CCM reside on the same VM.
  • NON-HA-STANDALONE  = A single VM is required for each component while the web server and database for the CCM resides on two separate VMs. This is the recommended mode to transition to the HA mode in the future.
  • HA = Two separate VMs are required for each component, including the CCM web server (2) and database (2), and three VMs are required for each CCO instance.

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

Components

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

  • CCM role for a Non-HA deployment
  • CCM_SA and MGMTPOSTGRES roles for a Standalone 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 installed on a per-deployment basis.

CCM

ModeRoleTypeOS OptionsPurpose
NON-HA
CCMVM
  • CentOS7
  • CentOS6
  • RHEL7
  • RHEL6
CCM web server and database
NON-HA-STANDALONE
CCM_SAVMStandalone CCM – web server only
NON-HA-STANDALONEMGMTPOSTGRESVMStandalone PostgreSQL database server only
HA
CCM_SA_PRIMARYVMStandalone Primary CCM – web server only
HA
CCM_SA_SECONDARYVMStandalone Secondary CCM – web server only
HA
MGMTPOSTGRES_MASTERVMPostgreSQL Master database server
HA
MGMTPOSTGRES_SLAVEVMPostgreSQL Slave database server
HA
CCM_LBLoad Balancer -Balance incoming requests across both CCM VMs
HA
MGMTPOSTGRES_VIPVirtual IP (VIP) or Easltic IP (EIP)

 -

Attach to one of the PostgreSQL servers to enable dynamic switching to the active server if one of the servers go down

Monitor

ModeRoleTypeOS OptionsPurpose
NON-HA
MONVM
  • CentOS7
  • CentOS6
  • RHEL7
  • RHEL6
Monitor health of Cloud Region and report to the CCM
HA
MON_PRIMARYVM(Primary) Monitor health of Cloud Region and report to the CCM
HA
MON_SECONDARYVM(Secondary) Monitor health of Cloud Region and report to the CCM
HAMON_LBLoad Balancer-Balance incoming requests across both Monitor VMs

Bundle Store

TypeRoleOS OptionsPurpose
HTTP Web Server    BUNDLE_STORE-Host CloudCenter agent binaries and out-of-box service scripts

 

Package Store

TypeRoleOS OptionsPurpose
VM                                                PACKAGE_STORE
  • CentOS7
  • CentOS6
  • RHEL7
  • RHEL6
Host binaries for out-of-box service scripts and software required to setup other CloudCenter components (JDK, PostgreSQL, and so forth)

Dedicated Docker Registry for Services

TypeRoleOS OptionsPurpose
VM                 DOCKER_REGISTRY
  • CentOS7
  • CentOS6
  • RHEL7
  • RHEL6
Docker-based host container images for out-of-box services

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 install, setup, and configure the following CloudCenter components.

CCO

ModeRoleTypeOS OptionsPurpose
NON-HA
CCOVM
  • CentOS7
  • CentOS6
  • RHEL7
  • RHEL6
The Orchestrator
HA
CCO_PRIMARYVMThe Primary Orchestrator
HA
CCO_SECONDARYVMThe Secondary Orchestrator
HACCO_TERTIARYVMThe Tertiary Orchestrator
HA
CCO_LBLoad Balancer -Balance incoming requests across both CCO VMs

AMQP

ModeRoleTypeOS OptionsPurpose
NON-HA
AMQPVM
  • CentOS7
  • CentOS6
  • RHEL7
  • RHEL6
RabbitMQ-based Message Queue
HA
AMQP_PRIMARYVMPrimary RabbitMQ-based Message Queue
HA
AMQP_SECONDARYVMSecondary RabbitMQ-based Message Queue
HA
AMQP_LBLoad Balancer-Balance incoming messages across both AMQP VMs

Dedicated External Script Executor

ModeRoleTypeOS OptionsPurpose
NON-HAEXT_SCRIPT_EXECUTORVM
  • CentOS7
  • RHEL7
Docker-based isolated script execution environment

Dedicated Guacamole

ModeRoleTypeOS OptionsPurpose
NON-HA
GUACVM
  • CentOS7
  • CentOS6
  • RHEL7
  • RHEL6
Guacamole-based server to enable web based SSH/VNC/RDP
HAGUAC_PRIMARYVMPrimary Gucamole server.
HA

GUAC_SECONDARY

VMSecondary Gucamole server.
HAGUAC_LBLoad BalancerBalance incoming messages across both GUAC VMs.

Linux Worker Image

TypeRoleOS OptionsPurpose
VM image                         LINUX_WORKER_OS_VERSION
  • CentOS7
  • CentOS6
  • RHEL7
  • RHEL6
  • Ubuntu 12.04
  • Ubuntu14.04
Machine image to be used when launching VMs during application orchestration

Windows Worker Image

TypeRoleOS OptionsPurpose
VM image                        WINDOWS_WORKER_OS_VERSION
  • Win2k8,
  • Win2k12
Machine Image to be used for launching VMs during application orchestration

 


  • No labels