Cisco CloudCenter Release Notes, Release 4.6.0 First Published: October 1, 2016Last Modified: March 23, 2017

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706USAhttp://www.cisco.comTel: 408 526-4000 800 553-NETS (6387)Fax: 408 527-0883

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITEDWARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITHTHE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain versionof the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANYOTHERWARRANTYHEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS"WITH ALL FAULTS.CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OFMERCHANTABILITY, FITNESS FORA PARTICULAR PURPOSEANDNONINFRINGEMENTORARISING FROMACOURSEOFDEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUTLIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERSHAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, networktopology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentionaland coincidental.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnershiprelationship between Cisco and any other company. (1110R)

© 2017 Cisco Systems, Inc. All rights reserved.

Cisco CloudCenter Documentation

Cisco CloudCenter Release Notes 1

Cisco CloudCenter 4.6.0 Release NotesRelease DateArchitectureCloudsApplications and ServicesAdministration and GovernanceSecurityDeprecatedCCM UIAPIDocumentationKnown IssuesResolved Issues

Release DateFirst Published: October 1, 2016 

: March 23, 2017 Last Modified

ArchitectureInstallers:

The installer: Package StoreIs 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:Networking Requirements Manual Installation

PostgreSQL Database:CloudCenter 4.6.0 uses  database instead of MySQL.PostgreSQLInstaller and appliance installation and configuration procedures for the PostgreSQL database is similar to the MySQLprocedures 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 replicationmode.In Non-HA mode, the database may be installed with CCM or as a standalone server. To have  installed in aPostgreSQLstandalone VM, you must open Port 5432 to the CCM. See for additional context.Manual Installation

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 setupin master-master mode.See for additional context.Manual Installation

Upgrade to CloudCenter 4.6.0:Non-HA Mode:

1. CCM-Database Upgrade2. CCO Upgrade3. AMQP Upgrade4. Health Monitor Upgrade

HA Mode:CCM-DB Upgrade in HA ModeCCO Upgrade in HA Mode

CloudsVMware: IPAM Naming Callout – Ability to configure the following features

The to identify callouts.Instance Naming Strategy The at the cloud region level.Instance IPAM StrategySpecify the name of the Customization Spec (already created on the VMware vSphere console), in the IPAM callout script.See for additional context.VM Name Config

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.

Cisco CloudCenter Documentation

Cisco CloudCenter Release Notes 2

The cloud region setting validates the region – earlier releases did not valid region settings.See > for additional context.Configure Cloud(s) Configure an OpenStack Cloud

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

Applications and ServicesAvailability Sets and Zones

Virtual machines launched as part of a cluster can be evenly spread across multiple Availability Zones (OpenStack, AWS) orAvailability 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 for additional context.Availability Sets and Zones

Containerize OOB Service: If your worker image has the Docker engine installed, some out-of-box (OOB) CloudCenter services will be run as containersinside the Application VM (worker): Apache2, Memcached, MongoDB, MySQL, Nginx, and Tomcat6/7.See for additional context.Dedicated Docker Registry InstallationSee for a complete list of OOB services.Services

Passing information from external services:The CloudCenter external service accepts , , and as input parameters.ipAddress hostName environmentSee > for additional context.External Service Passing Information from External Services

Administration and GovernanceExtensions:

The is available as a standalone extension on the CloudCenter platform and provides increased ease when  policy modelAPICcreating 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

for additional context.IntegrationYou can then use to configure CloudCenter resources at the Deployment Environment level and Application ProfileExtensionslevel. See for additional context.ExtensionsConfigure 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 deploymentsettings for each deployment environment.Ability to lock deployment environment defaults so to ensure that defaults are not changed by end users during the deploymentprocess.Flexibility to define deployment environment default configurations, but not lock them, so end users can select the default valueat 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 tothe 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 toCloudCenter 4.6.0, you must manually select your default instance again.See for additional context.Deployment Environment DefaultsIf using the API, you have the added advantage of completing the forms associated with the Submit Job (v2) New Deploymentworkflow and retrieving the corresponding JSON request body for use with the API(s). See the API section below for API-specificdetails.

Reports: The new  aggregates the cloud cost by Tenant or by Cloud Region. Each Tenant or Cloud Region isUsage Summary Reportaggregated as a group as well as individually when you click the dropdown arrow for eachThe provides usage information for your tenant down to each sub-tenant level. Some information from thisUsage Details Reportreport is now available in the to ensure that the CloudCenter platform displays related information in theUsage Summary Reportsame place.The and the are redesigned to enhance usability andManaged VM Inventory Report Unmanaged VM Inventory Reportperformance.The section identifies common filters and functions provided in the section.Reports Overview All ReportsThe remaining reports continue to provide the same information as earlier releases with the new UI updates.The :Report Management APIs

Have a new JSON format and standardized field names. For example, was renamed to , wavendorId tenantId cloudTypes changed to , and so forth.regionNameThe pagination information is only provided for list data in the details section.Filter details are simplified. The UI column name metadata and unused fields are dropped in the v2 version.See the API section below for API-specific details.

SecurityThe Tomcat setting in CloudCenter appliances had a short Session ID of 32 characters. Effective CloudCenter 4.6.0, the Tomcat Session ID

Cisco CloudCenter Documentation

Cisco CloudCenter Release Notes 3

settings for CloudCenter appliances have a length of 256 characters. This setting is also changed in the new installation files. Existingdeployments will continue to have the shorter Session ID.

DeprecatedThe following features are deprecated effective CloudCenter 4.6:

The  (only available in CloudCenter 4.5 and earlier releases) option is now deprecated.Manage VM InventoryThe managed inventory option is now provided in the  and provides details based on billing andManaged VM Inventory Reportcost-related database views.The non-managed inventory option no longer uses the deployment environment as the source. Instead, it relies on cloud accountand cloud region details. See for additional context. This change was made to ensure thatView Non-Managed Cloud Detailsusers who are further down the tenant hierarchy do not have the ability to view VMs for which they do not have managepermissions.

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:

BracketCisco Cloud Service (CSS)HPCloudNCloudStackAmazon EC2 Classic

These references are removed from the CloudCenter 4.6 documentation.

CCM UINew CCM UI Enhancements:

New Dashboard: The Dashboard now boasts a new Summary dashlet that displays resource information based on the ComputeCost spending, Run Time, and the Running VMs inventory. Administrators can choose to see the usage and cost summary forthe entire tenant hierarchy. The popular dashlets continue to be available in the CloudCenter 4.6.0 Dashboard along with a fewnew dashlets. See for additional context.The DashboardDeployment Environment Usability: The Deployment Environment management and Job Submission process have beencompletely redesigned to enhance usability.New UI Behavior: The CloudCenter UI provides real time feedback on errors that you encounter while configuring a deploymentenvironment or deploying a new job. See for additional context. UI Behavior

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

New APIs:v1 APIs:

ACI Extensions:Create ExtensionView ExtensionsUpdate ExtensionDelete Extension

Report Management:Create Report FilterView Report FiltersUpdate Report FilterDelete Report Filter

Inventory Management:View Non-Managed Cloud Details

v2 APIs:Job Management:

Submit Job (v2)Submit BenchmarkView JobsView Job DetailsView Benchmark DetailsUpdate JobDelete Job

Report Management:View Usage Summary Report

Cisco CloudCenter Documentation

Cisco CloudCenter Release Notes 4

View Usage Details ReportView Managed VM Inventory ReportView Unmanaged VM Inventory Report

Cloud Instance Management APIsView Cloud Instances

Updated v1 APIs:Perform User Actions (MANAGE_CLOUDS payload)Get Job Details ( query attribute)excludeTerminatedNodesView Tenants ( query attribute and the response attribute)includeDeleted deleted

Additional Notes:The list is updated with the additional error messages.API Error Codes

DocumentationFeature 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 .http://docs.cloudcenter.cisco.com

Documentation Versions: From use the Documentation Version dropdown on the left pane to selecthttp://docs.cloudcenter.cisco.com,the documentation version that applies to your CloudCenter release. By default, the latest documentation version is displayed in thehome page.Search Results: All documentation search results display all available releases from each CloudCenter version. Select the version ofchoice. The home page  field (highlighted in the following image) restricts the search results to justRestrict Your Documentation Searchthat release.

For example, the home page for CloudCenter 4.6 is  – type your search text in the Cisco CloudCenter Documentation, Version 4.6 Searc field.h Documentation

v2 APIs Documentation: This is the first time that the CloudCenter platform offers a new version of older APIs, where available. If a newversion is available, you will see the option to review the information for each version under a separate section. For Example:

Job Management APIs (will now have two new sections within):v1 Job Management

Submit JobList Jobs...

v2 Job ManagementSubmit Job (v2)View Jobs...

Known IssuesCloudCenter 4.6.0 has the following known issues:

The button is currently not enabled for restricted users in a deployment environment. Consequently, restricted users cannot add orDone

Cisco CloudCenter Documentation

Cisco CloudCenter Release Notes 5

remove the cloud and accounts. Restricted users can add new clouds or cloud accounts, but will not be able to remove those regions orcloud accounts if the deployment environment owner does not have access to those resources.If using Internet Explorer 10 to access the CCM UI and if you do not have Windows admin access for the browser, then you cannot viewor use the CCM UI. To view and perform CCM UI-based tasks using Internet Explorer 10, you must log in using Windows admincredentials.If you have launched an application that uses the Elastic Load Balancer (ELB) service in a release prior to CloudCenter 4.6.0, be awarethat you cannot suspend or resume this service in CloudCenter 4.6.0. You can workaround this issue by backing up yourapplication/service information and terminating that application before upgrading to CloudCenter 4.6.0. Your can then relaunch thisapplication after the upgrade.The billing task runs only every calendar hour. As a result, even if a job is deploys successfully, you may see the initial cost items for thisjob only the hourly billing task has run at least once. It may be up to an hour before costs for your running job are displayed in after TheDashboard and all .All ReportsWhen you deploy an application to a SoftLayer cloud, the application deploys successfully. However, when you try to power off or rebootthe VM from the page, the task does not complete. These operations continue to work from the JobManaged VM Inventory Report  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 thisscript may not execute as designed. To work around this issue, verify that any script that resides inside the service bundle contains avalid extension (based on the script) when using it in a Windows environment.The data that is displayed in response to a 30-Day time period request only displays data from the 1st of the month, not forAll Reportsthe previous 30 days. To work around this issue, use the date option and provide the begin and end date for the required period.RangeThe Path parameter defined in an application profile (global parameter or tier-level custom parameter) does not display as designed onthe Deployments page.The Suspend operation is not listed in the responses for the v1 API and the v2 API.Get Job Details View Job DetailsWhen you map a VM Template to an image, the deployment may fail. To workaround this issue, convert the template to a VM, take asnapshot, and use the Linked Clone mode. See  for additional context.VMware Configurations

Resolved IssuesThe 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 beavailable. For example, NewStatus. In addition, status seems to have taken the expected value of NewStatus.

: While this issue was addressed by renaming the attributes and verifying that the right data displayed for each statusResolutionattribute, CloudCenter 4.6.0 also introduces a new attribute for the older state, called , which displays the status of the joboldStatusbefore 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 ispopulated from one tier to the other. However, during a scaling event (scale up/down) the information is not populated from one tier to thenext.

: CloudCenter 4.6.1 includes a fix to ensure that the information is accurately propagated.ResolutionIssue:  If you edit a CentOS service and save it (with or without changes), a deployment using this service may remain in an incomplete

that triggers a download of a bundle file called CentOS.zip during the deployment. This file does notstate. This issue is caused by a flagexist and is not required and causes the deployment to remain in an incomplete state.   

: CloudCenter 4.6.0 provides a fix for this issue and the column for this flag has been removed from the database.ResolutionIssue: When you update the instance type, the instance price is rounded up/down to 2 decimals. For example, if a user saves a cost of0.0512 via UI, the UI displays this cost as 0.05 instead of 0.0512 even though the database stores this value as 0.0512. 

: This issue is fixed and the UI now preserves the value up to 9 digits after the decimal.  Resolution: , if you added attributes to a profile and you used the  Issue Prior to CloudCenter 4.6 during an application deployment password with

(see ) you may see the  error. confirmation type Using Parameters , Password cannot be empty and has to match the confirm password The error is caused by an improvement in the CloudCenter 4.6 UI which now enforces the value in the :Resolution password with type. You can now pursue one of two paths:confirmation

Re-type the password in the Confirm Password field and continue deploying the application. Cancel the deployment, edit and save the profile, and then deploy the application.

:Issue New lines are being not added automatically in action email templates. This generally happens when you use macroPolicysubstitutions as the text continues to be interpreted as HTML. As a workaround, insert where required.<br />    

: CloudCenter 4.6.0 includes the software change that was made to address this issue. New lines are now addedResolutionautomatically to the action email templates.Policy