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
IBM Turbonomic ARM
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)
Turbonomic VLAN ID Merge and Mapping for vCenter portgroups with different names but same VLAN IDs
Our superclusters are spread between two VDS within vCenter, 1 for our legacy 10gbe network and the other for our 25gbe ACI network. vCenter requires the port group names to be unique and the unique naming is preventing Turbonomic from merging the...
Constrained vCPU VM's from Azure taken into consideration for recommendations
Azure has a class of VM's that have constrained vCPU's for DB vm's that often require high memory, storage and IO bandwidth, but not high core count. So the VM class will basically only use a portion of the core count for that class to save money ...
Extend the concept of consistent sizing for grouped servers to storage on the grouped servers. For instance, if i have servers in a cluster or servers that have been grouped together via tagging and rule, if there is a recommendation for storage, ...
Put all actions together, regardless of whether they are complete or not
If there are some actions that you're trying to monitor within one change window and some take longer than others, or some don't trigger until a later time, or whatever other reason there might be, you will be in a place where your actions and exe...
Customer is using Turbo to migrate VMs from one storage cluster to another. They want to set action concurrency via the UI for the automation policy without impacting the global concurrency settings. For their use case, they wanted to always see 5...
Ability to freeze generated actions for a specific group
I would like the ability to freeze the generated actions for a specific group so that when we notify resources owners of the action a week prior, we take that specific action or none at all on their resource. For example: We sent out notifications...
Consistent Resizing based on Example / Template Server Group-
We'd like to request an enhancement to the "Consistent Resizing" feature that would allow an "example" or "template" server group to drive the sizing actions of several other linked groups. We would like to be able to divide our servers into diffe...
Group the actions in ServiceNow - and then let the App Owner approve the VM rightsize actions from the one CR.
Group the actions in Snow - and then let the App Owner approve the VM rightsize actions from the one CR. And is able to select some or all of them.
Otherwise the app owners will get deluged with multiple individual changes coming in to approve/rej...
Do not place IBM confidential, company confidential, or personal information into any field.