Suite Admin 5.1.1 Release Notes

Release Date

First Published: September 26, 2019

Updated:

  • September 30, 2019: Added the supported Kubernetes version and updated cluster availability details for the Backup/Restore feature.

  • October 15, 2019: Updated the Kibana search filter access in the Known Issues section.

  • November 4, 2019: Updated the Documentation section to list modified pages.

Installation

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

CloudCenter Suite supports Kubernetes 1.15.4 and earlier releases.

Backup and Restore

CloudCenter Suite 5.1.1 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

You can use the installer to upgrade the Kubernetes cluster from CloudCenter Suite 5.1.0 to a later version. During this upgrade, the base image (CCS-version-Base-Image) from the upgrader is used to upgrade the Kubernetes cluster nodes. See the following pages for additional details.

To upgrade the Kubernetes cluster from CloudCenter Suite 5.0.x to CloudCenter Suite 5.1.1, follow this process:

  1. Update the Suite Admin on your CloudCenter Suite 5.0.x cluster to CloudCenter Suite 5.1.1. This update introduces the Backup and Restore functionality.

  2. Backup your CloudCenter Suite 5.0.x cluster. See Backup for additional details.

  3. Launch a new CloudCenter Suite 5.1.1 cluster and restore the backup from the previous step. See Restore for additional details.

See SaaS Access for FAQs on updating SaaS environments.

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.

Architecture

The load balancer that was used for the master nodes in CloudCenter Suite 5.0.x is no longer required in CloudCenter Suite 5.1.1.

Clouds

No updates

Administration 

No updates

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

See Security Considerations for details.

Suite UI

No updates

Deprecated

  • If you upgrade only the Suite Admin from 5.0.x to 5.1.0, you will continue to see the Download SSH Key option. However, if you install CloudCenter Suite or Suite Admin using the 5.1.1 appliance in private clouds, you will no longer see the Download SSH Key option in the Installer success page and in the Suite Admin Details page. This is because you have provided the key being used in the placement properties page when installing CloudCenter Suite.

  • System administrators no longer have root access to CloudCenter Suite clusters. 

  • The Reconfigure Cloud Credentials feature is no longer available for OpenStack environments.

API

The following new APIs are available effective Suite Admin 5.1.1:

  • GET /suite-idm/api/v1/admin/tenant_hierarchy

    • This new API lists all tenant and subtenants with the ability to select hierarchy reporting under a tenant, along with the total tenant count, the breakdown by tenant ID with a defined tenant name, and the last login by a user for each tenant.

    • See IDM Service API Calls 5.1.1 for additional details.

  • GET /suite-idm/api/v1/admin/user_statistics 

    • This new API identifies the total users as a snapshot in time and includes the user count per tenant ID and user count per role.

    • See IDM Service API Calls 5.1.1 for additional details.

  • GET /suite-idm/api/v1/admin/users?roles=SUITE_TENANT_ADMIN 

    • This new API lists the email address of all tenant admin roles for maintenance and event notifications.

    • The roles enumeration accepts any role listed in the Suite Admin as a valid entry.

    • See IDM Service API Calls 5.1.1 for additional details.

  • DELETE /suite-idm/api/v1/tenants/id?force=true 

    • This new API option (force=true) forces a resource deletion even if resources are still attached to the requested tenant.

    • See IDM Service API Calls 5.1.1 for additional details.

Documentation

The following documentation changes were implemented in CloudCenter Suite 5.1.0:

Known Issues

CloudCenter Suite 5.1.1 has the following known issues:

  • CloudCenter Suite 5.1.1 only supports air gap environments with proxy services. See Without Internet Access for additional details. Any isolated environment without proxy services is not supported.

  • When configuring the VMware vSphere Appliance Setup, use lowercase characters when providing the installer hostname in the Customize vApp Properties page.

  • 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.

  • When configuring a Backup, you cannot change the cloud account at any point in the process.

  • After upgrading from Suite Admin 5.1.0 to 5.1.1, Kibana may not be accessible. To workaround this issue, you must delete the Kibana Index file and restart the Kibana pod in your Kubernetes cluster as described in the following procedure.

    1. Access any of the pods in your Kubernetes Suite Admin cluster (for example, the license pod) using the following command.

      kubectl exec -it common-framework-suite-license-0 -n cisco /bin/bash
    2. Delete the Kibana index file using the following command.

      curl -XDELETE http://suite-logging-elasticsearch-2:9200/.kibana_1
    3. Exit this Kubernetes Suite Admin cluster pod that you just accessed.

    4. Restart the Kibana pod (search for exact name using the kubectl get pods -n cisco | grep kibana string) using the following command.

      kubectl delete pod <kibana pod name> -n cisco
    5. Wait for approximately 30 seconds for Kibana pod to come up.

    6. Once the Kibana pod is up and running, access Suite Admin > Dashboard > View Modules Details > View Logs Kibana.

    7. Kibana will be accessible at this point.

    8. Import the attached search filters file to the Kibana Application > Management > Saved Objects > click the Import link > then click Import within the Import saved objects pane and finally select the attached JSON file.
      kibana-searches_2.json

    9. Once you select the attached file in your Kibana application, click the Import button at the bottom of the Import saved objects pane.

You have now deleted the Kibana Index file, restarted the Kibana pod, and imported the search filters in your Kubernetes cluster.

Resolved Issues

This release includes fixes for internally found issues that do not change the product behavior in any way.



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