Skip to Main Content
IBM Power Ideas Portal

This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 PowerVC
Created by Guest
Created on Apr 18, 2019

PowerVC - versioning of instances

PowerVC provides Snapshot to capture disk of a vm or instance. This information does not include vm details (cpu memory network etc)
Capturing an image of a vm would include all data, but this feature doesn't provide a way to tie that image as a "backup" for a given vm or instance

Idea priority Medium
  • Guest
    Jun 15, 2020

    This is very similar to a request I was going to submit. Taking the traceability of an image further within the GUI with the capability to deploy older versions of an image.

    Eg. Today, I have an image for a base install of RHEL 7.6 LE, which I'll call RHEL7.6LE_v1.0. Today that image doesn't have RMC, which is an issue I'd like to fix in the near future. To make that new change, I would take the RHEL7.6LE_v1.0 image, deploy it. Once I have RMC enabled, I would capture it as a new image RHEL7.6LE_v1.1. Now I have two images in my list, which as we continue to add functionality / changes 1.2, 1.3 it starts to clog the repo list.

    Having this trackable, and reversible (using snapshots?) in a collapsible manner in the UI would be very helpful. That way I can eliminate the need for versioning, since we could add comments to the version tracking!

  • Guest
    Jun 10, 2019

    Thanks for the suggestion - we'll consider this for a future release