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.
Specific links you will want to bookmark for future use
Add "Non-Disruptive" column to Action Center for On-Prem and Container actions
Today, in the Action Center for many Cloud scaling actions, we have a column highlighting whether the action is non-disruptive or not. This helps customers adopt Turbo's automation quicker, builds trust, and lowers the barriers to action execution.
The same tactic should be taken for on-prem and container actions. We oftentimes have to explain to customers that certain actions do not require downtime - immediately easing their concerns over the effort required to execute/automate actions. No downtime = easier to execute/automate.
Actions today that come to mind are:
VM Storage Moves
VM Resize Up (if hot-add is enabled)
Container Pod Moves
Some of these actions may seem obvious that they would be non-disruptive (like VM Moves), but there is no harm in emphasizing how painless it is to execute certain actions. "If you know it's non-disruptive, then why haven't you taken the action yet? :) "
Other actions, like VM Resize Up w/ Hot-Add are actually not obvious to end-users when looking at our Action Center. How do I know which VMs have hot-add enabled? Will this be non-disruptive or disruptive if I execute the action? Today, you have to navigate away from the Action Center, make a group of VMs and filter based on hot-add, and then view just that group's Action Center. With this new feature, the Action Center would make it obvious that a customer has pending VM Resize actions that are non-disruptive - and would help them prioritize executing those actions.
Lastly, Turbo's ability to move (schedule) container pods non-disruptively is such a new concept to people they are almost always unaware it. It's a huge opportunity to have our UX/UI inform the customer of Turbo's unique value prop.
Do not place IBM confidential, company confidential, or personal information into any field.