CliQr is now part of Cisco Learn More About Cisco

The CloudCenter Orchestrator (CCO), also referred to as Orchestrator, has the following characteristics:

  • Is a patented multi-tenant orchestration tier that is transparent to users, and resides in datacenter, private cloud, and public cloud environments.
  • Decouples an application from its underlying cloud infrastructure, and isolates the complexity of the cloud infrastructure.
  • Is a virtual backend server that intelligently encapsulates the best practices of each cloud and does not add any performance overhead.
  • It acts as a cloud controller and seamlessly allows enterprises to govern and manage their applications in the cloud.
  • One CCO is required for each public cloud region or private cloud datacenter:
    • Enterprise users can download and install a CCO to their private cloud and configure it to connect to their CCMs.
    • A single CCO can manage up to 10,000 Virtual Machines (VMs) in a public, private, or hybrid cloud.
    • The CCO can also be deployed as a cluster to provide additional scalability and to avoid a single point of failure.
    • 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.

      Cloud Type

      Supports One (Only one combination of these per CCO)

      Supports Multiple (Any number of these per CCO)

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

        Icon

        To use IAM roles, you must launch the CCO VM using the admin role so you can use the IAM role at any point in the future. Launching a CCO VM with the admin role allows you to use either the IAM role or the classic key/secret key access at any time.

      vCentermultiple vCenter Datacenter (VCD)
      • Clusters
      • Resource pools
      • Accounts
      • Datastores
      • Datastore clusters

      GCERegion  Projects
      AzureRegion  
      • Networks
      • Cloud services
       
      OpenStackRegion
      • Tenants
      • Networks
      SoftLayerRegion
      • Accounts
      • Networks
  • Each CCO must register with a CCM. The CCO communicates directly with the CCM irrespective of the cloud on which the CCO is deployed.
  • It receives application management instructions from the CCM and interfaces with each cloud provider to call the cloud layer, spin the infrastructure, deploy the application, and manage the deployment.
  • See HA Best Practices > CCO for additional context on highly available CCOs.