What’s New

Turbonomic 8 is powered by a robust architecture that enables the core platform to scale with large application and infrastructure environments in a single-instance deployment. This eliminates complexity and provides scale-on-demand capabilities, while continuing to assure application performance and health.

Note:

Frequent changes to the product or third-party targets require that some features are updated, deprecated, removed, or no longer supported. For more information about these features, see Feature Updates and Notices.

Version 8.13.6

  • Sustainability Liveboards in SaaS Reporting

    The following Liveboards are now available in SaaS Reporting to help you gain insight into how you can reduce your carbon footprint and energy usage.

    • Sustainable IT Dashboard – Private Cloud

      This Liveboard focuses on the energy usage and carbon footprint of hosts. It also shows opportunities to reduce usage and footprint by executing Turbonomic actions.

    • Application Carbon Footprint – Private Cloud

      This Liveboard focuses on the energy usage and carbon footprint of VMs. The Top Applications by Carbon Footprint view provides insight into the carbon dioxide equivalent (CO2e) emissions of the VMs that power your applications. The Liveboard also shows opportunities to reclaim resources by executing VM resize actions, as well as optimization opportunities that can help reduce usage and footprint further.

    Note:

    SaaS Reporting is available to customers who use a SaaS instance of Turbonomic and customers who use a self-hosted instance and are participating in the private preview of SaaS Reporting.

  • Data Retention Settings for Executed Actions

    To optimize storage for your Turbonomic instance, this release introduces the following data retention settings and default values for actions that were executed in your environment:

    • Succeeded actions – Each action is retained for 1,095 days (3 years) and then purged.

    • Failed actions – Each action is retained for 90 days and then purged.

    • Maximum failed actions – A maximum of 200,000 actions are retained at any given time. When this number is exceeded, Turbonomic starts to purge the oldest actions.

    If you have a self-hosted instance of Turbonomic, you can change the default values in the Data Retention section of the Maintenance page. Note that more storage is required if you increase the values. If you have a SaaS instance and need to change the default values, contact your Turbonomic representative for assistance.

  • Parking Actions for Azure Virtual Machine Scale Sets

    This release introduces parking actions for Azure Virtual Machine Scale Sets. With these actions, you can stop Virtual Machine Scale Sets temporarily to reduce your cloud expenses and then start them later when you need them. You can enforce these actions in the following ways:

    Note:

    In the supply chain, Virtual Machine Scale Sets are presented as Virtual Machine Spec entities. To view details for a Virtual Machine Scale Set, scope to a Virtual Machine Spec and then check the Entity Information chart.

    To take advantage of this feature, add the Microsoft.Insights/AutoscaleSettings/Read permission to the Azure service principal for Turbonomic.

  • Discovery of Azure Savings Plans

    Turbonomic now discovers the Azure savings plans that you purchased for your workloads. Use the Discount Inventory and Discount Coverage charts to view information for these savings plans.

    For more information, see Discount Inventory (Azure Savings Plans) and Discount Coverage (Azure Savings Plans).

    To enable the discovery of savings plans, add the Microsoft.BillingBenefits/savingsPlanOrders/savingsPlans/read permission to the Azure service principal for Turbonomic.

  • Enhanced Support for Azure Confidential VMs

    This release enhances support for Azure confidential VMs in the following ways:

    • Turbonomic now supports the Azure DCsv2, DCsv3, and DCdsv3 instance type series for confidential VMs and groups these instance type series under the Confidential Computing category.

    • A new read-only policy called Azure VMs with Confidential Computing Type: SNP is now available. This policy prevents confidential VMs on instance types that use Secure Nested Paging (SNP) from scaling to instance types that do not support SNP. For example, a VM on Standard_DC2as_v5 can scale to Standard_EC2as_v5 since both instance types support SNP. The same VM cannot scale to Standard_DC2s_v2, which does not support SNP.

  • Improved Management of Cloud Instance Types in Cloud Policies

    When you configure cloud instance types as a scaling constraint in cloud policies for VMs, VM Specs, Volumes, Databases, and Database Servers, you can now use an inclusion or exclusion list to define instance types more quickly. For example, if 400 instance types are currently available for scaling but you want to prevent scaling to 20 instance types, configure an exclusion list and select those 20 instance types.

    Note:

    After you update to this version, any instance types that you previously configured for exclusion continue to be excluded. No additional configuration is required. For example, if you previously unselected 20 instance types to exclude them from scaling, you will notice that the exclusion list is turned on by default after the update and the 20 instance types are now selected for exclusion.

  • Enhanced Cloud Savings and Investments Charts

    The cloud savings and investments charts are now migrated to the new design for the user interface. For these charts, the Show All view includes the following enhancements:

    • A stacked bar chart or area chart now displays in the view.

    • The table in the view now shows detailed information for the accounts, regions, entity types, and action types in scope. This information is now easier to view using a horizontal scroll bar. You no longer need to expand a row in the table to view the information.

    • If you filtered the data by a specific group, the table now provides a Search functionality to help you narrow down the data further. For example, if you filtered by account, you can search for accounts by specifying an account name as your keyword. Partial keyword matching is supported.

      The following groups are supported:

      • Account – Cloud accounts discovered in your environment

      • Action Type – Scale and delete actions

      • Cloud Service Provider – AWS, Azure and Google Cloud

      • Entity Type – Virtual Machine, Volume, Database (Azure only), Database Server (AWS and Azure only), Document Collection (Azure only), Virtual Machine Spec (Azure only)

      • Region – Regions for the entities

      • Resource Group (Azure only) – Available resource groups in your environment

      • Tag – Tag values for a given tag key

        Select a tag key from the list. For AWS, the tag keys are limited to cost allocation tags.

Version 8.13.5

  • New Design for the Turbonomic User Interface

    The new design for the Turbonomic user interface is now enabled by default. This design is powered by IBM Carbon and is intended to bring a consistent style and tone to Turbonomic. It creates a more effective communication, reduces learning curve, and enables a seamless transition if you are using other IBM products.

    The new design is a work in progress and is currently implemented for certain features and pages in the user interface. For more information, see New Design for the User Interface.

  • Scale Actions for Google Cloud VMs Running E2 Custom Machine Series

    Turbonomic can now generate scale actions for Google Cloud VMs running E2 custom (including shared-core) machine series to optimize performance at the lowest possible cost.

  • New and Improved Parking Page Filters

    You can now use the following filters in the Parking page to narrow down the list of parkable entities:

    • Service name – Use this filter to show entities for specific cloud services.

    • Unparkable – Use this filter to show entities that are currently unparkable. These entities are unparkable because they apply policies that disable parking actions.

    In addition, parking filters now show valid values in a dropdown list and support partial keyword matching to help you narrow down parkable entities with ease. You can continue to use regular expressions as usual.

  • Discovery and Maintenance of vSAN Minimum Host Requirements

    VMware vSAN storage clusters require a minimum number of hosts that contribute capacity to the cluster. Turbonomic now automatically discovers the minimum host requirements for a vSAN cluster and treats them as placement constraints in its analysis. With this capability, Turbonomic can generate more accurate workload placement recommendations in the real-time market and plans. This capability is enabled by default and no new configuration is required.

Version 8.13.4

  • Support for Azure SQL Managed Instances

    Turbonomic now discovers Azure SQL Managed Instances and presents them as Database Server entities in the supply chain. Turbonomic generates non-disruptive and reversible scale actions for SQL Managed Instances to optimize performance and costs. For more information, see Database Server - Azure SQL Managed Instance.

    To take advantage of this feature, add the following permissions to the Azure service principal for Turbonomic:

    • Microsoft.DatabaseWatcher/watchers/read

    • Microsoft.DatabaseWatcher/watchers/targets/read

    • Microsoft.Sql/managedInstances/read

    • Microsoft.Sql/managedInstances/databases/read

    • Microsoft.Sql/managedInstances/metrics/read

    • Microsoft.Sql/managedInstances/write

    In addition, configure Azure database watcher to enable the collection of metrics for SQL Managed Instances. Turbonomic requires these metrics to generate memory scaling actions. For more information, see Azure SQL Metrics Collection Using Database Watcher.

  • Support for Azure VMs Running GPU Instance Types

    Turbonomic now discovers NVIDIA GPU metrics for supported Azure GPU instance types and uses these metrics to generate VM scale actions that optimize performance at the lowest possible cost. Currently, Turbonomic supports the following Azure instance type series that use Linux source images.

    • NC A100 v4

    • NCads H100 v5

    • NCasT4_v3

    • NCv3

    • NDv2

    • NVadsA10 v5

    • NVv3

    For more information, see Scale Actions for Azure VMs Running GPU Instance Types.

    To enable the discovery of GPU metrics, configure NVIDIA Data Center GPU Manager (DCGM). For more information, see Azure GPU Metrics Collection.

  • Newly Supported Azure Instance Type Series

    This release introduces support for the following Azure instance type series for standard VMs.

    • Basv2, Bpsv2, Bsv2

    • Dldsv5, Dlsv5, Dpdsv5, Dpldsv5, Dplsv5, Dpsv5

    • Ebdsv5 (E96bds_v5 and E112ibds_v5), Ebsv5 (E96bs_v5 and E112ibs_v5), Epdsv5, Epsv5

    • FX

    • Lasv3, Lsv3

  • Improved Action Generation for Unattached Cloud Volumes

    When Turbonomic discovers unattached AWS, Azure, or Google Cloud volumes, it now waits an hour before generating volume delete actions. This improvement aligns with the volume deletion policy seen in many organizations.

    To change the default waiting period of one hour, contact your Turbonomic representative.

    For more information, see Generation of Delete Actions for Unattached Volumes.

  • OAuth 2.0 Authentication Enabled by Default

    The OAuth 2.0 feature, which provides an easier way to programmatically authenticate with Turbonomic APIs, is now enabled by default. You can now use the Turbonomic API to create, list, and delete OAuth 2.0 clients without having to enable the feature or declare an audience value in your API call.

    For more information, see Authenticating OAuth 2.0 clients with the API.

Version 8.13.3

There are no new features in this release.

Version 8.13.2

  • Automation of Scale Actions for GenAI Large Language Model (LLM) Workloads Served by KServe

    Turbonomic can now automate scale actions for GenAI LLM workloads served by KServe in Red Hat OpenShift AI. Turbonomic automatically detects and updates the minimum and maximum replicas to the values configured in the InferenceService spec in KServe. The KServe controller then scales the workloads accordingly.

    No additional setup is required to enable KServe support in Turbonomic.

    For more information, see Scale Actions for GenAI LLM Inference Workloads.

Version 8.13.1

  • Parking Actions for AWS Auto Scaling Groups

    This release introduces parking actions for AWS Auto Scaling groups. With these actions, you can stop Auto Scaling groups temporarily to reduce your cloud expenses and then start them later when you need them. You can enforce these actions in the following ways:

    To take advantage of this feature, add the following permissions to the policies for the IAM role or user that you set up for Turbonomic:

    • autoscaling:DescribeLaunchConfigurations

    • ec2:DescribeLaunchTemplateVersions

    Note:

    In the supply chain, Auto Scaling groups are represented as Virtual Machine Spec entities. To view details for a group, scope to a Virtual Machine Spec and then see the Entity Information chart.

  • New User Role

    This release introduces a new user role called Parker. Users with this role can park workloads on demand, manage parking schedules, and view all Turbonomic charts and data. However, these users cannot place workloads, create policies and templates, run plans, and execute any recommended actions.

  • Improved Cost Analysis for AWS VMs Covered by Compute Savings Plans

    Turbonomic now considers your Compute Savings Plans inventory when it calculates the cost impact of scale actions on AWS VMs. This improvement results in more accurate projected savings for VM scale actions.

    To take advantage of this improvement:

    1. Add the savingsplans:DescribeSavingsPlansOfferingRates permission to the policies for the IAM role or user that you set up for Turbonomic.

    2. Specify the purchase profile for your Compute Savings Plans. Navigate to Settings > Billing and Costs, click the AWS discounts tab, and then scroll to the Compute savings plans section.

    For more information, see AWS Discounts - Compute Savings Plans.

Version 8.13.0

  • Container Resource Management

    • Scale Actions for GenAI Large Language Model (LLM) Inference Workloads

      For GenAI large language model (LLM) inference workloads that use GPU resources and are deployed in a Kubernetes cluster, Turbonomic can now generate workload controller scale actions to maintain Service Level Objectives (SLOs) for these workloads.

      For more information, see Scale Actions for GenAI LLM Inference Workloads.

    • Node Provision and Suspension Actions for Google Kubernetes Engine (GKE) Clusters

      For nodes in a Google Kubernetes Engine (GKE) cluster, Turbonomic can now generate node provision actions to address workload congestion or meet application demand, and node suspension actions to improve infrastructure efficiency.

      For more information, see Node Provision and Suspension Actions.

      To execute these actions, Turbonomic must be able to connect to your GKE cluster through a Kubernetes or Red Hat OpenShift target and a Google Cloud target. For the Google Cloud target, the service account requires the following permissions:

      • compute.instanceGroupManagers.update

      • compute.instanceGroups.get

      • container.clusters.get

      • container.clusters.update

      For the full list of permissions, see Permissions for the Google Cloud Target.

    • Enhancements for Container Pod Move Actions

      • This release enhances the mechanism for handling pod-to-pod affinity and anti-affinity. With this enhancement, Turbonomic can now generate more accurate container pod move actions that comply with affinity and anti-affinity rules, while continuously driving the target environments toward the desired state. To review these actions in Action Center, look for container pod move actions with an action category of Compliance and a risk of Unsatisfied Affinity Constraints or Unsatisfied Anti-Affinity Constraints.

        For more information, see Pod Affinity and Anti-affinity Rules.

      • When pod move actions execute, the pod clone process now copies and persists labels so that label constraints for the pods comply with any label-specific constraints that exist in the container platform cluster. This enhancement ensures that pod move actions can be successfully completed.

      • For Kubernetes or Red Hat OpenShift environments that have Security Context Constraints (SCC) in use, SCC support is now enabled by default. You no longer need to specify sccsupport="*" in Kubeturbo deployments to enable container pod move actions.

    • Improved Management of Prometheus Targets

      To align with industry terminology, the category name for the Prometheus target has changed from 'Custom' to 'Observability'.

      Turbonomic collects application metrics from Prometheus servers through the Prometurbo agent that you deploy to OperatorHub in Red Hat OpenShift. To help you deploy and manage Prometurbo with ease, this release introduces the following improvements.

      • In the user interface, when you navigate to Settings > Target Configuration > New Target > Observability > Prometheus, you will now see a guide that walks you through the Prometurbo deployment process, including the settings that you need to configure directly in OperatorHub. You do not need to configure any settings in the user interface.

        Note:

        The Prometurbo deployment guide is also available in the Turbonomic documentation. For more information, see Prometheus.

        The Prometurbo deployment guide in GitHub is no longer maintained and will be retired. Always refer to the Turbonomic documentation for the latest information.

      • After the deployment, Prometurbo automatically adds itself as a Prometheus target in the user interface, in Settings > Target Configuration. When you view the details for a target, you will now see read-only information about your Prometurbo deployment. To make changes, update the Prometurbo configuration in OperatorHub.

  • Cloud Resource Management

    • Enhancements for AWS VMs Running EC2 GPU Instance Types

      • Support for Additional NVIDIA GPU Metrics

        Turbonomic now discovers the following NVIDIA GPU metrics for AWS VMs running supported EC2 GPU instance types:

        • GPU FP16, FP32, and FP64

        • GPU Tensor

        • GPU Memory BW

        Turbonomic uses these metrics to generate VM scale actions that optimize performance and costs. You can view these metrics in the Capacity and Usage and Multiple Resources charts.

        For more information, see Support for AWS EC2 GPU Instance Types.

        To enable the discovery of these metrics, configure NVIDIA Data Center GPU Manager (DCGM). For more information, see Linux Configuration for NVIDIA GPU Metrics (DCGM).

      • Ignore NVIDIA GPU Compute Capability

        This constraint is a setting that you can choose to turn on in automation policies for AWS VMs. When this setting is turned on, scale actions that change the GPU compute capability of VMs are allowed to execute in Turbonomic.

    • Newly Supported AWS Instance Families and Regions

      This release introduces support for the following AWS instance families and regions.

      Instance families:

      • C6id, C6in, C7a, C7g, C7gd, C7gn, C7i

      • Hpc7g

      • I4g, I4i

      • M6id, M6idn, M6in, M7a, M7gd, M7i, M7i-Flex

      • R6a, R6id, R6idn, R6in, R7a, R7gd, R7i, R7iz

      • U-1 (High Memory) – u-18tb1 and u-24tb1 only

      Regions:

      • ap-south-2 – Asia Pacific (Hyderabad)

      • ap-southeast-4 – Asia Pacific (Melbourne)

      • ca-west-1 – Canada West (Calgary)

      • eu-central-2 – Europe (Zurich)

      • eu-south-2 – Europe (Spain)

      • il-central-1 – Israel (Tel Aviv)

      • me-central-1 – Middle East (UAE)

    • Support for AWS Standard Data Exports (CUR 2.0)

      The AWS Billing target can now retrieve billing data from a standard data export (CUR 2.0) that you set up in the AWS Billing and Cost Management console.

      If you previously set up a legacy CUR export for use with the AWS Billing target and now want to switch to the standard data export:

      1. Set up a standard data export. For more information, see Setting Up a Standard Data Export (CUR 2.0).

      2. In the Turbonomic user interface, remove your existing AWS Billing target and then add a new one. In the new target, specify the S3 bucket name, S3 path prefix, and S3 bucket region of the standard data export.

      Note:

      You can continue to use a legacy CUR export until further notice.

    • AWS RDS Data in Discount Charts

      For AWS RDS Reserved Instances (RIs), utilization and coverage data is now available in the Discount Utilization and Discount Coverage charts.

      Note:

      Currently, utilization data is not considered in database server scaling recommendations. In addition, Turbonomic does not generate actions to purchase RDS RIs.

    • Support for Azure Zone-redundant Storage (ZRS)

      Turbonomic now discovers Azure zone-redundant storage (ZRS) with Premium SSD and Standard SSD managed disks.

      Turbonomic can generate volume scale actions for ZRS to optimize performance and costs. If a ZRS is currently unattached, Turbonomic immediately generates a volume delete action as a cost-saving measure. Savings and investments associated with these actions are tracked in the Savings, Cumulative Savings, Investments, and Cumulative Investments charts.

    • Azure Billing Target Support for Azure Government

      The Azure Billing target can now discover and monitor billing data for Azure Government workloads. To ensure seamless monitoring of billing data, follow the guidelines outlined in Support for Azure Government.

      With this new capability, the Azure Billing target is now the only target that Turbonomic requires to monitor billing data for both global Azure and Azure Government workloads. The Microsoft Enterprise Agreement target is no longer required and has therefore reached end of support. If you have an existing Microsoft Enterprise Agreement target in the Settings > Target Configuration page in the user interface, remove the target immediately and then set up an Azure Billing target. For more information about end of support and next steps, see Notice: Microsoft Enterprise Agreement Target.

    • Azure Volume Delete Action Enhancement

      Turbonomic now checks the DiskState property of Azure volumes to accurately determine their attachment state. If the DiskState is Unattached, Turbonomic generates an action to delete the volume.

    • Scale Actions for Google Cloud VMs Running Custom Machine Types

      Turbonomic can now generate scale actions for Google Cloud VMs running custom machine types to optimize performance and costs. Currently, Turbonomic supports the N1, N2, and N2D custom machine series.

    • Historically-informed Action Generation for Google Cloud VMs

      Turbonomic can now generate VM scale actions informed by historical utilization data on the same day a new Google Cloud target is added.

      To take advantage of this feature, add at least one Google Cloud target. The service account for the target requires the logging.logEntries.list permission. For the full list of permissions, see Permissions for the Google Cloud Target.

      Note:

      Currently, VM scale actions consider historical utilization of all monitored resources, except I/O throughput.

    • Tracking of Externally-executed Cloud Actions

      Turbonomic now tracks actions for cloud workloads that you executed externally. For example, you may have executed these actions through your cloud provider.

      Use the following charts to view relevant data:

      • Savings, Cumulative Savings, Investments, and Cumulative Investments

        The total amounts shown in these charts now include savings or investments associated with externally-executed actions.

      • Executed Actions - Succeeded

        For externally-executed actions, the Execution column shows 'Executed Externally'.

  • On-prem Resource Management

    • Sustainability Metrics in VM Move and Host Suspend Actions

      For on-prem environments, Turbonomic now shows the projected change in carbon footprint and energy usage in the action details for VM move and host suspend actions. For host suspend actions, a new Energy Usage column in the Action Center summary also shows energy usage data for hosts. For more information, see Sustainability Metrics in VM Move and Host Suspend Actions.

    • Stitching Between Datadog and vCenter Targets

      When both Datadog and vCenter targets are added, VM entities will be stitched and a complete supply chain will be available.

    • Discovery of VM Virtual Disks for Nutanix Targets

      For Nutanix targets, VM virtual disks are now discovered and displayed as volume entities in the supply chain. The new Nutanix probe property (enableVolumeDiscovery) is enabled by default.

    • Handling of Duplicate Storage Targets

      This release implements a duplicate target check for storage targets. If you added duplicate targets, you will now see discovery errors to notify you to remove the duplicates.

  • Orchestration and IT Management

    • Support for ServiceNow Washington DC Release

      Turbonomic Actions for ServiceNow is an integration that brings the power of Turbonomic to your ServiceNow® Change Management application. Turbonomic Actions 1.1.11 now supports the ServiceNow Washington DC release. You can download this integration from the ServiceNow store. For more information, see the Turbonomic Actions for ServiceNow documentation.

    • Enhancements for Flexera Targets

      You can now target FlexNet Manager Suite 2023 R2 (on-premises) with Turbonomic to discover software license assets in the same manner as the existing Flexera One (SaaS) integration. By discovering software license assets, Turbonomic can more intelligently place or resize workloads to ensure compliance with licensing policies. Operations teams no longer need to manually define these constraints. Application owners will see optimized license usage in Flexera One and FlexNet Manager by using Turbonomic to optimize license consumption.

      The category name for the Flexera target has changed from "Orchestrator" to "IT Management."

      For more information, see Flexera.

  • User Interface Management

    • Telemetry and Usage Data Sharing

      After upgrading to this version, the Turbonomic telemetry and usage data sharing feature is automatically enabled. Telemetry data, including IP addresses and approximate geolocation, is sent automatically to IBM and/or its sub-processors. The data is only used by IBM for product development and feature improvement. You can opt out of the automatic telemetry data upload at any time by disabling it in the Settings > Maintenance Options > Telemetry Data Sharing page.

      For more information, see Maintenance Options.

  • API Management

    • Programmatic Authentication with Turbonomic APIs by Using OAuth 2.0 Tokens

      This release includes a new OAuth 2.0 feature, which provides an easier way to programmatically authenticate with Turbonomic APIs. You can now use the Turbonomic API to create, list, and delete OAuth 2.0 clients. After you create a client, you can programmatically exchange the client credentials for access tokens.

      For more information, see Authenticating OAuth 2.0 clients with the API.

    • Improvement for Searches that Use Regular Expressions

      If you used a regular expression (regex) to search for a group in the user interface and specified * as the first character, the /search API call now performs a regex validation to prevent errors with error code 500.