Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management 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
Categories Action Automation
Created by Guest
Created on Oct 3, 2023

Add an "at least" option to go up to maximum when scaling up and down to minimum when scaling down

Today, Turbonomic calculates the desired sizing of a VM and then generates an action to go there. Currently if there's a minimum set in a policy, Turbonomic could just discard the action if the Desired State is below the minimum and then not resizing at all. Let's take an example:

- We have a VM with 40 Gb of vMem and we set a minimum of 32 Gb of vMem in the policy for resizing that VM

- Turbonomic looks at the percentile and usage and considers the VM could do the job with only 8 Gb

==> Turbonomic wants to generate an action going from 40 Gb to 8 Gb, but as 8 Gb is below the minimum of 32 Gb set in the policy, it's "discarding" the action and not generating anything, so the VM is never going to be resized down.

With a new toggle, we would like to give the instruction to Turbonomic to resize down to "at least" 32 Gb if a resize down is doable.

Same thing of course for resizing up.

Idea priority High