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 May 23, 2017

No root authority needed on storage for DRO alone

Client wants to use PowerVC for its sole DRO functionality. No short term plan for deploying VMs with PowerVC. Nevertheless, PowerVC requires "root" authority on storage and SAN linked to the partitions. Due to client's organization and needs, this is a show stopper. Even though PowerVC needs all information for the managed partitions, could you change the requirement in this case for Read Only since nothing will be modified on the storage/SAN side.
Thank you.

Idea priority Urgent
  • Guest
    May 26, 2017

    Thank you for the suggested enhancement - we will consider this for a future release. In general, the primary objective of PowerVC is to automate the provisioning process such that you can quickly provision and de-provision your cloud infrastructure - hence the dependency on the underlying storage infrastructure. That said, we do recognize there are situations in which users want to restrict operations that would result in "write" operations to the SAN.

    To that end, we want to ensure folks are aware of what can be done with the product as it currently exists to help mitigate this issue. PowerVC has built the concept of "roles" [1] that allow admins to restrict the types of operations that users can perform within PowerVC. For example, there is a "vm_user" role that allows a VM to be started, stopped, etc., but does not allow anyone to deploy new VMs, create volumes, etc.


    Thanks again for your interest in IBM PowerVC!