Cisco CloudCenter 126.96.36.199 Release Notes
Release Date: May 29, 2018
May 31, 2018: Addressed screenshots display issue as identified in the Documentation section. Additionally, most pages continue to be updated as we work on our accessibility requirements.
June 6, 2018: Addressed the REPO/bundle component upgrade order and conditions and policy time zone details.
June 28, 2018: Added Docker service explicit re(start) as a known issue.
August 1, 2018: Added details on the Upgrade Path.
August 3, 2018: Added details on the security hardening requirements for CURL/WGET.
- February 25, 2019: Clarified the process when configuring CCM on a FIPS System.
CloudCenter 188.8.131.52 is available as installer for ALL components for all supported clouds. Contact the CloudCenter Support team for additional details.
To upgrade to CloudCenter 184.108.40.206, see Upgrade Overview for additional context.
Upgrading to CloudCenter 220.127.116.11 in HA Mode
When upgrading CCOs in HA mode, you MUST stop all the CCOs and then start them again. See Upgrade CCO for additional context.
The recommended upgrade path if you are using CloudCenter 18.104.22.168 is to upgrade to CloudCenter 4.9.1 Release Notes.
Applications and Services
Deleting Additional Volumes at Deployment Time:
The number of additional volumes that was initially configured by the application owner can now be deleted by end users, if not required, at deployment time.
To delete the unwanted volume(s) click the delete icon next to that additional volume.
See Application Tier Properties > General Settings for configuring additional volumes
See Multiple Volumes for configuring volume attributes.
See Deploying an Application for deployment details.
Special characters in the usrenv file:
In earlier releases, users were able to use special characters in the usrenv file. However, sourcing files with these special characters caused issues in scripts that used the usrenv file.
Effective CloudCenter 22.214.171.124, special characters like pipe or double quotes " | " are configured with escape sequences that use single quotes instead of double quotes. This is a change!
You can successfully source userenv files that contain these special characters.
See Deployment Lifecycle Scripts for additional script sourcing details.
Administration and Governance
Security – CURL AND WGET UTILITIES REMOVED!
Due to security hardening requirements, the following changes apply to application VMs (Worker):
THE CURL AND WGET UTILITIES ARE NO LONGER AUTOMATICALLY INSTALLED IN APPLICATION VMs DEPLOYED BY THE CLOUDCENTER PLATFORM.
If scripts in your application VMs require curl and/or wget, please install these utilities using your OS-specific package manager (apt-get/yum) in your application VM scripts.
See CURL and WGET Utilities for additional details.
This is a change!
End of Life Notices
The Network menu item is removed from the CCM Wizard as it was not used for any configuration. See CCM Wizard for additional context.
Browser Compatibility: Cisco supports the two latest versions of each browser. See Browser Compatibility for a list of compatible browsers.
The Upload File API was introduced in CloudCenter 4.8.2 and recently documented as part of the .
The CloudCenter Jenkins plugin requires the Jenkins server to use Jenkins 2.107.2 and Java 8 going forward. See Jenkins for additional context.
For security and compliance reasons, Cisco CloudCenter documentation is accessible on browsers that support the Transport Layer Security (TLS) 1.2 protocol defined in RFC 5246. See your browser documentation for compliance details. In general, the following browser versions are compatible by default when viewing Cisco CloudCenter documentation.
Firefox 27 and higher
Google Chrome 38 and higher
Desktop Safari versions 7 and higher for OS X 10.9 (Mavericks) and higher
This section lists the documentation changes implemented in.
Locate Log Files (added pg_log file details)
Configure CCM Wizard Properties (updated Custom Certificate Menu entry)
Certificate Authentication (updated Custom Certificate Menu entry)
CCM_LB (added clarity the last step being optional)
PostgreSQL Troubleshooting (added a few more tips)
Sample AzureRM Appliance Setup (added a note to indicate that you do not need to explicitly run the validation script for this procedure)
Upgrade Overview (added CloudCenter 4.8.1, 4.8.0, and 4.7.3 to the table)
Container Clouds (added a note about additional steps not being required to use AMQP in a container environment and clarification on relative paths, clarified that Kubernetes is our only container cloud)
Configure a Kubernetes Cloud (added command details to retrieve the API Endpoint URL and the Account Token)
Container Service (added an example for Kubernetes-specific deployment parameters)
CloudCenter-Defined Parameters (moved the Kubernetes-specific deployment parameters to this page)
Service Lifecycle Actions (co-related service type with corresponding actions)
Tenant Information (deleted reference to tenant billing and updated firewall settings information)
Sub-Tenants (deleted reference to tenant billing)
CloudCenter Cost and Fees (deleted payment details)
Financial Overview (updated plan type and fees details to exclude payment details)
Configure Cloud Storage (deleted reference to tenant billing)
Finance (deleted mention of seed credit)
Terminate Protection (included reference to the deploy form)
Deploying an Application (added additional steps)
SSH Options (updated overview section)
Metadata for Custom Properties (deleted pointer for microsegmentation)
Multiple Volumes (updated supported public cloud type details)
Deployment (Job) Details (added information on the Associate Tags field)
System Tags (added the Adding System Tags as Annotations section)
Cross-Region Disaster Recovery (updated public/private IP references for the database from Primary to Master and Secondary to Slave)
End of Support Notices (added the EOL and EOS timeline for CloudCenter 4.9)
Application Using Imported Profile (changed third-party format to applications using the CloudCenter format)
Import Application Profiles (updated the CURL request format to multipart/form-data as it requires a file upload)
Kubernetes Troubleshooting (added a new page and included solutions around this setup)
VM Management (added VMware Tools dependency to the overview section)
Docker (addressed screenshots display issue – May 31, 2018)
Upgrade Overview (addressed the component upgrade order – June 6, 2018)
REPO Upgrade (Conditional) (addressed the component upgrade condition – June 6, 2018)
Bundle Store Upgrade (Conditional) (addressed the component upgrade condition – June 6, 2018)
Policy Management (clarified the time zone used when a suspension policy is applied – June 6, 2018)
CCO (Required) (updated the agent bundle details in the wizard description table – June 6, 2018)
Services (added a note on security hardening requirements – August 3, 2018)
Updated numerous pages to ensure that the screenshots reflect the latest UI changes
Ongoing changes to multiple pages to address accessibility requirements in documentation – effective May 31, 2018
Additional Documentation Updates:
The CloudCenter 4.6 has reached End of Life (EOL) as of April 1, 2018 and CloudCenter 4.7 will reach EOL on July 6, 2018. See End of Life Notices for additional context.
CloudCenter 4.5 has reached End of Support as of October 23, 2017 and this section is now archived.
CloudCenter 126.96.36.199 has the following known issues:
If you deploy an Azure Pack VM with more than one additional volume, the CloudCenter platform only attaches one disk to the VM using the region-level data disk information that was configured with the default size at the time of data disk creation. All other disk creation requests will be ignored. This limitation applies to deployments that use either Generation 1 or Generation 2 images.
A deployment name that contains more than 63 characters fails to deploy – This is due to a Kubernetes limitation that does not allow metadata values to be longer than 63 characters. As a workaround, use deployment names that are less than 50 characters as the CloudCenter platform requires the additional 13 characters to ensure a unique cluster name.
You may find the following warning message in the Kubernetes CCO logs – you can safely ignore this message as it does not impact product functionality.
The Docker (docker) service must be explicitly (re)started after the CCO sever is (re)started. See Certificate Authentication > Dedicated Components for process details (added on June 28, 2018).
The following issues were resolved/addressed in CloudCenter 188.8.131.52:
CSCvf86406: An enhancement request to allow a value of 0GB to be specified for volume size during deployment.
Resolution: See the Applications and Services > Deleting Additional Volumes at Deployment Time section for additional details.
CSCvf98414: The Instance Type descriptions displayed during a deployment and VM details currently display the size of the additional storage that is configured, but not the size of the root disk.
Resolution: The additional storage concept is applicable to AWS, Azure RM, Azure Stack, Alibaba and OpenStack while the other clouds would not display this field. The storage type description is fixed to reflect the correct type. See Manage Instance Types > Overview for additional context.
CSCvi59400: In the job details screen of a child job, the End Time column in the nodes table is mislabeled.
Resolution: CloudCenter 184.108.40.206 includes a fix to reflect the correct column name.
CSCvi74806: For VMware deployments, regardless of which datastore is selected for root storage, the additional storage is always placed on the first available datastore.
Resolution: CloudCenter 220.127.116.11 includes a fix to ensure that the right datastore and host are used based on whether DRS is enabled for Datastore.
CSCvj10970: The Application Profile > Deploy page loads slowly in a HA environment with around 2000 users.
Resolution: CloudCenter 18.104.22.168 includes a fix to address this issue and the Deploy page in the same HA environment loads faster.
CSCvj12646: If any ESXi host is not reachable or has an issue during a scale up, vCenter reports an error and the scale up job in CloudCenter remains stuck in the Scaling state.
Resolution: CloudCenter 22.214.171.124 includes a fix to ensure that when a VM creation fails on the cloud during scaling operation, the job status is set back to Deployed and all VM(s) launched during scaling are deleted.
CSCvj12865: Inconsistent SSH connectivity was encountered by a customer in VMs that were deployed in an AWS HA environment.
Resolution: This issue was caused by the Load Balancer IP address not being updated in the CCM after the upgrade. The High Availability Best Practices > Load Balancer Requirements section specifies this requirement:
CSCvj23102: VMware deployments fail with IPAM in Full Clone mode when the template being cloned does not have additional NICs.
Resolution: CloudCenter 126.96.36.199 includes a fix for this issue and deployments function as designed.
CSCvj27701: When using CloudCenter 188.8.131.52, an application deployment using IPAM callouts fails if the network name contained special characters.
Resolution: CloudCenter 184.108.40.206 includes a fix to accept special characters in the network name.
CSCvj29227: When a user has locked the cloud settings (in the Default Tier Cloud settings of the Deployment environment) to prevent it from being viewed by end users, it also prevented other users' ability to change the root disk size at deployment time and blocked the deployment from being submitted.
Resolution: CloudCenter 220.127.116.11 includes a fix to allow the root disk size to be changed by end users even if the owner locks the cloud settings. This allows end users to proceed with the deployment submission.
CSCvj29333: Some Azure Pack deployments fail if the application contains additional volumes and uses Generation 2 images. The failed VMs are not cleaned up.
Resolution: While this was a known issue in CloudCenter 4.9.0, it is also a current limitation for Azure Pack configurations – At the region level, you can configure only one data disk. If you deploy a VM with more than one additional volume, only one disk will be attached to the VM with the data disk information available at region level with the default size specified at the time of data disk creation. All other disk creation requests are ignored. This limitation applies to deployments that use either Generation 1 or Generation 2 images. CloudCenter 18.104.22.168 contains a fix to ensure that the failed VMs are cleaned up.
CSCvj70873: Failed to dynamically bootstrap when public internet access is not available.
Resolution: As a side-effect of this fix, wget/curl are no longer installed as part of the application VM bootstrapping process. This might have implications when new deployments might fail if the image being used does not have the wget/curl utilities installed. See the Securities section above for additional context.
CSCvj71503:Unable to deploy in Azure when diagnostics info is not provided in Deploy.
Resolution: CloudCenter 22.214.171.124 contains a fix for this issue and deployments on Azure work as designed.
- No labels