Component Modes and Roles
This section explains various modes available for each CloudCenter component along with its unique infrastructure requirements.
Role: Identifies each infrastructure element. These roles are extensively used in each installation and configuration procedure.Icon
To identify IP address associated to specific roles, documentation follows the convention ROLE_IP format. For example, IP address for a Virtual Machine (VM) assigned the role CCM would be referenced as CCM_IP
- Mode: You can set up CloudCenter components in various modes based on scalability or high availability requirements. Each mode has its unique infrastructure requirements (VMs, Load Balancers, Virtual/Elastic IPs).
- NON-HA-STANDALONE = Web server and database are installed on two separate VMs.
- NON-HA = A single VM is configured with web server and database.
- HA = Two separate instances, each contains both the web server and database and are configured for high availability. See HA Best Practices for additional context.
- Type: Identifies the infrastructure type that is required for each mode and role. The type can be a VM, or a load balancer, or a web server, or a VM image, and so forth.
- OS Options: Out-of-box available for this mode.
|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|
Depending on your mode:
- NON-HA = One VM
HA = Two VMs must be set up and configured for high availability, assuming you have an existing load balancer. See HA Best Practices for additional context.Icon
If you do not have an existing load balancer VM, you will need a third VM specifically for this purpose – for each component that requires HA.
|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.|
|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|
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