Cisco CloudCenter 126.96.36.199 Release Notes
CloudCenter 188.8.131.52 – November 20, 2017
Updated on August 1, 2018: Added details on the Upgrade Path.
CloudCenter 184.108.40.206 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 220.127.116.11 from CloudCenter 4.6.0 and later releases.
To upgrade to CloudCenter 18.104.22.168, see Upgrade Overview for additional context.
The recommended upgrade path if you are using CloudCenter 22.214.171.124 is to upgrade to CloudCenter.
SysPrep: You can now skip running sysprep on the Windows platform, for VMware (vSphere) cloud. See Callout Scripts for additional context.
Batch Node Launch: You can now launch VMs batch-wise on OpenStack clouds. This option reduces the number of API calls made to OpenStack. See Region-Level Cloud Settings for additional context.
Configuration Drive: You can now use the config drive option while launching VMs on OpenStack clouds. See Region-Level Cloud Settings for additional context.
Delete Boot Diagnostic Logs on VM Termination:
You can now configure this setting in the region-level cloud settings – if you prefer to delete the diagnostic logs when a VM or an application is terminated
See Region-Level Cloud Settings > Edit Cloud Settings popup to delete the diagnostic logs.
See Configure an Azure RM Cloud for additional context.
Applications and Services
Minimum Number of Nodes: Sometimes, a few VMs in a cluster of VMs may not launch fully and error out. This resulted in a complete deployment failure. Starting from CloudCenter 126.96.36.199, the deployment continues as long as the Minimum Number of Nodes specified for an application launches successfully.
Node Ready Timeout: You can now specify a timeout for initialization scripts that run on VMs through an application parameter. The VM gets terminated if the initialization scripts do not complete within the specified time. This setting prevents VMs from running indefinitely if the initialization scripts get stuck.
Bootstrap Timeout: You can configure the timeout for launched VMs to become available through an application parameter. The bootstrap timeout window is enhanced to ensure that VMs become fully operational within this window.
See Deployment and VM States > Orchestration Lifecycle Threshold Settings for additional context.
Administration and Governance
The System Tags table includes an additional Priority column that is only visible when Governance mode is ON. Use this column to change the priority for system tags.
See System Tags > Prioritizing System Tags for additional context.
End of Life Notices
Browser Compatibility: Cisco supports the two latest versions of each browser. See Browser Compatibility for a list of compatible browsers.
IPAM – VMware for Windows
If the IPAM parameters do not require SysPrep, then the CloudCenter platform does not start the SysPrep operation for the corresponding operation.
See Callout Scripts > Alternate Windows Guest OS Customization for additional context.
, v1.5 is available for the following ServiceNow releases (added to CloudCenter documentation on October 10, 2017):
See Release Notes for v1.5 for additional context.
Instance IPAM Strategy
All changes listed in the CloudCenter 188.8.131.52 release notes are repeated here for inclusion as those changes are also ported to the 4.8.1 train.
This section lists the documentation changes implemented in184.108.40.206
CloudCenter 220.127.116.11 Changes: See the links provided in this section for additional context on documentation for this release.
The following bullets identify the documentation changes implemented during the CloudCenter 18.104.22.168 time frame:
CloudCenter 22.214.171.124 has the following known issues:
When you submit several jobs concurrently, a few may fail with a gateway timeout error.
When a new user submits multiple jobs concurrently, some of them fail with a database constraint violated exception. Subsequent jobs submission by the same user continue to work as designed.
The following issues were resolved/addressed in CloudCenter 126.96.36.199:
Issue: The system encountered a race condition when multiple jobs were submitted and the security group creation failed on AWS.
Resolution: CloudCenter 188.8.131.52 provides a fix to ensure that initial job submission is verified and the security groups are reused in these cases.
Issue: The Job Details page makes too many calls to vCenter.
Resolution: If the VMs launched for a job have a single NIC, then additional calls will no longer be made to the CCO from the Job Details page.
Issue: The Dashboard was slow to load in cases where the deployments contain a large number of VMs.
Resolution: CloudCenter 184.108.40.206 includes a fix to enhance the underlying query and the Dashboard loads as designed.
Issue: The job details page was slow to load.
Resolution: CloudCenter 220.127.116.11 includes performance enhancements to the underlying APIs to eliminate unnecessary delay when loading the Job details page.
Issue: Job submission fails with an internal server error for N-tier applications that have a tier mapped to an external service.
Azure diagnostic extension failed to be provisioned on Windows VMs
The VM's userenv file in some VMware deployments did not contain the IP addresses for all tiers.
- No labels