Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace IBM Turbonomic ARM
Created by Guest
Created on Sep 15, 2025

Consistent sizing: Show group member(s) with highest utilization which determine size of the group

In Turbonomic UI you don't have a chance to easily identify the member of a consistent resizing group with the highest load which determines the VM size for the group. This becomes almost impossible when comparing VMs running on hosts with different HW/CPUs, maybe resulting in different numbers of vCPUs.

Sample from IBM demo environment SE1 for which screenshots attached:

For this sample a group containing the 3 master nodes of an unmanaged K8s cluster where the three VMs have a different target size was created and a consistent resizing policy for that group.

See the attached screenshot for the pending actions before the policy took effect. Thus, Master2 will determine the sizing of the group (See also the screenshot of the top VMs widget for reference).

After the policy was applied the actions looked like this (see attached screenshot): All of the 3 group member shall be scaled to the same size as there is no difference in CPU type, but in the action details e.g. of node 0 (see screenshot) you are seeing that this action is part of a autoscaling group (which is misleading name in an on-prem environment) but you cannot identify the reason for the target size without going to the group and check e.g. the top VMs widgets. Thus, the proof-it-ui/action details are not helpful in this case for validating the action.

It would be great to get the hint that master2 is determine the size of the group and have at least  a like to this VM’s details or even better have the VM comparison directly in action details because this group is scaled as one entity.

Idea priority High