Skip to Main Content
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
  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 (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.

Status Future consideration
Workspace IBM Turbonomic ARM
Created by Guest
Created on Jan 26, 2026

Azure DB Non-Disruptive notice

Azure DBs scale actions states that the change is "Non-Disruptive", technically there is no downtime in that the database doesn't go down during the change, though there could be a connection drop and re-connect during the change. 

Following the Azure documentation: https://learn.microsoft.com/en-us/azure/azure-sql/database/scale-resources?view=azuresql "Azure SQL Database and Azure SQL Managed Instance enable you to dynamically add more resources to your database with minimal downtime; however, there is a switch over period where connectivity is lost to the database for a short amount of time, which can be mitigated using retry logic."

So this should be advised somehow in Turbonomic.

As suggested by Joby Joseph, this doesnt need to be a black-and-white Disruptive Yes/No, we should probably have a color coded status there:

  1. Non-Disruptive (Green) -> We should only use this if we know that there is NO downtime at all during the action execution. Meaning apps will retain their connectivity.
  2. Minimally-Disruptive (Orange) -> There might be short periods of time when there may be a connectivity loss, apps should handle it accordingly.
  3. Disruptive (Red) -> There will be a noticeable period of time when the VM/DB is unreachable while its size is getting updated, and apps should plan accordingly.

If we don't use Non-Disruptive option correctly, we may risk losing trust with customers

 

 


 


 

 


 


 

Idea priority High