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
Created by Guest
Created on Jun 20, 2024

Add support for vSAN Witness host

Implementing vSAN Stretched Clusters in a VMware vSphere environment requires setting up a witness host storing all meta data but hosting no VMs and acting as a quorum in a split brain situation (see https://core.vmware.com/resource/vsan-stretched-cluster-guide#vsan-stretched-clusters-vs-fault-domains). 

Turbonomic is discovering the Witness host as a host outside the cluster without an VMs running and is therefore recommending to suspend the host. The current workaround is setting a policy to prevent generating this action. Witness hosts implemented as virtual appliances (nested ESXi) can easily be identified by Model = ".*VMware.*" and maybe Number of hosted VMs = 0, but physical witness host cannot be grouped easily as you cannot group by field not existing for an entity like cluster name. Thus, the workaround needs to be applied or at least verified per cluster.

Please add the support for discovering witness hosts and automatically disabling suspend actions on those hosts.

Idea priority High