Cisco CloudCenter 220.127.116.11 Release Notes
Release Date: November 13, 2018
November 15: Updated the Documentation section as listed.
CloudCenter 18.104.22.168 is available as installer for ALL components for all supported clouds. Contact the CloudCenter Support team for additional details.
You can only upgrade to CloudCenter 22.214.171.124 from CloudCenter 4.7 and later releases.
To upgrade to CloudCenter 126.96.36.199, see Upgrade Overview.
If you are upgrading your environment to use tagless governance, you must use the latest CloudCenter 188.8.131.52 ccm-response.xml file to upgrade to CloudCenter 184.108.40.206. See Migrate to Tagless Governance for additional context.
When you upgrade the CCM, you will see an additional warning if the ccm-response.xml file is not edited as mentioned in the migration procedure, you can dismiss the warning if this change does not affect your environment.
The recommended upgrade path if you are using CloudCenter 220.127.116.11 is to upgrade to CloudCenter 4.10.0 or later releases.
The Java agent, available in earlier CloudCenter releases, is no longer used in CloudCenter 4.10.0 and later releases. Effectively, CloudCenter 4.10.0 and later does NOT install a Java-based agent for custom images that are created by running the installer on a Base OS image. -
While CloudCenter 4.10.0 included both the new Go agent as well as the old Java agent for application VMs that use dynamic bootstrapping, CloudCenter 18.104.22.168 ONLY includes the new Go agent.
See Golang and Java Version Compatibility for additional details.
Applications and Services
Administration and Governance
End of Life Notices
Effective CloudCenter 22.214.171.124, Cisco is deprecating support for the Java agent. See the Architecture section above for additional details.
The CCM installer installs x-Frames to prevent clickjacking and CSRF attacks. X-frames prevent a SNOW integration from functioning as designed – only for new installations.
If you have already installed the ServiceNow integration using an earlier CloudCenter release and are merely upgrading the CloudCenter platform to 126.96.36.199, the following information does not apply to you as the upgrade process handles the uninstall script.
For new CCM installations, you can uninstall x-frame and proceed with the SNOW integration. To uninstall x-frame, issue the following commands on the CCM server as a root user:
See ServiceNow Extensions for ServiceNow integration details.
The following bullets identify the documentation changes implemented for CloudCenter 188.8.131.52
Upgrade Overview (addressed an upgrade to the Docker image on a CCO server)
Upgrade CCO (addressed an upgrade to the Docker image on a CCO server)
Configure a VMware Cloud (added details on the Global role)
The following issues were resolved/addressed in CloudCenter 184.108.40.206:
CSCvk42321: When attempting to delete a cloud in the Root tenant, the user received an error saying this cloud still has active accounts which had to be cleaned up. Since the sub-tenant is already deleted, there is no way for the admin to clean-up the cloud account and this cloud.
Resolution: CloudCenter 220.127.116.11 includes a fix to delete cloud accounts associated with a tenant when a tenant is deleted. This will unblock the deletion of clouds.
CSCvm22145: The CCM UI web page did not use anti-framing measures.
Resolution: CloudCenter 18.104.22.168 includes a fix to use anti-framing measures to prevent clickjacking and Cross-Site Request Forgery (CSRF) attacks.
CSCvm94645: When using SSO Shibboleth in the CloudCenter platform, it is not possible to configure the forceAuthN parameter.
Resolution: CloudCenter 22.214.171.124 includes an enhancement to allow users to toggle IDP force authentication settings (disabled by default to keep with the Spring SAML default config). To enable forceAuthN, set SAML_FORCEAUTHENTICATION=true in the /etc/sysconfig/mgmtserver.conf file and restart the CCM server.
CSCvn00357: When you model an application deployment, add a password that uses a Parameter with Type and which requires a confirmation, the password parameter is not passed to the IPAM Callout.
Resolution: CloudCenter 126.96.36.199 includes a fix to ensure that all parameters defined while creating an application profile are available in the IPAM Callout scripts.
CSCvn09387: Windows 2012/2016 deployments failed when they contain initialization scripts requiring multiple reboots.
Resolution: CloudCenter 188.8.131.52 includes a fix to ensure that Windows deployments with initialization scripts requiring multiple reboots function as designed.
- No labels