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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
Further consideration for this feature/addition/idea would be that I can specify members of GroupA can not live/placed on the same host as any members of GroupB.
Further consideration should be made to ensure that the VM-to-VM affinity policies will support movement between merged clusters (Superclusters). Today the imported DRS rules from cluster A do not exist in any other merged clusters, and therefore VMs configured to use these rules (if moved) will potentially be out of compliance
From a customer perspective/usability standpoint this should consider that a typical environment has these rules created within vSphere, that we import from. Our product being able to import these rules means that we could replace the entire process to create/edit/delete rules entirely into our platform, and the entire replacement should be possible. The primary reasoning is that Turbonomic can create more complex and more interesting rules that the underlying technology simply can't create (like affinity/anti-affinity cross-cluster, cross-vc, etc.) and from an end users perspective they would either want to manage all rules in vSphere, or if they were interested in the more advanced rules, manage all rules in Turbo instead.