Workload Manager 5.1.4 Release Notes
First Published: February 27, 2020
July 2, 2020: Updated the Documentation section to include the changed pages.
CloudCenter Suite 5.1.4 is available as an upgrade for existing customers from Workload Manager 5.1.0, Workload Manager 5.1.1, Workload Manager 5.1.2 or Workload Manager 5.1.3.
Backup and Restore
Workload Manager: You can upgrade to Workload Manager 5.1.4 via the Suite Admin UI. See Update Module for additional details.
If you upgrade the Workload Manager, you must also upgrade the Cost Optimizer and vice versa as both modules use shared components.
The recommended upgrade path is from CloudCenter Suite 5.0.3 to CloudCenter Suite 5.1.0. You can then upgrade Workload Manager to Workload Manager 5.1.1, Workload Manager 5.1.2, or Workload Manager 5.1.3 or directly to Workload Manager 5.1.4 as identified in the Update Module section.
There are no architecture changes for Workload Manager 5.1.4.
Workload Manager 5.1.4 supports RedHat Linux 8. See OOB Logical Images for an updated list.
Services, Applications, and Deployments
Administration and Governance
Workload Manager 5.1.4 supports deployment of applications to networks running on Cisco ACI/AVE switch.
End of Life Notices
The following sections were updated for technical accuracy:
Cloud Remote (statement of redundancy support)
OOB Logical Images (added support for RHEL8)
Pre-Defined Parameters (added CliqrTier_$tierName_$networkName environment variable to the N-tier list)
Benchmark an Application (added a tip on the time taken to refresh)
ServiceNow Extensions (added support for ntegration – Cisco CloudCenter Suite 4.1.0 and Orlando)
Create a Deployment Environment (addressed clustered DS management)
Configure a Kubernetes Cloud (added a - to the kubectl create clusterrolebinding command)
Cloud Overview (updated for technical accuracy)
Guidance for Callout Scripts (updated details for the hwClockUTC parameter)
CCM Calls 5.1 (updated the Swagger file to reflect APIs for all releases up to CloudCenter Suite 5.1.4)
Cloud Setup Calls 5.1 (updated the Swagger file to reflect APIs for all releases up to CloudCenter Suite 5.1.4)
Policy Management (deleted outdated screenshots)
Arcus Server (updated XSLT format, JSON data endpoint, and validation command)
The following issues were resolved in Workload Manager 5.1.4:
CSCvt21860: When deploying application that have multiple Network Interface Cards (NIC) attached to a tier, the Job Details/Virtual Machines pages do not display their hostnames.
Resolution: Workload Manager 5.1.4 includes a fix that displays the hostnames for the VMs that have multiple NICs attached to them.
CSCvt21832: For deployment of applications having tiers with Multiple NICs, there is no way to get all the IPs assigned to a network in the service scripts.
Resolution: Workload Manager 5.1.4 includes a new environment variable, CliqrTier_$tierName_$networkName, which has a comma separated list of IP addresses assigned to a network in a tier. The network name needs to have only alpha numeric characters and underscores.
CSCvs66683: Attach Volume operations fail for OpenStack deployments, when OpenStack is configured with Volume types.
Resolution: Workload Manager 5.1.4 includes an additional configuration in the Cloud Region settings to use storage type as volume type. When enabled, storage types selected are used for configuring appropriate volume types on OpenStack.
CSCvs69834: Terminate protection cannot be turned off on some deployments which prevents the deployments from being terminated.Terminate action items are missing on the right-click menu.
Resolution: : Workload Manager 5.1.4 includes a fix to address this issue and terminate protection can be disabled as needed.
CSCvs66084: When a “Terminate And Hide” operation is tried on a failed deployment, it gets stuck in Cancelling state.
Resolution: Workload Manager 5.1.4 includes a fix to address this issue and the deployment that is in an Error state can be terminated and hidden.
CSCvs13243: Workload Manager Benchmarking results are always 0 cost in Benchmark charts.
Resolution: Benchmark costs are calculated based on the Job cost and Node cost and are updated hourly. Once the benchmark completes, it is essential to wait for at least 1 hour before checking the benchmark results.
- No labels