Cost Optimizer 5.1.2 Release Notes
First Published: November 14, 2019
December 11, 2019: Updated the Documentation section to include a list of pages that were modified.
Installation and Upgrade
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.
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.
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.
The supported cloud families are as follows:
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.
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.
For 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.
All tags are fetched and displayed as disabled in Cost Optimizer. You must manually enable the tags.
See Cost Optimizer API for additional details.
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.
The following issues were resolved/addressed in Cost Optimizer 5.1.2:
CSCvs08194: Cost Optimizer does not implicitly enable AWS tags.
Resolution: In Cost Optimizer 5.1.2, Cost Optimizer does not fetch AWS tags associated with a resource.
The following documentation changes were implemented in Cost Optimizer 5.1.2:
Tag-Based Cost Reporting (updated for technical accuracy about disabling of AWS tags)
Configure an AWS Cloud > Add an AWS Cloud Account, Configure an AzureRM Cloud > Add an AzureRM Cloud Account, Configure an IBM Cloud > Add an IBM Cloud Cloud Account, Configure a Google Cloud > Add a Google Cloud Account(updated for technical accuracy about incur expenses to retrieve cost data for Reporting accounts)
Cloud Overview > Minimum Permissions for Public Clouds (updated for technical accuracy about enabling AWS Cost Explorer to view AWS-specific costs)
Cloud Overview > Minimum Permissions for Public Clouds (updated for technical accuracy)
- No labels