Workload Manager 5.1.0 Release Notes

Release Date

First Published: August 19, 2019

Updated:

  • September 17, 2019: Added the Documentation section to include a list of pages that were updated.

Installation and Upgrade

  • Workload Manager:

    • You can upgrade to Workload Manager 5.1.0 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 APIs.

    • When upgrading to the latest release of Workload Manager, Workload Manager image mappings are not synced to the latest images mappings published by Workload Manager. The images must be synchronized explicitly using the Sync Image Mappings functionality (See Regions Tab Image Settings Section > Sync Image Mappings section). Explicit synchronizing overrides the existing image mappings with the ones published by Workload Manager.

  • Cloud Remote:

    • Manual installers are available to install Cloud Remote in an IBM Cloud or a vCD cloud.

    • See Cloud Remote (Conditional) for additional details.

Architecture

There are no architecture changes for Workload Manager 5.1.

Clouds

The Workload Manager supports the following cloud families:

  • AWS

  • AzureRM

  • IBM Cloud

  • Google (GCP)

  • VMware

    • vCenter

    • vCloud Director

  • OpenStack

  • Kubernetes

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

  • Kubernetes:

    • Rolling Updates: When you deploy an application with at least one container-based tier, and the deployment is in the deployed state, the Update on-demand action becomes available for that deployment. If you use this action, you will be performing a live update. Your existing replica sets continues to receive traffic until the replica sets with the new images are fully functional. Once that happens, traffic is redirected to the new replica sets. See Container Tier Rolling Updates for additional details.

    • New Updating State: Deployments involving containers have a new UPDATING state for each job as described in Deployment, VM, and Container States. The Deployments > Application Deployments > Click Application page displays this state in the UI. 

  • vCenter:
    • VM Group support. A new option is added to the Deployment Environment > Cloud Settings > Default tier cloud settings section to specify the default VM group for deployment. A similar option exists for each tier in the deploy flow as well.

    • Disable Custom Attribute. A new toggle is added to the Cloud Settings section of vCenter Details tab. Leaving this toggle at the default Off setting causes any tags specified for the VM, including tier level and deployment level tags, to be written to the attributes field in the VM. Setting this toggle to On prevents any tags from being written to the attributes field in the VM.

    • vCenter enhanced peripheral support. Support the following interface types and properties via a resource placement callout script as listed in the Define Resource Placement section:

      • Single Root I/O Virtualization (SR-IOV)

      • PCI passthrough

      • Shared PCI passthrough (vGPU)

      • USB license dongles

      • CPU pinning (CPU affinity)

    • Suspend (Hibernate) VM support. For applications where all tiers are deployed to a vCenter cloud region, an option is added to the Workload Manager deployment suspend function that hibernates the associated VMs instead of causing a full power off / shut down. When such a deployment is later resumed from within Workload Manager, the vCenter Power On function is applied to the associated VMs. This causes the VMs to resume from hibernation instead of being booted up from a cold start. See Deployment, VM, and Container States and Deployment Details Page for additional details.

    • Maximum Number of Snapshots settingIn the VMware Details tab, Cloud Settings section, a setting is added for a maximum number of snapshots that a customer can create. The count is based on the total snapshots currently stored in vCenter and is independent of whether those snapshots were created through Workload Manager or vCenter. The Workload Manager user is prevented from creating more snapshots than the number specified in the region cloud settings. When the snapshot limit is reached, the user needs to manually delete snapshots through vCenter before the user can create more snapshots through Workload Manager. See the Deployment Details Page for additional information.

  • All VM-Based Clouds:

    • Guacamole IP address specification enhancement. In previous versions, Workload Manager only allowed setting a single Guacamole IP address in the Cloud Connectivity section of the Regions/Details tab. WM 5.1 supports two Guacamole IP addresses: one public IP address for launching the SSH/RDP session from a browser, and the other IP address for worker VMs to connect to the Guacamole server. This second IP address could be a private IP address or the same public IP address used by the browser session. See the Configure a Region section in any Configure a Cloud End-to-End section.

  • Cloud Remote Configuration:

    • Copy Encryption Key link. In previous versions of Workload Manager, in the Region Connectivity section of a cloud region, the encryption key for the downloaded connectivity configuration was shown as a string for just a minute after downloading the artifacts.zip file. Instead, in Workload Manager 5.1, the Region Connectivity section shows a Copy Encryption Key link next to the Download Configuration link after downloading the configuration for the first time. See the Download Configuration and Encryption Key section in any Configure a Cloud End-to-End section.

Services, Applications, and Deployments

  • Container-based service and application enhancements. The following changes are made to container-based services and applications that use those services:

    • Docker image initialization override: This option is available in the Topology modeler and allows you to override the entry point defined in the container image.

    • Customize Lifecycle hooks using commands: When defining a container service, you can specify commands for Container post-start and pre-stop lifecycle actions. See Container Service > Lifecycle Hooks for additional details

    • Generate unique service name toggle: In the Network Services section of the applications profile properties panel for container tiers, you will see a new toggle switch to generate a unique service name. See Container Service > Container Tier Properties in an Application Profile for additional details.

    • Single Docker image specification: You can now specify a single URL prefix for the image and the version of the image to be used instead of having multiple images for container service. This is available in the Image section of the service definition form, General Settings section of the applications profile properties panel for container tiers, and the first page of the deploy form. See Docker Service for additional context.

  • Configmap property to override the default message retention period. The number of days that Workload Manager saves messages for the execution of actions against deployments and VMs may be set by the user by editing the cloudcenter-manager configmap. See Adjusting Action Message Purge Frequency for additional context.

  • Configmap property to make a user read-only. Use configmap property to create a read-only user for Workload Manager by adding the user ID to the key read.only.user.ids=. See OOB Groups, Roles, and Permissions Creating a Read-Only User for Workload Manager for additional context.

  • Available Instance Types:

    • For a deployment environment in the instance type subsection, select the instance type(s) that you would like to make available at deploy time. The initial Instance type subsection display shows the All tab highlighted, followed by the Instance Type Filters, and below that, tiles representing instance types that may be made available at deploy time. However, no instance types are initially selected. See Create a Deployment Environment > Available Instance Types for additional details.

    • For existing, private clouds (VMware and OpenStack) created prior to CloudCenter Suite 5.1, a user would need to click Edit Instance Type and save it again without modifying any fields. For new cloud environments (VMware and OpenStack) added as part of CloudCenter Suite 5.1, this step is not needed. See Manage Instance Types > Instance Types Not Visible for additional details.

Administration and Governance

  • Images and Services. Managing Images and Services has moved out of the Admin section. Two new Workload Manager-related groups and their corresponding roles and permissions are added to Workload Manager 5.1 for management of images and services, which is as summarized in the table below.

    OOB GroupAssociated RolesAssociated Permissions
    Policy ManagersWM_POLICY_MANAGERAbility to view, modify and manage Workload Manager policies
    Service ManagersWM_SERVICE_MANAGERAbility to view, modify and manage Workload Manager services
    Image ManagersWM_IMAGE_MANAGERAbility to view, modify and manage Workload Manager logical images

    See OOB Groups, Roles, and Permissions for additional context.

  • Sharing of Images and services. Images and services can be accessed by anyone belonging to the Image managers group and Service Managers group under the same tenant. These can be shared as read-only with their subtenants.

  • ACLs for OOB on-demand actions. In Workload Manager 5.1, tenant admins of the root tenant have the ability to limit which users, groups or subtenants can view and share each of the OOB on-demand actions. By default, all OOB on-demand actions are visible to all users of all tenants. If you are a root tenant administrator, you can enable or disable the Default share option for the out of box actions. Once you click this choice, the menu choices change to two choices: Share, Enable Default Share. See Manage Actions for additional details.

  • Sharing Cloud Accounts/Regions with Tenants. You can now allow or disallow your subtenants to add their own clouds. See Tenant Management > Manage Clouds for additional details.

  • Improved Support for Cloud Remote. Cloud Remote now has additional support as listed in the following bullets:

    • For IBM and vCloud Director cloud environments, you can install the cloud remote binaries on your own VM. See Cloud Remote (Conditional) > Install Cloud Remote on a Custom CentOS7 VM for additional details.

    • For all cloud environments, you can upgrade the Cloud Remote component. See Cloud Remote (Conditional)Upgrade an Existing Cloud Remote Installation for additional details.

    • For all cloud environments, you can enable direct connectivity between CloudCenter Suite and Cloud Remote using a script that is included with the See Cloud Remote (Conditional)Navigating Cloud Remote through Proxy for additional details.

    • The additional scripts used for these procedures are included in the Cloud Remote Bundle. See Conditional Component Appliance Images for additional details.

Policy Management

The Runtime Schedule field is renamed to Suspend Time Schedule with a start and stop time that can be selected in half-hour time slots. See Policy Management > Configuring a Suspension Policy for additional details.

Security

Cloud Remote 5.1 includes a script to install your own TLS certificate and key. 

UI

New Look and Feel for Images page. Searching has been enhanced to search for entries which are outside the visible window. See Images Page for additional details.

API

Workload Manager 5.1.0 includes the following new and updated APIs.

New APIs

The following list identifies the new Workload Manager APIs:

  • Images and services RBAC now has a new API that uses the name, detail (Boolean), page, size, sort, order, checkRole (Boolean):

    • GET /api/v1/tenants/{tenantId}/images/search

    • See CCM Calls 5.1.0 > images-controller for additional details.

  • The Multi-Site integration feature has new APIs:

    • GET /api/v1/extensions/mso

    • POST /api/v1/extensions/mso

    • GET /api/v1/extensions/mso/properties

    • GET /api/v1/extensions/mso/{extensionId}

    • PUT /api/v1/extensions/mso/{extensionId}

    • POST /api/v1/extensions/mso/{extensionId}/connect

    • PUT /api/v1/extensions/mso/{extensionId}/revalidate

    • See CCM Calls 5.1.0 > mso-extensions-controller-v-1 for additional details.

  • The containerServiceActions parameter:

    • This is a new parameter to set up two types of container lifecycle hooks – post-start and pre-stop.

    • Any action defined in post start is executed after the container has started.

    • Any action defined in pre stop is executed just before the container is terminated.

Updated APIs

The following list identifies the updated Workload Manager APIs:

  • The Actions APIs include the following additional action request parameters to the PUT /api/v1/actions/{actionId} API:

    • enableExplicitShare (boolean):

      • true = Out of Box (OOB) action is not shared by default.
        For example: PUT /api/v1/actions/{actionId}?enableExplicitShare=true

      • false = OOB action is shared by default.
        For example: PUT /api/v1/actions/{actionId}?enableExplicitShare=false

    • enable (boolean):

      • true = Out of Box (OOB) action is enabled.
        For example: PUT /api/v1/actions/{actionId}?enable=true

      • false = OOB action is disabled.
        For example: PUT /api/v1/actions/{actionId}?enable=false

    • See CCM Calls 5.1.0action-controller-v-1 for additional details.

  • The JobsController v1 APIs have a new parameter as part of the JobResponseJaxb object that is only supported for VMware:

    • hibernateAction (boolean):

      • true = Hibernate action is supported for this deployment (the toggle button is visible in the UI as part of the Suspend popup).

      • false = Hibernate action is not supported for this deployment.

    • If the nodes are in the hibernate state, the job will still be in a suspended state. However, the virtual machine status will display Hibernated!

    • See CCM Calls 5.1.0 > jobs-controller for additional details.

  • The following APIs in JobsController v2 have been updated to include container deployments (see CCM Calls 5.1.0 > jobs-controller-v-2 for additional details):

    • POST: /v2/jobs (you can also override the container image version):

      {
         "appId":34,
         "appVersion":"1.0",
         "name":"nginx",
         "environmentId":"1",
         "parameters":{
            "appParams":[
      
            ],
            "cloudParams":{
               "cloudRegionId":"2",
               "accountId":"2"
            }
         },
         "jobs":[
            {
               "tierId":"35",
               "policyIds":null,
               "tagIds":[
      
               ],
               "securityProfileIds":null,
               "parameters":{
                  "appParams":[
                     {
                        "name":"referredJob",
                        "value":""
                     }
                  ],
                  "envParams":[
      
                  ],
                  "cloudParams":{
                     "cloudRegionId":"2",
                     "accountId":"2",
                     "volumes":[
      
                     ],
                     "rootVolumeSize":"0",
                     "cloudProperties":[
                        {
                           "name":"namespace",
                           "value":"cisco"
                        }
                     ],
                     "nics":[
      
                     ]
                  }
               },
               "appServices":[
                  {
                     "appServiceId":"3",
                     "imageVersion":"1.17",
                     "parameters":{
                        "appParams":[
      
                        ],
                        "cloudParams":{
                           "instance":"100mCPU_1074MBMEMLinux",
                           "containerVolumes":[
      
                           ]
                        }
                     }
                  }
               ],
               "numNodesToLaunch":1
            }
         ],
         "timeZone":"GMT+05:30",
         "responseJobJaxbNotRequired":true
      }
    • PUT /v2/jobs/{jobId} (for Kubernetes-based applications and for rolling update attributes, you can update the image version in a deployed application – with the first ID representing the parent jobId and the jobs attributes representing the child jobs – as visible in the following payload):

      {
         "id":"116",
         "action":"UPDATE_CONTAINER_IMAGE",
         "jobs":[
            {
               "id":"117",
               "k8SDeployment":{
                  "pods":[
                     {
                        "containers":[
                           {
                              "id":120,
                              "image":{
                                 "name":"nginx:1"
                              }
                           }
                        ]
                     }
                  ]
               }
            }
         ]
      }
  • The following APIs include the checkRole (Boolean) parameter:

    • GET /api/v1/tenants/{tenantId}/images/{id}

    • GET /api/v1/tenants/{tenantId}/services

    • GET /api/v1/tenants/{tenantId}/services/{id}

    • See CCM Calls 5.1.0 > images-controller for additional details.

  • The API endpoint is now corrected to ensure that the appId is passed as part of the object.

    • In earlier releases, this usage resulted in an HTTP_405 error.

    • See View Cloud Instances for additional details.

  • The GET v1/tenants/{tenantId}/clouds/{cloudId}/regions/{regionId}/instanceTypes API has a new serviceCategory parameter, which is an enumeration with the possible values being COMPUTE, STORAGE, DATABASE, or NETWORK, to identify types as visible in the following code block. See CCM Calls 5.1.0 > action-controller-v-1 for additional details.

    {
       id:"5d1..................4cc",
       resource:"https://<HOST>:<PORT>/cloudcenter-cloud-setup/api/v1/tenants/1/clouds/3/regions/4/instanceTypes/5d1..................4cc?page=0&size=30&sort=id-&order=asc",
       name:"c5n.large",
       description:"$0.108 per On Demand Linux c5n.large Instance Hour",
       type:"c5n.large",
       cloudId:"3",
       regionId:"4",
       costPerHour:0.108,
       costPerHourPreferredCurrency:0.108,
       memorySize:5376,
       numOfCpus:2,
       cpuUnit:"VIRTUAL_CPU",
       numOfNics:3,
       localStorageCount:0,
       localStorageSize:0,
       supportsCuda:false,
       supportsSsd:false,
       supports32Bit:false,
       supports64Bit:true,
       supportsHardwareProvision:false,
       serviceCategory:"COMPUTE"
    }
  • If a service type is identified as CONTAINER, then the following changes apply:

    • The following APIs were updated with these changes:

      • POST /v1/tenants/{tenantId}/services

      • PUT: /v1/tenants/{tenantId}/services/{serviceId}

      • See CCM Calls 5.1.0 > services-controller for additional details.

    • The containerImages parameter:

      • This parameter continues to be an array to ensure backward compatibility, can now hold only one element.

      • The following code block displays a sample JSON of containerImages which is a subset of the ServiceJaxb.

        "containerImages":[
           {
              "id":50,
              "url":"nginx",
              "imageVersion":"",
              "containerCommand":{
                 "commands":[
                    "sh",
                    "-c",
                    "while true; do sleep 2; echo hello $0$1; done"
                 ],
                 "arguments":[
                    "Picked from",
                    "Service"
                 ]
              },
              "default":true
           }
        ]
    • The imageVersion is a new parameter to specify the image version. If left blank, the Workload Manager uses the latest image.

    • The containerCommand parameter is a new parameter which includes command and arguments. The command parameter overrides the entry point defined in the Docker image. The arguments parameter passes arguments to the entry point. The following code block displays a sample payload for containerServiceActions which is a subset of ServiceJaxb.

      "containerServiceActions":[
         {
            "actionName":"CONTAINER_PRE_STOP",
            "actionType":"CMD",
            "commands":[
               "/bin/sh",
               "-c",
               "echo Hello from Pre stop handler UI > /usr/share/Pre_stop; do sleep 100; done"
            ],
            "url":null
         },
         {
            "actionName":"CONTAINER_POST_START",
            "actionType":"CMD",
            "commands":[
               "/bin/sh",
               "-c",
               "echo Hello from postStart handler UI > /usr/share/Post_start"
            ],
            "url":null
         }
      ]

Swagger File Documentation for APIs

The Workload Manager Calls 5.1.0 section provides an automated Swagger file listing the available API calls for Workload Manager 5.1.0. While these files do not contain the history and details that are available in the older API documentation, this section provides an exhaustive list of the API calls for each release. Going forward, the API documentation for each release will be generated automatically to ensure consistency with the rest of the CloudCenter Suite documentation.

The Manual API Documentation section continues to be available and provide information that was previously available in Workload Manager 5.0 and earlier releases. The same information is retained here for easy reference in addition to the Swagger files. The Swagger files and the Release Notes provide the historical API information going forward – this manual section is only intended for additional reference and will not be updated. Once the swagger files are in place, this section will be deprecated.

Integrations

  • ACI Multi-Site: Workload Manager 5.1 supports a new extension: ACI Multi-Site. See ACI Multi-Site Extensions for additional details.

  • ServiceNow: Workload Manager 5.1 introduces support for Integration – Cisco CloudCenter Suite 4.0.0 for ServiceNow's New York, Madrid, and London versions. See ServiceNow Extensions for additional details.

Deprecated Functions

  • The NFS and CephFS services are deprecated.

  • Workload Manager support for Cisco UCSD was deprecated effective CloudCenter Suite 5.0. In CloudCenter Suite 5.1, the action type Invoke Cisco Director Workflow is deprecated from the Action Library On-Demand Action. While this action continues to display in this release the functionality is no longer supported and will be removed in a subsequent release.

  • The OpenStack v2 identity API was deprecated as of 5.0.1 (as part of the Queens release) and will be removed support in a subsequent release.

  • The following OOB logical images are no longer available:

    • Bare Metal Ubuntu 12.04

    • Callout Workflow

    • Cloud Image Helper

    • Common AWS External Services

    • External Service RDS

Documentation

The following documentation changes were implemented in CloudCenter Suite 5.1.0:

Known Issues

Workload Manager 5.1.0 has the following known issues:

  • Prior to CloudCenter Suite 5.x, manual AgentLite installations used a default value for vhost and did not require user input. Effective CloudCenter Suite 5.0, users must specify the vhost value for the region in which the vhost instance exists. You must specify the vhost (brokerVirtualHost) value for the region in which the vhost instance exists. To retrieve the vhost value, you must configure a load balancer instance for RabbitMQ, log into the load balancer instance, and retrieve the value using the /v1/tenants/tenantId/clouds/cloudId/regions?size=0 API. See Virtual Machine Management > Install AgentLite ManuallyLocating the vhost Value for additional details.  

  • When configuring a cloud region, the Proxy field only accepts the hostname of the proxy server. Appending HTTP or HTTPS along with the proxy server hostname, will cause application deployment to fail. Hence enter the hostname in the proxy field without prefixing the protocol.

  • When configuring environments for IBM Cloud, verify that you have at least one VM instance running in that region (which could be launched manually) to ensure that the VLAN properties are listed in the Workload Manager's Environments page. If VLAN does not exist, they get created on first deployment.

  • For existing deployments created before 5.1.0, deploy flow does not show instance types, for deploy windows applications. In such cases, just edit the existing environment without making any changes and save it. Post that, the instance types will be displayed in the deploy flow. (CCSWM-1528).
  • Image mappings for Windows Server 2008 with Microsoft SQL 2008 and Windows Server 2012 with Microsoft SQL 2012 have been removed in AzureRM as these images do not support cloud-init anymore. To use these services, create your own custom image and add the mapping.

  • For deploying applications that use Ubuntu14 and Windows (2008, 2012, or 2016 versions) on IBM Cloud, create your own custom images and add the mapping. Out-of-the-box mappings are not provided for these operating systems.

  • If a user key pair is deleted from the cloud, deployments will fail stating that the user key pair does not exist. The Repair User functionality is not supported from Workload Manager 5.0 onwards. Instead, use the API to generate the key pair: 

    API: https://<ccs-ip>/cloudcenter-ccm-backend/api/admin/service/reinit_user, 
    
    HTTP Method: POST
    
    Sample Payload
    { ""cloudType"":""<your cloud region"", ""cloudAccountId"":<cloud account id for which key needs to be generated"", ""forAllClouds"":false, ""userId"":<user id for which key needs to be generated>} "
  • When a proxy points to the Suite Admin URL, you may not be able to add workflows in the Workload Manager lifecycle action. 

  • When using the ServiceNow Integration - Cisco CloudCenter Suite 3.0.0 application with CloudCenter Suite 5.0, then you can retrieve the CloudCenter Suite Owner API key in the ServiceNow application during the integration setup process using one of two ways. 

    • A manual method where you copy-paste the owner API key into a ServiceNow table. 

    • An automated method where you enter CloudCenter Suite owner credentials in the ServiceNow application.  The application retrieves the API key from CloudCenter Suite and saves it into a ServiceNow table.  The automated method was first developed for CloudCenter Suite 5.0 and ServiceNow app v3.0.  Due to the API end-point change in CloudCenter Suite 5.1, the automated method to retrieve the API key does not work when using the integration application v3.0.

    You can workaround this issue by using the manual method to copy-paste the owner API key.

  • Each AWS and Azure cloud account may not have access to allregions. To access different regions you may need to use different accounts. In CloudCenter Suite 5.x, this delineation is not enforced - when you add regions and cloud accounts to a cloud group, make sure to only add the regions that are accessible by all the cloud accounts you add to the cloud group. For example, AWS has separate accounts for China, Government, and other regions. The following links provide additional details on the regions supported by AWS and Azure - for each of these cloud groups, be sure to create separate cloud accounts.

Resolved Issues

The following issues were resolved/addressed in CloudCenter 5.1.0:

  • CSCvf61598: In CloudCenter 4.8.0.1 environments, when using the search functionality within the CloudCenter Deployments section, the search results are only provided for the current page. It should search all deployments across multiple pages.
    Resolution: Workload Manager 5.1.0 includes fixes to ensure that deployment searches work across pages.

  • CSCvf93492: The search only lists matches from the current page and does not search across pages.
    Resolution: Workload Manager 5.1.0 includes fixes to ensure that image and deployment searches work across pages.

  • CSCvg19806: Need the ability to share the Cloud Accounts with edit access to a restricted group in which they can manage cloud accounts. In the current situation, Cloudcenter does not provide edit access to the cloud accounts other than the owner itself.
    Resolution: In Workload Manager 5.1.0 cloud accounts are tenant owned entities. All the users belonging to the Workload Manager Admin group will have edit access to the cloud accounts to share the cloud account with permitted users who are not the cloud account owners.

  • CSCvg50487: The CCM GUI does not reflect new volume size after modifying the instance in the cloud and sync in Cloud Remote.
    Resolution: In Workload Manager 5.0, the Sync VM Information action displays the instance state, instance type, and volume details for the VM for each action performed on the cloud.

  • CSCvi96398: In a cloud or datacenter environment that does not allow access to external package repositories and where a Workload Manager internal repo is configured, the deployment fails even if the component is configured to use the internal repo. The CentOS worker appliance contains references to external package repositories, which are inaccessible by this configuration. If an internal Cloud Remote repo is configured these package repos should be updated so the CentOS worker appliance is updated to point to the internal Cloud Remote package repository.
    Resolution: repo.cliqrtech.com is updated with the missing packages. If an internal Workload Manager package repo is configured, these package repos should sync with repo.cliqrtech.com. Additionally, ensure that CUSTOM_REPO environment variable is updated to point to the Workload manager internal repository while running the worker installer.

  • CSCvj63894: In a CloudCenter 4.8.2.1 environment with VMware ESXi, if a deployment fails because of any error coming from the ESXi side, the gateway.log reports the error, but it does not report which ESXi host returned the error.
    Resolution: This issue is being closed as it is not possible to retrieve the ESXi host information using the VMware cloud SDK.

  • CSCvk27251: CCM GUI is extremely slow when 630 Instance Types exist.
    Resolution: This works as expected in Workload Manager 5.1.0. 

  • CSCvm66827: In a CloudCenter 4.9.0 environment, when executing a VM action (Stop/Reboot/Terminate) from the deployment status page, the warning message provided to the user is insufficient.  
    Resolution: Workload Manager 5.1.0 includes an enhancement to provide descriptive error messages in these scenarios.

  • CSCvo12874: Unable to enable or disable termination protection from project deployments.
    Resolution: Workload Manager 5.1.0 includes a fix to enable or disable termination protection for deployments in a project.

  • CSCvo16588: Any part of the UI that allows users to configure parameters of type number, the value range is to be with the 0-255 range. 
    Resolution: Workload Manager includes a fix to ensure that parameters of type number have a range from 0-999999.

  • CSCvo22784: Cisco Cloudcenter - VM deployment number restriction not working (VMs running simultaneously)
    Resolution: In Workload Manager 5.0, there is no option to assign plans in CCM, plans can be assigned through CloudCenter Suite only. This issue has been fixed Workload Manager 5.1.0.

  • CSCvo29130: The default Overage strategy for a VM Subscription should not be Unlimited as a user can state that a specific number of VM be allowed for this plan. The default should be changed to Limited.  
    Resolution: Workload Manager includes an enhancement to change the default Overage strategy for a VM Subscription to Limited.

  • CSCvo64795: When using the benchmark in CCM GUI, the benchmark throws an error with JobError: IP address of the worker node not found.
    Resolution: %
    wm 5.1.0 includes a fix to use a private IP address of the worker node for benchmarking.

  • CSCvo77363: When using a Service Parameter password type - after the initial value is set, it does not update during deployment after changing password.
    Resolution: It is recommended that customers facing this issue use the deployment parameters, instead.

  • CSCvo92773: CloudCenter Platform 4.9.0 did not track the time it took for a VM to start the deployment until the time it took to finish the deployment. It only provides the start time or runtime of the Application and the end time. This would only reveal the total time of the deployment.  
    Resolution: Workload Manager 5.1.0 includes an enhancement to calculate and display the total deployed time.

  • CSCvp00110: CloudCenter Platform 4.10.0.2 had a periodic SQL query against the PostgreSQL database that includes a UNION in the syntax. The customer requested that this query be improved to remove the UNION from the syntax.
    Resolution: Workload Manager 5.1.0 includes an enhancement to remove this UNION from the syntax.

  • CSCvp14195: Ubuntu18.04 not available in custom_repo_util.sh Cliqr script.
    Resolution: Workload Manager 5.1.0 includes a fix for custom_repo_util.sh Cliqr script that includes Ubuntu18.04.

  • CSCvp53665: A customer using hundred of tags requested the ability to retain the metadata but turn off the tags being injected into vCenter.
    Resolution: Workload Manager includes a new Disable Custom Attributes field (default = false) in the region settings to allow users to determine the behavior.

  • CSCvp69740: Benchmark via cloud remote on AWS does not work
    Resolution: Workload Manager 5.1.0 includes a fix that benchmarks applications via cloud remote also.

  • CSCvp70738: When specifying an additional Service or Deployment parameter it is not possible to specify a list of values that is more than 255 characters. 
    Resolution: Workload Manager 5.1.0 includes an enhancement to support more than 255 characters for these parameters.

  • CSCvp70814: Legacy CloudCenter Custom Service Cleanup scripts are not being executed unless a node cleanup script is also specified for each custom service cleanup script that is being run.
    Resolution
    : Workload Manager 5.1.0 includes an enhancement to execute the cleanup scripts for custom services.

  • CSCvp99234: Error message when trying to reference callout scripts from a repo.
    Resolution: The cloud region is not shared with managed permissions and hence, during deployment, there are no get strategy settings at the job level. This results in an empty job level strategy. So, no repo is added. Workload Manager 5.1 has been changed to fetch the cloud object from the database directly without an ACL verification.

  • CSCvp99362: Modeling a new application template does not display the template's image.
    Resolution: Workload Manager 5.1.0 includes a fix so that logos appear as required.

  • CSCvq09604: The web service global parameter does not work with proxy authentication.
    Resolution: As web service calls are routed through the proxy CloudCenter Suite 5.1 includes a fix to ensure that when proxy settings are modified on the Suite Admin, the CloudCenter Suite management pod is rebooted to apply the configuration. See Proxy Settings for additional details.

  • CSCvq13004: Unable to see unmanaged Azure VMs with a base cluster in VMware.
    Resolution: Unmanaged VMs started to show up for Azure after the account role was updated to Provisioning, Reporting, which is required for inventory collection.

  • CSCvq25607: Request to add support for custom Azure RM Resource Naming Conventions.  
    Resolution: Workload Manager 5.1.0 provides an optional osHostname in addition to the vmName for AWS, VMware, and Azure RM. If users provide the osHostname, then the Workload Manager uses it as the hostname. If using a security group, the firewall rules are also updated accordingly. Additionally, the vmName value is now increased to 64 characters.

  • CSCvq30347: Currently, a CLI user does not have the ability to schedule API jobs. However, the same is possible using the UI.
    Resolution: Workload Manager 5.1.0 includes an enhancement to allow CLI users to schedule API jobs.

  • CSCvq37239: Add disk is failed for Azure server.
    Resolution: Workload Manager 5.1.0 includes a fix for the permission issue so that disk can be added the VMs on Azure.

  • CSCvq62059: Unable to view VM details from deployment page as a standard user.
    Resolution: Workload Manager 5.1.0 includes a fix so that standard users can view VM details from deployment page.

  • CSCvq63405: VMs deployed through Workload Manager do not contain detailed information in the exported CSV file.
    Resolution: Workload Manager 5.1.0 includes a fix that displays the Details column in the CSV file.

  • CSCvq67729: systemctl restart, start, stop, or status is not working for agentd.
    Resolution: Workload Manager 5.1.0 includes a fix so that agentd can be administered through systemctl.

  • CSCvq71090: Attach volume fails if Cinder is configured in a different availability zone than the VM. 
    Resolution: Workload Manager 5.1.0 includes an enhancement to verify the zone information as part of the validation

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