CCO (Required)

The CloudCenter Orchestrator (CCO) must be deployed to every cloud region. The CCO is a backend server that intelligently interacts with cloud endpoints to handle application deployment and runtime management. CCO decouples an application from its underlying cloud infrastructure in order to reduce the cloud deployment complexity.

  • CloudCenter requires one CCO per cloud region, unless the application network is completely isolated and does not have outgoing connections.
  • CloudCenter treats an isolated network (VPC) with VPN as a private cloud which 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.

The CCO always requires access to a Bundle Store regardless of your use of worker images or dynamic bootstrapping.

CCOs Per Cloud Region

Depending on the cloud type, one CCO is required for each cloud region or private data center.

Cloud Type

Supports only one combination of these per CCO

Supports any number of these per CCO

Public Clouds
AlibabaRegion
  • Accounts

  • VPCs

AWSRegion
  • Accounts
  • Sub-Accounts
  • Identity and Access Management (IAM)

  • VPCs
AzureRMRegionAccounts
Dimension Data (DiData)

Region

Accounts

Google CloudRegion
  • Accounts
  • Projects
IBM CloudRegion

Accounts

Private Clouds
Azure PackRegion

Accounts

Azure StackRegion

Accounts

Cisco UCSD

UCSD instance

Not applicable

OpenStackRegion
  • Networks
  • Accounts
VMware vCenter

vCenter instance

  • Accounts
  • Datacenters
VMware vCD

vCD instance/endpoint

  • Accounts
  • Organizations
Containers
KubernetesRegionAccounts


CCO ModesRoleTypePurpose
NON-HA
CCOVMThe Orchestrator
HA
CCO_PRIMARYVMThe Primary Orchestrator
HA
CCO_SECONDARYVMThe Secondary Orchestrator
HACCO_TERTIARYVMThe Tertiary Orchestrator
HA
CCO_LBLoad BalancerBalance incoming requests across all three CCO VMs
© 2017-2019 Cisco Systems, Inc. All rights reserved