Cisco CloudCenter 4.6.0 Release Notes

Release Date

First Published: October 1, 2016 

Last Modified: March 23, 2017


  • Installers:
    • The Package Store installer:
      • Is available for CentOS7 and REHL7 operating systems. Continues to be available on Ubuntu 12.04.
      • Installs the Docker registry (additional) that hosts container images for CentOS7 (out of the box services).
    • Installation Details:
  • PostgreSQL Database:
    • CloudCenter 4.6.0 uses PostgreSQL database instead of MySQL.

    • Installer and appliance installation and configuration procedures for the PostgreSQL database is similar to the MySQL procedures in previous releases.

    • Upgrade to 4.6 handles data migration from MySQL to PostgreSQL.

    • In High Availability (HA) Mode, the PostgreSQL DB should be setup on two standalone servers in a master-slave replication mode.

    • In Non-HA mode, the database may be installed with CCM or as a standalone server. To have PostgreSQL installed in a standalone VM, you must open Port 5432 to the CCM.
    • See Manual Installation for additional context.
  • High Availability and Data Replication:
    • You can now configure all the replication changes in the db_config_wizard directly. 

    • HA setup requires databases to be installed in separate virtual machines.

    • Database servers are setup in a master-slave replication mode unlike previous versions where the MySQL database was setup in master-master mode.
  • Upgrade to CloudCenter 4.6.0:


  • VMware: IPAM Naming Callout – Ability to configure the following features
    • The Instance Naming Strategy to identify callouts.

    • The Instance IPAM Strategy at the cloud region level.
    • Specify the name of the Customization Spec (already created on the VMware vSphere console), in the IPAM callout script.
    • See VM Name Config for additional context.
  • OpenStack: Ability to configure either V2 or V3 endpoints.
    • When you add an OpenStack cloud account, can choose V2 or V3 API endpoints.

    • If you choose V3 API, provide either the default Domain ID or Default Domain Name.

    • The cloud region setting validates the region – earlier releases did not valid region settings.

    • See Configure Cloud(s) > Configure an OpenStack Cloud for additional context.

  • Amazon: Effective CloudCenter 4.6.0, Cisco continues to provide support for Amazon EC2 VPC accounts and has discontinued support for Amazon EC2 Classic accounts.

Applications and Services

  • Availability Sets and Zones
    • Virtual machines launched as part of a cluster can be evenly spread across multiple Availability Zones (OpenStack, AWS) or Availability Set (AzureRM).

    • Even during scaling operations (up or down), the VMs continue to be scaled across the zones.
    • This feature is specific to each tier within an application and applies to AWS, AzureRM, and OpenStack cloud configurations.
    • See Availability Sets and Zones for additional context.
  • Containerize OOB Service:
    • If your worker image has the Docker engine installed, some out-of-box (OOB) CloudCenter services will be run as containers inside the Application VM (worker): Apache2, Memcached, MongoDB, MySQL, Nginx, and Tomcat6/7.

    • See Dedicated Docker Registry Installation for additional context.
    • See Services for a complete list of OOB services.
  • Passing information from external services:

    • The CloudCenter external service accepts ipAddress, hostName, and environment as input parameters.

    • See External Service > Passing Information from External Services for additional context.

Administration and Governance

  • Extensions:
    • The  APIC policy model is available as a standalone extension on the CloudCenter platform and provides increased ease when creating ACI objects by allowing better, faster, and easier network isolation. 
    • You can create an ACI extension to extend the capabilities of the CCO to provision networks in an ACI environment. See ACI Integration for additional context.
    • You can then use Extensions to configure CloudCenter resources at the Deployment Environment level and Application Profile level. See Extensions for additional context.
    • Configure ACI Extensions using CloudCenter APIs. See the API section below for additional details.
  • Deployment Environment Enhancements:
    • The Deployment Environment management and Job Submission process is redesigned.

    • Ability to create security around cloud defaults and at the same time, retain the functionality of configured defaults deployment settings for each deployment environment.

    • Ability to lock deployment environment defaults so to ensure that defaults are not changed by end users during the deployment process.

    • Flexibility to define deployment environment default configurations, but not lock them, so end users can select the default value at the time of deployment but also have the option to select any other value allowed in the list.

    • Ability to specify simplified networks that encapsulate network settings for clouds into user friendly names which are presented to the end user at the time of deployment.

    • Prior to CloudCenter 4.6.0, you could select the default instance along with the default cloud region. If you upgrade to CloudCenter 4.6.0, you must manually select your default instance again.

    • See Deployment Environment Defaults for additional context.
    • If using the Submit Job (v2) API, you have the added advantage of completing the forms associated with the New Deployment workflow and retrieving the corresponding JSON request body for use with the API(s). See the API section below for API-specific details.

  • Reports:
    • The new Usage Summary Report aggregates the cloud cost by Tenant or by Cloud Region. Each Tenant or Cloud Region is aggregated as a group as well as individually when you click the dropdown arrow for each


The Tomcat setting in CloudCenter appliances had a short Session ID of 32 characters. Effective CloudCenter 4.6.0, the Tomcat Session ID settings for CloudCenter appliances have a length of 256 characters. This setting is also changed in the new installation files. Existing deployments will continue to have the shorter Session ID.


The following features are deprecated effective CloudCenter 4.6:

  • The Manage VM Inventory (only available in CloudCenter 4.5 and earlier releases) option is now deprecated.

    • The managed inventory option is now provided in the Managed VM Inventory Report and provides details based on billing and cost-related database views.

    • The non-managed inventory option no longer uses the deployment environment as the source. Instead, it relies on cloud account and cloud region details. See View Non-Managed Cloud Details for additional context. This change was made to ensure that users who are further down the tenant hierarchy do not have the ability to view VMs for which they do not have manage permissions.

  • The CloudCenter platform's Spot Instance feature is no longer supported.
  • The CloudCenter 4.6 platform no longer supports the following clouds and cloud accounts:
    • Bracket
    • Cisco Cloud Service (CSS)
    • HP
    • CloudN
    • CloudStack
    • Amazon EC2 Classic

These references are removed from the CloudCenter 4.6 documentation.


  • New CCM UI Enhancements:
    • New Dashboard: The Dashboard now boasts a new Summary dashlet that displays resource information based on the Compute Cost spending, Run Time, and the Running VMs inventory. Administrators can choose to see the usage and cost summary for the entire tenant hierarchy. The popular dashlets continue to be available in the CloudCenter 4.6.0 Dashboard along with a few new dashlets. See The Dashboard for additional context.

    • Deployment Environment Usability: The Deployment Environment management and Job Submission process have been completely redesigned to enhance usability.

    • New UI Behavior: The CloudCenter UI provides real time feedback on errors that you encounter while configuring a deployment environment or deploying a new job. See UI Behavior for additional context.


CloudCenter 4.6.0 introduces v2 APIs, where applicable. The following list identifies APIs with a new version. If a new API is introduced for the first time, it continues to use v1 as it is still the first version of that particular API. The CloudCenter API Overview section provides specific details on difference between v1 and v2. Additionally, see the Documentation section below to understand the specific API nuances.


  • Feature Documentation: See the links provided in this page for additional context.
  • Re-branding:
    • CliQr is now part of Cisco.
    • The entire documentation set for CloudCenter 4.6 reflects this change.
    • The documentation website URL is also available from

  • Documentation Versions: From, use the Documentation Version dropdown on the left pane to select the documentation version that applies to your CloudCenter release. By default, the latest documentation version is displayed in the home page.
  • Search Results: All documentation search results display all available releases from each CloudCenter version. Select the version of choice. The home page Restrict Your Documentation Search field (highlighted in the following image) restricts the search results to just that release.

    For example, the home page for CloudCenter 4.6 is Cisco CloudCenter Documentation, Version 4.6 – type your search text in the Search Documentation field.
  • v2 APIs Documentation: This is the first time that the CloudCenter platform offers a new version of older APIs, where available. If a new version is available, you will see the option to review the information for each version under a separate section. For Example:

Known Issues

CloudCenter 4.6.0 has the following known issues:

  • The Done button is currently not enabled for restricted users in a deployment environment. Consequently, restricted users cannot add or remove the cloud and accounts. Restricted users can add new clouds or cloud accounts, but will not be able to remove those regions or cloud accounts if the deployment environment owner does not have access to those resources.
  • If you have launched an application that uses the Elastic Load Balancer (ELB) service in a release prior to CloudCenter 4.6.0, be aware that you cannot suspend or resume this service in CloudCenter 4.6.0. You can workaround this issue by backing up your application/service information and terminating that application before upgrading to CloudCenter 4.6.0. Your can then relaunch this application after the upgrade.
  • When you deploy an application to a SoftLayer cloud, the application deploys successfully. However, when you try to power off or reboot the VM from the Managed VM Inventory Report page, the task does not complete. These operations continue to work from the  Job Details page.
  • When you build a service bundle for a Windows environment, and the script residing inside the bundle does not have an extension type, the script may not execute as designed. For example, if you named the script as  service instead of service.cmd or service.ps1, then this script may not execute as designed. To work around this issue, verify that any script that resides inside the service bundle contains a valid extension (based on the script) when using it in a Windows environment.
  • The All Reports data that is displayed in response to a 30-Day time period request only displays data from the 1st of the month, not for the previous 30 days. To work around this issue, use the date Range option and provide the begin and end date for the required period.
  • The Path parameter defined in an application profile (global parameter or tier-level custom parameter) does not display as designed on the Deployments page.

  • The Suspend operation is not listed in the responses for the v1 Get Job Details API and the v2 View Job Details API.
  • When you map a VM Template to an image, the deployment may fail. To workaround this issue, convert the template to a VM, take a snapshot, and use the Linked Clone mode. See VMware Configurations for additional context.

Resolved Issues

The following issues were resolved/addressed in CloudCenter 4.6.0:

  • Issue: When using the API to create an action policy when a job status changes, the request body is missing data that should be available. For example, NewStatus. In addition, status seems to have taken the expected value of NewStatus.
    Resolution: While this issue was addressed by renaming the attributes and verifying that the right data displayed for each status attribute, CloudCenter 4.6.0 also introduces a new attribute for the older state, called oldStatus, which displays the status of the job before the job status changed.

  • Issue: In a multi-tier hybrid deployment with one tier using AWS cloud and another tier using AzureRM cloud, the information is populated from one tier to the other. However, during a scaling event (scale up/down) the information is not populated from one tier to the next.
    Resolution: CloudCenter 4.6.1 includes a fix to ensure that the information is accurately propagated.

  • No labels