Skip to Main Content
Cloud Management and AIOps

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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace IBM Turbonomic ARM
Categories General/Other
Created by Guest
Created on May 17, 2023

Allow staggering of high impact changes

  • App teams: "we cannot have these X number of vms down at the same time"

  • Infra engineers: "we cannot support manual policy creation for each execution schedule for each set of X VMs to reboot in the same CHG window"


We have many use cases for applications that need to be staggered when we perform maintenances that require reboots. It would be great if we could have a way to create groups for these apps and allow a configuration field that allows you to adjust several things

  1. Turn on/off staggered reboot

  2. Specify how many (and which, perhaps by regex or assigning order or something) VMs at maximum can be down at one time

  3. The minimum amount of time after previous VMs are up until it triggers the next set, until execution schedule is over.

Ex: Group of VM1-VM6, only 2 can be down at once, staggered an hour apart. GroupMembership=(VM[1-6]), MaxPerCycle=2, CycleTime=60 (min)

Idea priority High