Skip to Main Content
Cloud 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 Submitted
Workspace IBM Turbonomic ARM
Categories Policies
Created by Guest
Created on Aug 27, 2026

VM Redundancy and Placement Affinity during Superclustering

VM Redundancy - Customer needs a way to spread certain workloads around cluster. IE - multiple DB workloads cannot exist on the same host due to risk aversion policies internally. Turbo has no way of mapping this automatically without creating hundreds of Do Not Place policies on a per VM basis. Customer needs to be able to configure "This set of VMs (DB Workloads) must be equally distributed across the hosts on this cluster". 

VM Anti-Affinity - Customer is concerned with VMs moving onto clusters they shouldn't be on after a prior cross cluster move. ie -- VM1 exists on Cluster 1(C1). C1 VMs should not move to C3, but are allowed to move to C2. VM1 is moved to C2. Because DNP policies are defined by the cluster/host origin and not at the VM level, this VM now has no policy dictating it cannot move to C3 and may get accidentally scheduled onto a C3 host. We need a way of keeping affinity attached to the workload rather than the cluster/host level. This can be done via tagging, but creating tags for a large environment is difficult. Automated internal tags should be added to VM entities in turbo such that when a DNP policy is created even at host/cluster level, the associated VMs permanently inherit that constraint as well until otherwise removed. 

Idea priority Medium