Cisco CloudCenter 220.127.116.11 Release Notes
First Published: June 17, 2020
August 18, 2020: Updated the Documentation section to include modified pages.
CloudCenter 18.104.22.168 is only available as an upgrade for existing customers from CloudCenter 22.214.171.124, CloudCenter 126.96.36.199, CloudCenter 188.8.131.52, CloudCenter 184.108.40.206, CloudCenter 220.127.116.11, or CloudCenter 18.104.22.168. Contact the CloudCenter Support team for additional details.
You must be at a minimum version of CloudCenter 22.214.171.124 to upgrade to CloudCenter 126.96.36.199.
Effective CloudCenter 188.8.131.52 and later, the CloudCenter upgrade process downloads packages from a CentOS base and the extras repository via the internet. If you do not have internet connectivity, they must setup a local CentOS mirror and configure the CloudCenter components (CCM, CCO etc) to use the local mirror.
See the Upgrade Overview page and the following table for additional details.
|Upgrading CentOS CloudCenter Components to CloudCenter 184.108.40.206|
|Appliance Jar Files?||Notes|
|220.127.116.11 or earlier||Yes||Yes (for CCO only)||Yes||Yes|
|18.104.22.168||No||Yes (for CCO only)||Yes||Yes||You should have already run os_upgrade when you upgraded to 22.214.171.124|
|126.96.36.199 or later||No||No||No||Yes||Applicable to CloudCenter 188.8.131.52 or later|
|Upgrading Non-CentOS CloudCenter Components (RHEL) to CloudCenter 184.108.40.206|
|220.127.116.11 or earlier||No||No||No||Yes|
1 The os_upgrade command is not required when upgrading the REPO or Bundle store.
Applications and Services
The terminate behavior for non-VM tiers and VM tiers is different when compared to CloudCenter 18.104.22.168 if you have set the cliqrIgnoreAppFailure flag to true.
You must add the following variable to the /etc/sysconfig/gateway.conf file:
When set to false, then at the time of deployment termination the STOP script is implemented using a top-down approach – the top tier script is called followed by the dependent tier.
When set to true (default) the STOP scripts for all the tiers are called in parallel.
Administration and Governance
End of Life Notices
The worker1 and worker_full modes are not supported effective CloudCenter 22.214.171.124. The worker_basic mode is the only supported mode when installing the worker.
The following documentation changes were implemented in Workload Manager
CCO (added a note on os_upgrade verification check)
Install Worker on a Linux Image (updated support for worker modes)
CCO Troubleshooting (added the section)
Region-Level Cloud Settings (added the Max Socket details)
Upgrade Overview (updated to ensure flow and accuracy for upgrades from 126.96.36.199 to 188.8.131.52)
Upgrade CCO (updated to ensure flow accuracy for MongoDB steps in the section)
Virtual Appliances (updated for technical accuracy)
Worker (Conditional) > FAQs (added Question 11 for authorized key handling details)
The following issue was identified in Workload Manager 184.108.40.206:
At any time the number of users accessing a Job Details page should not exceed 30 users. Additional job details pages may not load completely if the number of users accessing Job Detail resources exceeds this number.
The following issues were resolved/addressed in CloudCenter 220.127.116.11:
CSCvu55475: A customer found the SDRS automation level for some VMs (VMs with multiple disks) had been disabled after attaching a volume from the CCM – this resulted in an enhancement request to avoid changing the SDRS automation level for VMs.
Resolution: CloudCenter 18.104.22.168 includes a fix to ensure that the SDRS automation level of the VM is preserved when an Attach Volume action is performed.
CSCvu51239: When creating a worker for RHEL6, Ubuntu 16, or CentOS 7 using the 22.214.171.124 worker installer (worker-installer.bin, worker_basic mode), the gcc / nfs / bash / openssl / dialog / lsof packages are not installed with the worker.
Resolution: CloudCenter 126.96.36.199 includes a fix to ensure that the gcc / nfs / bash / openssl / dialog / lsof packages are not installed with the worker installer and that rhel5 / centos5 / ubuntu10 / suse10 image mappings are not listed in the cloud region.
CSCvt83081: CloudCenter 4.9 does not assign proper tags to VM deployments that run on VMware 6.x.
Resolution: CloudCenter 188.8.131.52 includes a fix to ensure that tags are assigned as designed to VM deployments that run on VMware 6.x.
- No labels