Cost Optimizer 5.1.3 Release Notes

Release Date

First Published: December 20, 2019

Installation and Upgrade

  • CloudCenter Suite:

    • Cost Optimizer cannot be installed separately and must be installed as a part of the CloudCenter Suite UI. See Suite Admin 5.1.1 release notes for additional details.

      If you upgrade Cost Optimizer, you must also upgrade Workload Manager and vice versa as both modules use the same shared APIs.

  • Cost Optimizer:

    • The Optimizer Admin can upgrade Cost Optimizer at the suite level to the latest version of the software. See Update Module for additional context. 

    • When upgrading to Cost Optimizer 5.1.0, it is recommended that you upgrade from Cost Optimizer 5.0.1 or Cost Optimizer 5.0.3.

  • Cloud Remote:

    • When updating to Cost Optimizer 5.1.0, you must also update all instances of Cloud Remote to Cloud Remote 5.1.0.

    • See Cloud Remote (Conditional) for additional details.

Clouds

The supported cloud families are as follows:

  • AWS

  • AzureRM

  • Google (GCP)

  • IBM

  • VMware

    • vCenter

    • vCloud Director

  • OpenStack

  • Kubernetes

See Configure Clouds for additional context.

Cloud Accounts shared by the parent tenant are only applicable to Workload Manager and are not displayed in Cost Optimizer.

Cost Optimizer UI

  • Browser Compatibility: See Browser Compatibility for a list of compatible browsers. 

  • Localization: Cost Optimizer is only available in the English language.

  • Refer to the Suite Admin for additional context on Suite Architecture and Administration and Governance.

  • Tag-Based Cost Reporting: Tag-based cost reporting is available for AWS and Azure clouds only. As part of the inventory, tags associated with corresponding resources are fetched from all cloud providers. See  Tag-Based Cost Reporting for additional details.

    • AWS

      • Cost Optimizer obtains all tags but does not fetch active tags associated with a resource. Effective with Cost Optimizer 5.1.2, AWS tags are disabled. To enable tags, you must set the toggle to ON in the Cost Reporting column against the tag for which you want to display the cost. Invoice collection is triggered 30 minutes after you have enabled the tag-based cost reporting at the top of the page. If you are using a version earlier than Cost Optimizer 5.1.2 and have enabled AWS tags for cost reporting, the specific tag will be displayed as enabled and the remaining tags will be disabled.

    • Azure

      • All tags are fetched and displayed as disabled in Cost Optimizer. You must manually enable the tags.

API

See Cost Optimizer API for additional details.

Integrations

As a part of cost optimizing recommendation, Cost Optimizer works seamlessly for resizing, suspending, stopping, and terminating an instance and unused volumes by working with Workload Manager in the backend. There is no need to navigate to Workload Manager for the above actions.

Known Issues

Cost Optimizer 5.1.3 has the following known issue:

When migrating from Cost Optimizer 5.1.0 to Cost Optimizer 5.1.3 Microsoft Azure invoices are not displayed until the Invoice Aggregation (see Data Collection) process is run at the scheduled time. This is because Microsoft Azure invoice records are deactivated as some changes were made with respect to the tracking of the start and end dates for the invoices. This change is specific to Microsoft Azure only.

Resolved Issues

The following issues were resolved/addressed in Cost Optimizer 5.1.3:

  • CSCvs49488: The Cost Group API (/api/v1/costGroupTypes) takes a very long time to load a large number of cost groups in the system.
    Resolution: Cost Optimizer 5.1.3 includes performance improvements to load a large number of cost groups.


  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks