CloudCenter 4.8 has reached End of Life (EOL) as of November 14, 2018. See End of Support Notices for additional context.

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.
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

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

VMware vCenter

vCenter instance

  • Datacenter
  • Clusters
  • Resource pools
  • Accounts
  • Datastores
  • Datastore clusters
VMware vCD

vCD instance/endpoint


  • Networks
  • Cloud services
  • Accounts
Google CloudRegion
  • Projects
  • Accounts
  • Tenants
  • Networks
  • Accounts
SoftLayer (Bluemix)Region
  • Accounts
  • Networks
  • Accounts

  • Networks

Dimension Data (DiData)


  • Accounts

  • Networks

Cisco UCSD

UCSD instance

Not applicable

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