CliQr is now part of Cisco Learn More About Cisco

CloudCenter Architecture

Overview

Required CloudCenter Components

CCM

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.

 Clouds Supported by CloudCenter

For a list of clouds supported by CloudCenter:

For every cloud region that needs to be managed by the CloudCenter platform, you must install, setup, and configure the following  CloudCenter components.

Cloud Region ComponentsDescription

CCO

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.

Icon

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.

AMQP

The CloudCenter platform includes Advanced Message Queuing Protocol (AMQP) based communication between the CCO and the Agent. The CloudCenter platform uses RabbitMQ as the open source message broker to implement AMQP.

Icon

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.

CCO Server's Base OS ImageThe Script Executor Setup
RHEL 7.x and CentOS 7.x

Embedded in the CCO by default on the OS(s) used by CloudCenter.

Scalability Considerations

Icon

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

For every cloud region that needs to be managed by the CloudCenter platform, you can optionally install, setup, and configure the following CloudCenter components:

Optional CloudCenter Components

Description

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.

Icon

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.

Monitor

The Cloud Health Monitor (monitor) is an optional, independent CloudCenter component that monitors the cloud and CCO health status and consists of two sub-components:

  • The Health Check Manager: Polls the monitored clouds to collect health status information.

  • The Health Status Query Service: A set of web services that report the cloud health status data.

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.

Bundle Store

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.

  • With Internet Connection: The default bundle store is hosted at (cdn.cliqr.com) and CloudCenter deployments where the Application VMs have access to the internet can use the default bundle store.

  • Isolated Environments: For environments where connectivity to the internet is restricted, create a local bundle store and register it with the CCO(s).

See Bundle Store  for additional context.

Package Store

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.

  • With Internet Connection: The default package store is hosted at repo.cliqrtech.com and CloudCenter deployments where the Application VMs have access to the internet can use the default pacage store.

  • Isolated Environments: For environments where connectivity to the internet is restricted, create a local package store and register it with the CCO(s).

See Package Store for additional context.

Dedicated Docker Registry for Services

You can also launch an isolated Docker container when you define a custom service using a VM-based service or an external service at the container level.

  • With Internet Connection: Use the Docker hub to download service images

  • Isolated Environments: For environments where connectivity to the internet is restricted, setup a dedicated Docker container or use the Package Store option.

Base OS Image Preparation

You can also use the CloudCenter installer binary to create CloudCenter-enabled images on different clouds and regions.

See Base OS Images for additional context.

Network Architecture

CloudCenter Network Architecture

 

HA Network Architecture

HA Network Architecture