Workload Manager 5.0.0 Release Notes

Release Date

First Published: February 16, 2019

Updated:

  • March 7, 2019: Added to the list of Known Issues: Issue with exporting and importing an application profile that has lifecycle actions associated with it.

  • March 14, 2019: Added CSCvn76106 to the list of Resolved Issues.

  • March 18, 2019: Updated the Documentation section to include a list of pages that were updated.

  • March 19, 2019:

    • Added View Keys to the list of supported APIs.

    • Added the Obtaining Your SSH Private Key page to address the function of obtaining the SSH private key for logging into an application VM for troubleshooting.

  • March 20, 2019: Updated the ServiceNow Extensions page with configuration details.

  • March 28, 2019: Added the Advanced Configuration using Kubernetes ConfigMaps page as a reference for ConfigMaps.

  • March 29, 2019: Updated the Documentation section to include pages that were updated.

  • July 25, 2019: Added the Deprecated section and updated the Documentation section.

  • December 12, 2019: Updated the Documentation section to include pages that were updated.

CloudCenter Rebranding

  • The legacy versions of CloudCenter (Versions 4.10x and earlier) was called the CloudCenter platform.

  • The CloudCenter platform is being rebranded as Workload Manager effective CloudCenter Suite 5.0.0.

  • The term CloudCenter Suite refers to a suite of module consisting of Suite Admin, Workload Manager, Action Orchestrator, and Cost Optimizer.

Installation and Upgrade

  • You must install the Workload Manager module by installing the Workload Manager module after installing the CloudCenter Suite 5.0.0. See Installer Overview for additional details.

  • The Workload Manager has a new, optional component called Cloud Remote, which is installed as a virtual appliance. See Cloud Remote (Conditional) for additional details.

  • The Workload Manager can be upgraded to newer versions from the Suite Admin. See Update Module for additional context.

Architecture

  • The functions of the former CCM, CCO, AMQP, and Log Collector appliances have been moved to pods running in the CloudCenter Suite Kubernetes cluster. See Suite Architecture for details.

  • The local repository appliance and CentOS 6 worker VM appliance have been retained. See Conditional Component Appliance Images for details.

  • A new appliance, Cloud Remote, is added to facilitate connectivity between the CloudCenter Suite cluster and the cloud endpoint and between the CloudCenter Suite cluster and worker VMs.

Clouds

  • The Workload Manager supports the following cloud families:

    • AWS

    • AzureRM

    • Google (GCP)

    • VMware vCenter

    • OpenStack

    • Kubernetes

  • Other cloud families supported in legacy CloudCenter versions (4.10x and earlier) will be reintroduced to CloudCenter Suite over time. 

  • Additionally, you will see a change in behavior for the following functions:

    • Google: While creating a cloud account, the format of the GCP service account private key has changed to JSON from PK12.

    • AWS: IAM support is removed.

    • Azure RM: A new field, Subscription, is added to the Cloud Settings tab of the Deployment Environment and the deployment flow. It is a dropdown populated with the subscription names associated with all accounts associate with the region. Once a subscription name is selected, the associated resource groups for that subscription are displayed for selection. Previously, only the resource groups associated with the subscription ID entered in the Add Cloud Account form were displayed in the deployment environments form and the deploy form.

    • Invoice reports for cloud accounts has moved from the list of cloud account to the Cost Optimizer module.

    • Sync Instance types: The ability to manually sync instance types for public clouds is removed. Public cloud instance types are synced automatically once every 24 hours. See Instance Types Settings.

Services and Applications

  • All callout scripts used for VM naming and IPAM address allocation must generate output of key-value pairs in JSON format.

    • You must update callout scripts developed for previous releases so they can work in CloudCenter Suite 5.0.0.

    • See Guidance for Callout Scripts for additional details.

  • Out-of-Box (OOB) application templates are limited to N-tier application templates only. 

  • Additionally, the following functions are not currently available.

    • Capacity Management (for vCenter and OpenStack deployments)

    • Application Marketplace

    • Deployment export/import

Administration and Governance

  • The following legacy CloudCenter (Versions 4.10x and earlier) functions are now managed by the Suite Admin:

  • Activation profiles are removed – users can be auto-activated based on user groups through the Suite Admin.

  • Contracts are removed and no longer applicable.

  • Assigning plans to users is now optional. Tenants always requires a plan and all users in the tenant inherit that plan. The root tenant includes an unlimited usage plan.

  • The Federation of CloudCenter Manager is not supported in CloudCenter Suite 5.0.0.

Security

UI

  • Localization: Only English will be supported in CloudCenter Suite 5.0.0. Localization support for French, Chinese (simplified), and Japanese will be reintroduced in future releases.

  • User management: Management of users, groups, and tenants, formerly in CloudCenter Legacy 4.10, has been moved to Suite Admin 5.0.

  • The Workload Manager Admin home page has been removed.

  • Browser support: Internet Explorer support is removed. Microsoft Edge is supported. See Browser Compatibility for additional details.

  • Online help: WalkMe online help is turned off in CloudCenter Suite 5.0.0.

API

  • The following API calls, formerly in legacy CloudCenter (Versions 4.10x and earlier), has been moved to the Suite Admin. See Suite Admin API for additional details.

    • User management

    • Group management 

    • Tenant management

  • The ESB Header (message bus option) is not supported.

  • The Workload Manager API endpoint has changed with the addition of the following keywords:

    cloudcenter-ccm-backend/api/

    or, in the cloud-based APIs:

    cloudcenter-cloud-setup/api/

    • An example for a legacy request:

      curl -k -X POST -H "Accept: application/json" -H "Content-Type: application/json" -u cliqradmin:40E45DBE57E35ECB "https://<HOST>:<PORT>/v1/tenants/1/images"
    • An example for a Workload Manager 5.0 request:

      curl -k -X POST -H "Accept: application/json" -H "Content-Type: application/json" -u cliqradmin:40E45DBE57E35ECB "https://<HOST>:<PORT>/cloudcenter-ccm-backend/api/v1/tenants/1/images"
    • An example of a cloud-based Workload Manager 5.0 request:

      curl -k -X POST -H "Accept: application/json" -H "Content-Type: application/json" -u cliqradmin:40E45DBE57E35ECB "https://<HOST>:<PORT>/cloudcenter-cloud-setup/api/v1/tenants/1/clouds/9/regions"
    • See Workload Manager API for additional details.

  • Updated the View Keys API to include support for Workload Manager 5.0.0.

Integrations

  • Workload Manager integration withAction Orchestrator: Action Orchestrator workflows can be designed to be made available in Workload Manager in a fashion similar to custom on-demand and lifecycle actions created in the Workload Manager Actions Library. See Action Orchestrator Workflows in Workload Manager.

  • Workload Manager 5.0.0 is compatible with Integration – Cisco CloudCenter Suite, Version 3.0. See ServiceNow Extensions for details.

Documentation

Deprecated

The NFS and CephFS OOB services are deprecated in this release.

Due to the end-of-life dates from OpenStack and the subsequent lack of support by Workload Manager and Cost Optimizer, OpenStack Icehouse, OpenStack Juno, OpenStack Kilo, OpenStack Liberty are removed from the list of supported Datacenters and Private Clouds.

Known Issues

Workload Manager 5.0.0 has the following known issues:

  • Deployment runtime is sometimes off the mark for application deployment reports – When you create another cloud with the same name after deleting the existing cloud, then the runtime doubles for the job deployed on those clouds. 

  • Some instance types do not have the numOfNICs field listed in the API that populates instance types for some Azure regions. For these instance types, the CloudCenter Suite UI uses a placeholder value of 0 in this field. When you save the instance type for Azure with a 0 value, the configuration fails as every instance type requires NICs as specified in https://docs.microsoft.com/en-us/azure/virtual-machines/windows/sizes-gpu. A workaround for this issue is to use the payload request body of the Update Cloud Instance Type API call to update the numOfNICs field to the required number of NICs

  • In rare situations, an application failed to deploy and issued the exception={com.mongodb.MongoSocketOpenException: Exception opening socket} error after the timeout. To work around this issue, locate and delete the CCO pod using the following commands.

    kubectl get pod -n cisco | grep cco  
    kubectl delete pod $cco_pod -n cisco
  • The add workflow menu selection, available from various dropdown menus for lifecycle actions and from the VM list actions dropdown menu, and the add workflow button on the VM details page, direct users to a broken link. To work around this issue, go directly to the Action Orchestrator workflow canvas and create a new workflow with the Get WM Context action as the first step.

  • When exporting an application profile that has lifecycle actions associated with it, Workload Manager does not distinguish between lifecycle actions created through the Workload Manager Actions Library UI or workflows created in Action Orchestrator that are used as lifecycle actions. As a result, when you import an application profile, in the dialog box for mapping repositories and lifecycle actions, there is no separate grouping of Actions Library lifecycle actions and Action Orchestrator workflows. Therefore the user needs to use caution to ensure that imported workflows are not mapped to Actions Library actions and imported Actions Library actions are not mapped to workflows.

  • In the Workload Manager UI screens for deployment environments, the Deploy form, and deployment details it is possible to specify or change tags that are designed to be written to the VMs that are part of the deployment. Google Cloud does not support tags for VMs; however, the Workload Manager UI does not prevent tags from being specified for Google Cloud deployments and does not display any warning or error message when they are specified.

Resolved Issues

The following issues were resolved/addressed in CloudCenter 5.0.0:

  • CSCvo16391It is not possible to select the EPGs during deployment to VMware when there are more than 250 EPGs configured in the tenant.  
    Resolution: Workload Manager 5.0.0 includes a fix to ensure that an EPG can be selected even if there are more than 250 EPGs configured for a tenant.

  • CSCvo08200: By default, Azure does not delete a NIC even after a VM is deleted. This is an Azure limitation.  
    Resolution: Workload Manager 5.0.0 includes a fix to cleanup all dependent resources when a VM is deleted.

  • CSCvn73159: Due to a RHEL licensing agreement, all RHEL VMs in VMware can only have a certain number of sockets along with any number of cores. Both UCSD and CloudCenter set the number of CPUs by modifying the socket count. The reason for this setting is that the number of sockets can be changed while a VM is powered on, but changing the number of cores can only be done after you power off the VM.
    ResolutionWorkload Manager 5.0.0 includes a new Max Sockets cloud region settings for VMware. During an application deployment:  

    • If set, the Workload Manager ensures that the number of sockets set for the VM does not exceed the number specified in the setting. 

    • If not set, the current behavior of setting the VMs vCPU as the number of sockets will continue. 
    • Even if set, the Workload Manager does not use the Max Sockets setting when resizing the instance type.
  • CSCvn32077: Calling a script from a bundle in the External Lifecycle Actions Settings for a cloud region does not work. Specifying the bundle (ZIP file) for a service of type External Service also does not work. We have many external scripts bundled in ZIP files. 
    Resolution: Workload Manager 5.0.0 includes a fix to ensure that scripts from a bundle can be used in External Lifecycle actions.

  • CSCvk77421: If a user configures the CUSTOM_REPO option, the CloudCenter platform uses this repository for all RHEL packages.

    ResolutionWorkload Manager 5.0.0 includes a new BINARY_REPO environment variable so the URL can be provided to the repository for OS packages. JDK and Docker continue to be fetched from the CUSTOM_REPO, if specified.

  • CSCvj04850: The IPAM Dealloc callout script is not triggered if the deployment is terminated while in progress.

    ResolutionWorkload Manager 5.0.0 includes a fix to ensure that the IPAM Dealloc callout script is triggered as designed.

  • CSCvn76106: Add support for AWS m5d.2xlarge instance types.
    Resolution: Workload Manager 5.0.0 includes a fix to ensure that this instance type is included for AWS GovCloud (US).


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