Component Modes and Roles
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.
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.
|NON-HA||CCM||VM||CCM web server and database|
|NON-HA-STANDALONE||CCM_SA||VM||Standalone CCM – web server only|
|NON-HA-STANDALONE||MGMTPOSTGRES||VM||Standalone PostgreSQL database server only|
|HA||CCM_SA_PRIMARY||VM||Standalone Primary CCM – web server only|
|HA||CCM_SA_SECONDARY||VM||Standalone Secondary CCM – web server only|
|HA||MGMTPOSTGRES_MASTER||VM||PostgreSQL Master database server|
|HA||MGMTPOSTGRES_SLAVE||VM||PostgreSQL Slave database server|
|HA||CCM_LB||Load Balancer||-||Balance incoming requests across both CCM VMs|
|HA||MGMTPOSTGRES_VIP||Virtual 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|
|NON-HA||MON||VM||Monitor health of Cloud Region and report to the CCM|
|HA||MON_PRIMARY||VM||(Primary) Monitor health of Cloud Region and report to the CCM|
|HA||MON_SECONDARY||VM||(Secondary) Monitor health of Cloud Region and report to the CCM|
|HA||MON_LB||Load Balancer||-||Balance incoming requests across both Monitor VMs|
|HTTP Web Server||BUNDLE_STORE||-||Host CloudCenter agent binaries and out-of-box service scripts|
|VM||PACKAGE_STORE||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
|VM||DOCKER_REGISTRY||Docker-based host container images for out-of-box services|
Per Cloud Region
A 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 c
|HA||CCO_PRIMARY||VM||The Primary Orchestrator|
|HA||CCO_SECONDARY||VM||The Secondary Orchestrator|
|HA||CCO_TERTIARY||VM||The Tertiary Orchestrator|
|HA||CCO_LB||Load Balancer||-||Balance incoming requests across both CCO VMs|
|NON-HA||AMQP||VM||RabbitMQ-based Message Queue|
|HA||AMQP_PRIMARY||VM||Primary RabbitMQ-based Message Queue|
|HA||AMQP_SECONDARY||VM||Secondary RabbitMQ-based Message Queue|
|HA||AMQP_LB||Load Balancer||-||Balance incoming messages across both AMQP VMs|
Dedicated External Script Executor
|NON-HA||EXT_SCRIPT_EXECUTOR||VM||Docker-based isolated script execution environment|
|NON-HA||GUAC||VM||Guacamole-based server to enable web based SSH/VNC/RDP|
|HA||GUAC_PRIMARY||VM||Primary Gucamole server.|
|VM||Secondary Gucamole server.|
|HA||GUAC_LB||Load Balancer||–||Balance incoming messages across both GUAC VMs.|
Linux Worker Image
|VM image||LINUX_WORKER_OS_VERSION||Machine image to be used when launching VMs during application orchestration|
Windows Worker Image
|VM image||WINDOWS_WORKER_OS_VERSION||Machine Image to be used for launching VMs during application orchestration|
- No labels