Suite Admin 5.1.2 Release Notes

Release Date

First Published: November 25, 2019

Updated:

  • August 4, 2020: Removed references to SaaS EU from the entire site

  • August 26, 2020: Added the Limited Trial Program section

  • September 24, 2020: Updated the Documentation section to list modified pages

Installation

CloudCenter Suite 5.1.2 is available as installers for ALL components for all supported clouds. Contact the CloudCenter Suite Support team for additional details.

Backup and Restore

CloudCenter Suite 5.1.2 allows you to restore data in the following environments:

To restore data, the CloudCenter Suite requires that you launch a new cluster. If you configured the old cluster using a DNS, you must update the new IP address (from the restored cluster) that is mapped to the DNS entry. Once you update the DNS entry of your new cluster, these services will continue to work as designed.

The backup/restore feature is only available on CloudCenter Suite clusters installed using CloudCenter Suite installers and not on existing Kubernetes clusters.

Kubernetes Cluster Upgrade

No updates

Updating Modules

While you can update just the modules without upgrading the Kubernetes cluster, you will continue to see the new CloudCenter Suite 5.1 features for each module. See Update Module for additional details.

  • Before updating any module, verify that you have twice the required CPU/Memory in your cluster. A module-update scenario requires additional resources for the old pod to continue running until the new pod initializes and takes over. This additional resource requirement is temporary and only required while a module update is in progress. After the module is updated, the additional resources are no longer needed.

  • You must update the Suite Admin module before you update any other CloudCenter Suite module. 

  • Update only one module at at time. If you simultaneously update more than one module, your update process may fail due to limited resource availability. See Prepare Infrastructure for additional context.

  • You may see one or more error messages during the update process. Be aware that these messages will not affect the update itself.

See SaaS Access for FAQs on updating SaaS environments.

Limited Trial Program

The 30-day trial is a limited program that ends on September 30, 2020. Contact a Cisco sales representative for additional details.

Architecture

No updates

Clouds

No updates

Administration

  • Effective CloudCenter Suite 5.1.2, tenants admins can configure the Base URL of any of their ancestor tenants. The only caveat is that the admin cannot set the Base URL of child tenant for a parent tenant. See Base URL Configuration for additional details. 

  • After upgrading from Suite Admin 5.1.0 to 5.1.1, Kibana may not be accessible. This was a known issue in CloudCenter Suite CloudCenter Suite 5.1.1. After upgrading to CloudCenter Suite 5.1.2, Kibana is accessible and the workaround is no longer required.  

  • When configuring the backup storage location for the first time, CloudCenter Suite 5.1.1 uses this location as the default region. Subsequent changes to this region are no longer accepted. Once configured, you cannot change or update the backup storage location for the AWS S3 cloud region, when using CloudCenter Suite 5.1.1. This was a known issue in CloudCenter Suite 5.1.1 and has been fixed in CloudCenter Suite 5.1.2 – you can now change the backup storage location for the AWS S3 cloud region. 

  • When configuring a Backup, you cannot change the cloud account at any point in the process. his was a known issue in CloudCenter Suite 5.1.1 and has been fixed in CloudCenter Suite 5.1.2 – you can now change the cloud account.

  • Prior to CloudCenter Suite 5.1.2, users were unable to delete a subtenant. Effective CloudCenter Suite 5.1.2, a tenant deletion is successful and tenants do not reappear post deletion. 

Module Management

No updates

Smart Software Licensing

No updates

Suite Admin Dashboard

No updates

User Tenant Management

No updates

Cluster Management

No updates

Security Management

This release addresses security vulnerabilities by upgrading OS libraries. Cisco provides updated OS and Docker files that address the security vulnerability for both applications.

Suite UI

When logging into the CloudCenter Suite UI in prior releases, the Tenant ID was always required. Effective CloudCenter Suite 5.1.2, users have the option to save the Tenant ID on the login page so when they open the browser and login every day they are not required to manually enter the Tenant ID.   

Deprecated

No updates

API

The following APIs were introduced in CloudCenter Suite 5.1.2:

  • Lists all users under the requested tenant's last login information – to help identify how often different types of users log into the application: 

    • GET /suite-auth/api/v1/tenants/{tenantId}/lastLoginInfo

    • The tenantId must be a child of the current tenant.

    • See IDM Service API Calls 5.1.2 > User Controller for additional details.  

  • Lists the total current users as a snapshot in time long with the user count per tenant ID and the user count per role: 

Documentation

The following documentation changes were implemented in CloudCenter Suite 5.1.2:

Known Issues

In some CloudCenter Suite 5.x environments it may be necessary to increase CPU and memory limits for the common-framework-suite-prod-mgmt pod prior to upgrade of any CloudCenter Suite module. See Update Module for details.

Resolved Issues

CloudCenter Suite 5.1.2 has the following resolved issue:

  • CSCvp23756: After upgrading from CloudCenter Suite 5.0 to 5.0.1 and having a certificate installed in the UI, the user cannot login to the CloudCenter Suite UI. 
    Resolution: CloudCenter Suite 5.1.2 includes a fix to ensure that this feature works as designed.

  • CSCvq96291: After upgrading from Suite Admin 5.0.3 to Suite Admin 5.1 on a Kubernetes cluster that was setup as a pre-existing cluster (no installers were used other than to install products/modules), a user reported that the whole CloudCenter Suite system stopped working because the ingress controller pod continually crashed.  
    Resolution: CloudCenter Suite 5.1.2 was tested with this procedure and the product installation completed on an existing, upgraded cluster, without any issues.



  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks