Workload Manager 5.0.1 Release Notes

Release Date

First Published: April 6, 2019

Updated:

  • May 13, 2019: Updated the Documentation section to include pages that were updated.
  • May 2, 2018: Added Service Libraries integration details
  • July 1, 2019: Updated Datacenters and Private Clouds to include support for OpenStack Queens.

Installation and Upgrade

See the Suite Admin 5.0.1 release notes for additional context.

Architecture

No updates

Clouds

  • AWS – The Cloud Settings tab in the Deployment Environment form and the Deploy form now additionally display Subnet Name along with Subnet ID.
  • AWS - Added a toggle to disable Source/Destination checks for a particular NIC in the Cloud Settings tab in the Deployment Environment form and in the Deploy form.
  • Google Cloud - Added a toggle to enable IP forwarding for a particular NIC in the Cloud Settings tab in the Deployment Environment form and in the Deploy form.
  • vCenter - Added support to ensure that tags that are added or deleted in the Deployment Details page cause the corresponding VM metadata stored in vCenter to be updated.
  • vCenter - Added fields for Linux Max Sockets and Windows Max Sockets in the Cloud Settings section of the Details tab. Workload Manager will always attempt to use the maximum number of sockets during deployment as well as when resizing instance types. In addition, the dialog box for resizing instance types for vCenter VMs has two new toggles which are set to off by default: Stop instance before resizing and Start instance after resizing.

Services and Applications

No updates

Administration and Governance

No updates

Security

No updates

API

No updates

Integrations

Workflows that are necessary to support the integration between Workload Manager and Action Orchestrator are now available in a new public Git repository at https://github.com/cisco/ActionOrchestratorContent. This is described in Workload Manager - Action Orchestrator Integration (replaces Action Orchestrator Workflows in Workload Manager and adds details for ensuring proper operation of the integration).

Workload Manager allows users to create and integrate to various products as part of the orchestration process. These integrations can occur at various points (Day 0, Day 1, or Day 2) during the lifecycle of the application and can include databases, PaaS services, networking solutions, CMDBs, and so forth. See Service Libraries for additional context.

Documentation

The following documentation changes were implemented in Workload Manager 5.0.1:

Known Issues

Workload Manager 5.0.1 has the following known issue:

  • If you deploy a Linux image to an environment without internet access, and the net-tools package is not preinstalled in that image, the deployment will fail.
    Workaround: Install the net-tool package before attempting to deploy the image to an environment without internet access. The steps to do this have been added to Dynamic Bootstrapping and Install Worker on a Linux Image.
  • Upgrade of of the Workload Manager agent in a Linux brownfield VM will fail due to a syntax error in the pre-upgrade script.
    Workaround: Create a custom on demand action in the Actions Library to correct the pre-upgrade script and execute that action on the VM before attempting to perform the upgrade. The steps to do this have been added to Virtual Machine Management > Upgrade Agent.
  • Application profiles with lifecycle workflows which have been exported in Workload Manager 5.0.0 will not import properly in Workload Manager 5.0.1.
    Workaround: Export the application profile again in 
    Workload Manager 5.0.1 before importing it. See Application Tasks > Export for instructions.

Resolved Issues

Workload Manager 5.0.1 has the following resolved issues:

  • CSCvo45767: In Workload Manager 5.0.0, for a vCenter cloud, when assigning a NIC to a vCenter network in the Cloud Settings page of the deployment environment, the dropdown menu will list a maximum of 32 networks even if more than 32 networks are defined in vCenter.
    Resolution: Workload Manager 5.0.1 includes a fix to ensure that all networks defined in vCenter appear in the appropriate dropdown menus in the deployment environment form and the deploy form even when there are more than 32 networks defined in vCenter. 

  • CSCvo79455: For an AzureRM cloud region, in previous releases of CloudCenter Platform and in Workload Manager 5.0.0, in the Regions tab, Cloud Settings, the Exclude these special characters for Windows password  field was missing.
    Resolution: Workload Manager 5.0.1 includes a fix to ensure that for an AzureRM cloud, the Exclude these special characters for Windows password field is present in the Regions tab and works as expected

  • CSCvo77053: In Workload Manager 5.0.0, for all VM-based clouds, worker VMs were failing to receive the no_proxy environment variable during the deploy process.
    Resolution: Workload Manager 5.0.1 includes a fix to ensure that worker VMs receive the no_proxy environment variable during the deploy process. 

  • CSCvo45124: For an AzureRM cloud, in previous releases of CloudCenter Platform and in Workload Manager 5.0.0, when a VM was deployed with a security group assigned, when the VM was deleted by Workload Manager or CloudCenter Platform, the associated security group was not deleted.
    Resolution: Workload Manager 5.0.1 includes a fix to ensure that for an Azure RM cloud, whenever a VM is deployed by Workload Manager with an associated security group, when that VM is terminated by Workload Manager, the associated security group is also deleted.

  • No labels
© 2017-2019 Cisco Systems, Inc. All rights reserved