Cisco CloudCenter 4.8.1 Release Notes

Release Date

CloudCenter 4.8.1 – August 21, 2017

Updated:

  • August 30, 2017 (core_upgrade.bin and Microsoft Azure Government regions)
  • September 12, 2017 (ACI integration version support and additional known issue)

Installation

CloudCenter 4.8.1 is available as virtual appliances. See Virtual Appliance Overview for additional context.

  • The CCO wizard has been enhanced to include all CCO-related timeouts in the Config_Duration screen. See Per Cloud Region (Required) > CCOConfigure CCO Wizard PropertiesConfig_Duration for additional details.

  • The repository (repo) wizard properties, Bundle Folder and Bundle URL, need to be configured differently. See Repo (Conditional) for additional context. This is a change!

  • The Docker Container Timeout field in the CCO wizard is moved to the External_Script_Executor option to provide context for a script executor configuration change. In earlier releases, this field was part of the Docker option. See Per Cloud Region (Required) > CCOConfigure CCO Wizard Properties for additional details. This is a change!

Upgrade Instructions

You can only upgrade to CloudCenter 4.8.1 from CloudCenter 4.6.0 and later releases.

To upgrade to CloudCenter 4.8.1, see Upgrade Overview.

Architecture

No updates

Clouds

  • vCD:

    • Brownfield VMs can now be imported from VMware vCD to for management from the CloudCenter platform. See VM Management for additional context.

    • Additional support for VM Actions Attach Volume and Detach Volume. See Actions Library for additional context.

    • Prior to CloudCenter 4.8.1, If the vcdconfig file did not exist, you had to follow an additional step when configuring the vCD Cloud account, this step is no longer required. See Configure Cloud(s) > Configure a vCD Cloud for additional context.

    • The vCloud OrgVdc, vCloud OrgVdc Shared Network, and vCloud Isolated Network fields are no longer available in cloud account configuration in CloudCenter 4.8.1 and later releases. See Configure Cloud(s) > Configure a vCD Cloud for additional context. The Organization Virtual DataCenter is not required to configure a cloud. Instead, it is selectable as part of the Deploy form submission process. OrgVDC isolated network and shared network can be selected as part of the OrgVDC network dropdown in the Deploy form submission process.

    • Support for the vmnaming and ipam callouts (see Callout Scripts for additional context). Additionally, the  Instance Naming Strategy and the Instance IPAM Strategy fields are now available in the Cloud Regions page. See Configure Cloud(s) > Configure a vCD Cloud for additional context. 

    • Multiple NIC support allows you to specify the number of NICs to assign to the VM by adding the number in the image definition. The profile inherits the number of NICs from the image and when you deploy the application. See IP Allocation Mode > vCD for additional context.

    • Once you upgrade to CloudCenter 4.8.1, you must select the deployment environment defaults and save them again as the older saved defaults will not be carried forward.

  • Google Cloud:

    • Brownfield VMs can now be imported from Google Cloud for management from the CloudCenter platform. See VM Management for additional context. See Public Clouds for additional details.

    • Additional support for VM Actions Attach Volume and Detach Volume. See Actions Library for additional context.

    • The CloudCenter platform supports the vmNaming and ipam callout scripts for Google Cloud. See Callout Scripts and VM Name Config for additional context.

    • Effective CloudCenter 4.8.1, the Project ID for Google Cloud account setting is optional. Additionally, the Project ID selected in the cloud settings section of the Deploy form is where the VM is deployed. See Configure Cloud(s) > Configure Google Cloud for additional context.

    • Google cloud instances display one of the following values for the volume Type attribute: Standard Persistent Disk, SSD Persistent Disk, and Local SSD Scratch disk. See Multiple Volumes for additional context.

  • Azure RM:

    • Additional support for Microsoft Azure Government regions (US Gov Iowa/Virginia)

    • The CloudCenter platform does not support managed disk and custom images for these regions.

    • See Public Clouds for additional details.

  • New Images provided by Cisco: Application VM (worker) images:

    • Windows 2016 support for AWS, VMware, AzureRM, OpenStack and SoftLayer.

    • Ubuntu 14 support for VMware and OpenStack.

    • See Base OS Images for additional context.

Applications and Services

  • The version of RDS MySQL provisioned on the CloudCenter platform has changed from 5.6.23 to 5.6.35. See Services > PaaS Support for additional context. This is a change! 

CloudCenter Management

  • Deployment Management:

    • The Organization Virtual DataCenter (vCloud OrgVdc) field is selectable as part of the Deploy form submission process. The isolated network and shared network can be selected as part of the OrgVDC network dropdown in the Deploy form submission process. See Deployment Environment Defaults or Environments for additional context.

    • A Cron utility runs in the background at 02:00 hours (CCM system time) and automatically terminates VMs for jobs/deployments that are in the Error state. See Deployment and VM States > Auto-Clean up of Resources for additional context.

  • Virtual Machine Management:

    • The import icon for imported VMs has changed. See the VM Management page for a sample screenshot and additional context.

    • VMware vCD and Google Cloud Brownfield VMs can now be imported to CloudCenter from VMware vCD and Google Cloud. See VM Management for additional context.

  • Custom Actions Management:

    • Imported VMs with AgentLite installed can execute custom scripts/commands. Effective CloudCenter 4.8.1, these scripts can additionally send status messages back to the CloudCenter platform if you invoke the actionSendMessage function when you create a custom action.

    • See Actions Library > Action Definition Section > Execute From Bundle for additional context.

Administration and Governance

  • You can additionally filter CloudCenter resources using the user-based Groups filter (see the highlighted image above). See Reports Overview for additional details.

  • The cliqr-user-security-group_userId security group name:

    • Is created for AWS, Alibaba, and OpenStack clouds if the createUserSecurityGroup and allowVmConnection settings are both set to true (see the Create Tenant API changes below for additional context).

    • Is created for Google cloud as follows: This is a change!

      • Prior to CloudCenter 4.8.1 =  networkName-cliqr-job-worker-userId

      • Effective CloudCenter 4.8.1 = networkName-c3-user-userId-ruleId

  • The cliqr-firewall-*security group name is created for the Google cloud as follows: This is a change!

    • Prior to CloudCenter 4.8.1 =  networkName-cliqr-firewall-uniqueId

    • Effective CloudCenter 4.8.1 = networkName-c3f-uniqueId-ruleId

  • See Security and Firewall Rules for additional context.

Security

  • The Enable Microsegmentation feature has been renamed. This is a change!

    • New Name: Inter-Tier Communication (Firewall Rules) as a new sub-section title

    • Enable checkbox: Restrict to one-way south-bound communication between connected tiers.

  • A Google cloud firewall tag (named networkName-cliqr-job-worker-userId created for each user). This firewall tag is attached to all VMs in the applications deployed by the user. You can now configure the firewall rules that are specified to the Tenant configuration.

  • When the application profile, tier-level firewall rule has rules that have different CIDRs, the firewall tag configured was not correct. Instead, separate, reusable firewall tags are now available for different source CIDRs.

  • See Security and Firewall Rules for additional context.

End of Life Notices

See End of Life Notices for additional details.

Deprecated

  • Cisco will be deprecating support for Microsoft Azure Classic for CloudCenter 4.8.1 and later releases. The documentation and some pages in the CCM UI may still display Azure Classic as a possible choice. However, these choices will also be removed in an upcoming release.

CCM UI

  • Browser Compatibility: Cisco supports the two latest versions of each browser. See Browser Compatibility for a list of compatible browsers.

  • Localization: See UI Behavior for additional context.

API

CloudCenter 4.6.0 introduces v2 APIs, where applicable. If a new API is introduced for the first time, it continues to use v1 as it is still the first version of that particular API. The following list differentiates between the New and Updated APIs for CloudCenter 4.8.1.

  • New APIs:

Integrations

  • Callout Scripts:

    • The nicGateway_n parameter for the IPAM callout script is optional. This is a change! 

    • See Callout Scripts > Supported Properties for additional context.

  • ACI:

    • Effective CloudCenter 4.8.1, Cisco supports APIC, Release 2.3.

    • See ACI for additional context.

Documentation

This section lists the documentation changes implemented in CloudCenter 4.8.1.

Known Issues

CloudCenter 4.8.1 has the following known issues:

  • When using the CephFS and NFS services in an application, deploy these services using the Persist Private Key or the default, no preference for SSH options. Your storage browser will not function if you use the Assign SSH Public Key option. See SSH Options for additional context. 

  • When you deploy an application with persistent volumes attached on vCD cloud, the deployment status sometimes hangs in the In Progress state and does not move to the Deployed state. This issue is caused by an application tier (with volumes attached) being stuck in the service deploy state – the additional volume may have already been mounted by default to /mnt and leaves the service hanging in the In Progress state when trying to locate an unmounted volume. This issue was also observed when resuming an application after suspending it. To workaround this issue, unmount the persistent disk attached to the tier either by using SSH to connect to the VM or by restarting the VM. 

Resolved Issues

The following issues were resolved/addressed in CloudCenter 4.8.1:

  • Issue: Deploying a worker VM for a SoftLayer cloud results in a dynamic bootstrapping failure.  
    Resolution: CloudCenter 4.8.1 includes a fix to ensure that SoftLayer-specific bootstrapping scripts are included in the gateway.properties file.

  • Issue: A CloudCenter deployment on Google Cloud fails if the network name is more than 16 characters. 
    Resolution
    : Be aware that the CloudCenter platform appends the network name with an unique ID to form the firewall rule name, the network name can be a maximum of 24 (network name) + 39 (unique ID) = 63 total characters. For example: abcdefghijklmnopqrstuvwx-c3f-462828f37a06acd3ee194716bfe10d.

  • Issue: A deployment moved to the Terminated state, but the instance continued to remain in the running state. When trying to delete this instance from the CCM UI, the CloudCenter platform issued the following error: ERROR MESSAGE - Terminated is not a valid state for operation terminate. It should be in Deployed/Error/In Progress/Migrate Pending/Migration Error/Migrating/Resuming/Stopped/Stopping/Stopping Error/Submitted/Suspended/Suspending/Terminating/Upgrade Error/Upgrade Rolled back/Upgrade Rollback Error/Reconfiguring/Scaling state.  
    Resolution
    : CloudCenter 4.8.1 includes a fix to address this issue. If you need to terminate an instance (that exists on the cloud) where the deployment is already terminated, the CloudCenter platform allows you to terminate that instance.

  • Issue: When deploying an application using initialization scripts, you may receive an error from the nodeCleanup script. The CloudCenter platform monitors the node clean up script every 5 minutes and automatically times out and issues this error if the task runs for more than 10 minutes. 
    Resolution
    : CloudCenter 4.8.1 introduces a new property, node.cleanup.timeout=300, that you can set in the gateway.properties file. This mandatory property allows you to control the timeout for the node clean up script. The CCO wizard has also been enhanced to include the Config_Duration screen. See Per Cloud Region (Required) > CCOConfigure CCO Wizard PropertiesConfig_Duration for additional details.

  • Issue: Volumes larger than 2TB fail to attach during deployment when using the Attach Volumes button even if the NFSv3 datastore has sufficient capacity. However, the user was able to manually add the volume when using vCenter. 
    Resolution
    : CloudCenter 4.8.1 provides a fix to address this issue and the Attach Volumes button now functions as designed.

  • Issue: The application profile's editable metadata values are erased when you edit and save an application, even if no values have been changed. 
    Resolution
    : CloudCenter 4.8.1 provides a fix to address this issue and the edit operation now functions as designed.

  • Issue: The Password Reset screen was unable to locate a user if the user's email address contained mixed-case characters. 
    Resolution
    : CloudCenter 4.8.1 includes a fix to allow users to reset their password even when using a mixed-case email address.

  • Issue: A custom global parameter password is not being decrypted for an imported (zip) application during deployment
    Resolution
    : For security reasons, the CloudCenter platform encrypts the password parameters when applications are exported. Applications that were exported prior to when the password parameter encryption was introduced in the CloudCenter platform may have used the plain text password and those passwords will not work after the import. In these cases, you must manually edit those passwords after import the application.

  • Issue: An application profile does not work when using Governance Tags with existing deployments – it is not being listed for selection when users try to deploy an application that is modeled using an existing deployment.
    Resolution: For existing deployments to show up, they must run from the same deployment environment, from where the deployment is made. Error handling has been improved to display an appropriate message.

  • Issue: The AWS eu-west-2 region was missing from the CloudCenter 4.8.0 list when adding a repository.  
    Resolution
    : CloudCenter 4.8.1 includes a fix to reflect this region.

  • Issue: Passwords of repository providers configured in repository settings are visible in plain text when HTML source is viewed / inspect element is done from browser.
    Resolution: CloudCenter 4.8.1 provides a fix to ensure that passwords are encrypted when the HTML source is viewed or when the element is inspected on the browser.

  • Issue: When using the JSON file provided in Descriptor File: Sample 3 provided in the Prerequisite Checker JSON File, the network_Validator.py script fails with an error.
    Resolution: CloudCenter 4.8.1 includes a fix to ensure that the file provided in Descriptor File: Sample 3 provided in the Prerequisite Checker JSON File works as designed.

  • Issue: Deployment on CloudCenter 4.8.0, with VMware 6.0.0 and ACI 2.0(2g) fails with error that External network parameter is of the wrong format. 
    Resolution
    : Effective CloudCenter 4.8.1, external networks have deployment-related contracts in the consumed contracts list and the format error message no longer exists.

  • Issue: When installing the Local Package Store for CloudCenter 4.7.3, some users were unable to open the UI web page. 
    Resolution: This is not a bug, it is the designed behavior for this release, Step 8 in the Configure a Local Package Store page instructs a user to Invoke the repo config wizard and configure the basic properties through the config wizard.

  • Issue: The Sync Instance Types process tries to reach out to our repo.cliqrtech.com and since this environment does not have access to the internet, this process fails. 
    Resolution:  CloudCenter 4.8.1 includes a fix to ensure that the Sync Cloud Instance Types process functions as deigned.

  • Issue: When changing a user's email or phone number via the CCM UI when using Internet Explorer, there is no response from CCM UI and the information is not changed.  
    Resolution: CloudCenter 4.8.1 includes a fix to ensure that users are able to change the email and password details from the UI when using Internet Explorer.

  • Issue: Some customers were having problems with groups passed down by Shibboleth with assigning roles in the applications. Groups are showing up in the application but we are unable to assign any roles. 
    Resolution: The Shibboleth integration doc was only intended for older CloudCenter versions. CloudCenter 4.8.1 does not include a code fix as the issue is with the Shibboleth configuration when integrating with CloudCenter.

  • Issue: The CCM UI has multiple rendering Issues when using IE and Firefox browsers. 
    Resolution: CloudCenter 4.8.1 contains multiple fixes to address these issues and the CCM UI renders as designed when using IE and Firefox browsers.

  • Issue: When configuring SSO, a user ended up with two Vendor Admin records. When trying to delete the initial record, it continued to display when viewing the Manage Vendor Admins page. 
    Resolution: CloudCenter 4.8.1 provides a fix to ensure that deleted vendors do not display on the Manage Vendor Admins page.

  • Issue: The PostgreSQL cluster wont start after applying patch on RHEL 7. 
    Resolution: This is not a bug, the correct process is documented in two doc locations: Graceful PostgreSQL Reboot and PostgreSQL Troubleshooting. By following the process, you can ensure that the PostgreSQL cluster starts as designed.

  • Issue: The RDP library was not included int the local package repository and subsequently not available for the specific Guacamole server. 
    Resolution: CloudCenter 4.8.1 includes a fix to ensure that repo.cliqrtech.com includes the RDP library.

  • Issue: Unable to launch 50 Nodes in a single Job, while nodes are launched on the cloud, they are stuck from the CloudCenter side. 
    Resolution: CloudCenter 4.8.1 provides a fix to ensure that a job with more than 50 nodes are launched without getting stuck.

  • Issue:  Unable to delete an unused cloud/region that contains associated resources like deployments/ environments.    
    Resolution: When a user tries to delete any cloud/region with associated resources, the CloudCenter platform displays a detailed error message along with the list of deployment sand deployment environments that are still linked to that particular cloud region.

  • Issue: Even if a tenant is deleted it continues to appear on the SAML configuration page. 
    Resolution: CloudCenter 4.8.1 includes a fix to ensure that deleted tenants are not displayed on the SAML configuration page.

  • Issue: A user was unable to deploy CloudCenter to an AzureRM cloud if the Public IP option was unchecked.
    Resolution: CloudCenter 4.8.1 includes fix to ensure that the deployment to the AzureRM cloud completed successfully even if the Assign Public IP was unchecked.

  • Issue: Scaling fails in VMware if the template or snapshot is located in a different cluster other than the deployment cluster.
    Resolution: CloudCenter 4.8.1 includes a fix to ensure that the snapshot and template in one datastore in one cluster can be deployed and scaled on another datastore in another datastore cluster.

  • Issue: When an upgrade is started on one node in a tier, all other nodes in the same tier must wait for the node to finish upgrading in order to be upgraded. So only one node at a time can be upgraded regardless of each node being in separate VMs.
    Resolution: CloudCenter 4.8.1 includes a fix to ensure parallel upgrades of nodes in the same tier.

  • Issue: When a user tried deploying an application with an action policy, the Action policy did not executed according to the script.
    Resolution: The MongoDB was down and hence the notification service was also down – this prevented the policy from being executed. Once the MongoDB was up and running the script executed as designed.

  • Issue: Applying an existing ACI contract to a deployment using simplified networking does not add the contract to the EPG in ACI. When not using simplified networking the contract is successfully added to the EPG. 
    Resolution: CloudCenter 4.8.1 includes a fix to ensure that multi-tier and multi-NIC configurations apply an existing ACI contract to a deployment.

  • Issue: SSH Ciphers aes256-ctr, aes192-ctr and aes128-ctr should be supported from web console SSH Client.
    Resolution: SSH configuration is updated with these ciphers when installing CloudCenter components using core_installer files. 

  • Issue: When users tried to deploy an image which contains pre-installed software that needs to be purchased, then the deployment failed with such images. (Added on September 12, 2017.)
    Resolution: CloudCenter 4.8.1.1 includes a fix to ensure that a deployment using such images succeed without errors if that image is purchased from the Azure portal.


  • No labels