Skip to Main Content
Status Needs more information
Workspace * IBM Cloud Ideas
Categories Virtual Servers
Created by Guest
Created on Oct 16, 2025

When deleting a Virtual Server Instance (VSI), the default state of the "Release the VSN attached to this instance" switch should be set to OFF.

If the switch is left ON—whether due to oversight or misunderstanding—the Virtual Serial Number (VSN) will be released. This can lead to unintended consequences in scenarios where the VSN is intended to be retained for redeployment. For instance, when capturing an image of a Virtual Server Instance (VSI) to change its machine type, the absence of the original VSN prevents client applications from starting, as they rely on the data security related to that VSN
To mitigate this risk, the default state of the "Release the VSN attached to this instance" switch should be set to OFF, ensuring that the VSN is preserved unless explicitly released by the user.

Idea priority Medium
Needed By Yesterday (Let's go already!)
  • Guest
    Apr 10, 2026

    Hi Paulo thank you for the idea. Please provide some additional information by filling out the following fields so we can better understand the issue and priority. Thanks!


    "What"

    • Overview/Description

      • Problem: What problems are you focusing on solving?

      • Solution: What solutions to those problems are you focusing (High level)

    • Who-What-Wow (by persona) :

      • As a <specific persona... the who>, I need the ability to <objective... the what> <with a competitive, differentiating, measurable outcome... the wow>

    "Who"

    • Target Market:

    • Customer Segments/User Types:

    • Key Clients Requesting/ Sponsor Users:

      • Also update the sponsor user field

    • Partners/Seller Applicability:

    • Stakeholders (internal):

      • Identify Key Stakeholders and/or approvers

      • Key contacts including Product managers, Engineering, Design, Marketing, Sales etc.

      • Note: use Public Cloud Customer field to document specific client interest.

    ”Why"

    • Client Value proposition:

      • Document client value and why

        • Update in the "Value Statement" and obtain design approval

    • Business outcomes: Market share, revenue, financial implications

    • Easier to Consume / Easier to Sell - Document how this deliverable makes our Cloud easier to sell or consume

    • Competitive Position:

    Success Metrics/Exit Criteria

    • Quantifiable results -document quantifiable results for success

    • Acceptance Criteria

      • Specific condition that describe the conditions that define the completion of each feature.

      • If there is a beta - be clear on successful exit criteria for declaring completion of the beta.

    • Sponsor Users:

      • update sponsor users field in the Cloud OMD section