- Required CloudCenter Components
- Optional CloudCenter Components
- Network Architecture
- HA Network Architecture
Required CloudCenter Components
The CloudCenter Manager (CCM), sometimes called the Manager or the Management server, is a centralized management tier that acts as a dashboard for users to model, migrate, and manage deployments, and for unified administration and governance of clouds and users using either Deployment Models.
See CCM for additional details.
Per Cloud Region
A Cloud Region refers to single public cloud, datacenter, or private cloud supported by CloudCenter. Each cloud region is identified in the CCM UI when you configure clouds.
The CloudCenter Orchestrator (CCO), also called Orchestrator, is transparent to users, and resides in the datacenter, private cloud, or public cloud environments. It decouples an application from its underlying cloud infrastructure, and isolates the complexity of the cloud infrastructure.
CloudCenter requires one CCO per cloud region or datacenter, unless the application network is completely isolated and does not have outgoing connections. CloudCenter treats an isolated network as a private cloud and 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.
See CCO for additional details.
If the application VMs run in isolated networks (like Amazon's VPC), be sure to setup proper NAT rule (only outgoing needed) to allow application VMs to connect to RabbitMQ.
Dedicated External Script Executor (Conditional)
The CloudCenter platform provides the ability to use custom scripts that are executed during various phases of the application lifecycle. These custom scripts run inside a Docker-based script executor and depend on the OS in use by each CCO.
You may also opt to setup a dedicated script executor (standalone Docker container) for regions using RHEL 7x or CentOS 7x for the CCO server to address increased scalability considerations.
Optional CloudCenter Components
Optional CloudCenter Components
Dedicated Guacamole Server (Per Cloud Region)
The CloudCenter platform use a Guacamole server to enable web based SSH/VNC/RDP to Virtual Machines (VMs) launched during the application lifecycle process. The Guacamole component is embedded, by default, in the AMQP server.
If you do not want the AMQP IP address to be routable by end user, you may opt to setup a dedicated (standalone) Guacamole server for a cloud region.
The Cloud Health Monitor (monitor) is an optional, independent CloudCenter component that monitors the cloud and consists of two sub-components: health status and
See Cloud Health Monitor for additional context.
Effective CloudCenter 4.7.0, the Elasticsearch, Logstash, and Kibana, collectively referred to as the ELK stack, are installed by default when you install the Health Monitor Installer or Appliance. See Download Log File for additional context.
The bundle store is a repository that contains the CloudCenter-specific agent and service bundles. You must download and install these bundles on the VMs (worker or application VMs) launched by CloudCenter as part of the application orchestration process.
SeeBundle Store for additional context.
The package store is a repository that contains binaries for all third-party application services (out-of-box services) as well as binaries for several components required for the CloudCenter installation itself.
Seefor additional context.
Dedicated Docker Registry for Services
HA Network Architecture