Feature updates and notices

Recent updates to Turbonomic include changes to resolve a currency symbol mismatch that affected billing data for MCA customers billed in non-USD currencies. After updating from version 8.17.5 or earlier to 8.17.6 or later, customers may experience delayed billing data discovery and action generation. In some cases, stale actions may persist for 2 to 3 days while Turbonomic processes and reconciles the updated billing data.

Note that this behavior is typically minimal and may not be noticeable in most environments.

Starting with version 8.17.6, the following container platform node constraints are temporarily disabled:

• GPU memory target utilization

• GPU target utilization

• vCPU limit target utilization

• vCPU request target utilization

• vMem limit target utilization

• vMem request target utilization

These settings will be re-enabled in a future release, along with improvements to their functionality.

Note that for versions 8.16.5 to 8.17.5, it is highly recommended to reduce the node vCPU and vMem request values from 90% to 70% to prevent pod move failures.

Starting with version 8.17.5, an additional cluster was introduced in the AWS Asia Pacific (Tokyo) region. The URLs for the new cluster are as follows:

• Subdomain URL:

  xxxxxx.apne1h.turbonomic.ibmappdomain.cloud

• OIDC provider URL:

  https://oidc.op1.openshiftapps.com/2ll72b5mnpgk6c4gio2nhl7fi99edtqm

If the subdomain URL for your Turbonomic SaaS instance is xxxxxx.apne1.turbonomic.ibmappdomain.cloud, no action is required. You can continue using your instance and its associated OIDC provider URL as usual.

Starting with version 8.17.5 , the following Google Cloud permissions were removed from the documentation because they are no longer required.

• compute.disks.setLabels
• compute.instanceGroupManagers.resize
• compute.instances.setLabels
• compute.instances.useReadOnly
• compute.instantSnapshots.list
• compute.regionInstanceGroupManagers.resize
• compute.regionInstanceGroupManagers.update
• compute.reservations.list
• compute.resourcePolicies.use
• compute.snapshots.delete
• compute.snapshots.list
• compute.snapshots.useReadOnly

In version 8.17.3, the Google Cloud permissions listed in the documentation were updated to include descriptions. These descriptions explain how Turbonomic targets use the permissions to discover and optimize your workloads.

For more information, see Reference: Google Cloud permissions.

Starting with version 8.17.4, the following AWS permissions were added to the documentation. These permissions are required to scale virtual machines in Auto Scaling Groups.

• ec2:CreateTags
• ec2:RunInstances

In version 8.17.3, the AWS permissions listed in the documentation were updated to include descriptions. These descriptions explain how Turbonomic targets use the permissions to discover and optimize your workloads.

For more information, see Reference: AWS permissions.

Turbonomic operator now supports Network File System (NFS) storage, introducing flexibility to control storage preferences using the Custom Resource (CR). NFS storage is a supported option for Turbonomic deployed in OpenShift, Azure AKS, Amazon EKS, and Google Cloud GKE.

VMware Horizon target

The VMware Horizon target and related documentation are restored with version 8.17.2. This target was removed previously beginning with version 8.15.5.

If you deleted a Horizon target following the removal announcement in version 8.15.5, you can add the target back from the Target configuration page in the UI.

• Action disruptiveness and reversibility for Amazon Redshift
• Action disruptiveness and reversibility for Azure Cosmos DB

Due to a change in the Content-Type header value that the AppDynamics API expects, Turbonomic updated its OAuth support for this target. If you use OAuth authentication to connect to an AppDynamics target, upgrade to version 8.15.2 so that Turbonomic provides the required Content-Type header value.

Buy RI actions are disabled in the real-time market and are no longer displayed in the Action Center. These actions will be reintroduced in a future release along with improvements to the existing analysis.

You can run Buy VM Reservations plans to view new Buy RI actions.

Prometurbo deployments before version 8.12.4 automatically added Data Ingestion Framework (Prometheus) targets to the Custom category. After you update to version 8.12.4 or later, existing Data Ingestion Framework (Prometheus) targets are cloned and the clones are then added to the Observability category. The original targets remain in the Custom category but are now undiscoverable. Remove them immediately to clean up your targets list and avoid seeing target discovery failures.

Legacy data is available in the legacy savings and investments charts. The charts are titled 'Legacy' so you can distinguish them from the enhanced charts.

Currently, only VMware vCenter fully supports these features. The documentation has been updated accordingly.

For details, see Azure permissions.

If you have changed your default setting to 1 or want to keep the current default setting of 2, create a new policy that is scoped to all on-prem VMs and configure the Rate of Resize to your wanted setting.