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 updateson 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.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - including Orchestration and Performance Management
Cloud Pak for Watson AIOps - including Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - including IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - including Workload Scheduler
Tivoli System Automation - including Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
SuperClustering is one of the more unique & useful features that enables a lot of functionality across environments within Turbonomic. Unfortunately, it can be extremely cumbersome to implement SuperClustering due to requiring specific merge policies (datastore, cluster, & storage; and specifically storage requires SDRS clusters), as well as vCenter configurations - SDRS clusters, similarly named resource pools & DRS rule conflicts.
As a user, I'd like to see a SuperCluster policy implemented. What this policy would do is allow me to specify the clusters I'd like to merge and everything is considered automatically. Any storage that is available to the host, is available to use unless I specify Do Not Place policies for them. This would simplify troubleshooting as well, since any issues would not be related to policies unless I created them, as opposed to missing a configuration step or setting on vCenter.
Do not place IBM confidential, company confidential, or personal information into any field.