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 Under review
Workspace IBM Turbonomic ARM
Created by Guest
Created on Sep 5, 2024

CPU scaling on vCPU not MHz

As I know Turbonomic is scaling vCPU based on the MHZ or GHz config of the underlying physical Host.

The problem with this is that we have some virtual machine groups with „consistent resizing“ but Turbonomic has actions for one vm to increase vCPUs to 3 while the others stay on 2. Thats based on the MHz, because the VMs without an action are running on a physical host with 2.8GHz CPU instead of 2.3 GHz CPU (the machine with an action). The problem with this is that we only scale based on vCPUs.

I get now questions from the application owners why they get actions for resizing despite we have configured consistent resizing.

Is there any way to change Turbonomic that he should ignore MHz and GHz and only look at the vCPU numbers?

Idea priority High
  • Guest
    Reply
    |
    Nov 14, 2024

    yes please