This portal is to open public enhancement requests against IBM System Storage 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
To provide some more technical background:
In systems with "topology:standard", when trying to create a clone from a snapshot (example use case: provisioning a VM in OpenShift, for example from template), we will use the mkvolumegroup command. However the mkvolumegroup command does not support a list of pools as argument, i.e. it is not possible to create a mirrored clone. Thus the command on the storage system would fail with a CMMVC error message ("CMMVC5754E The specified object does not exist").
However there are some clients with a requirement to have mirrored volume copies on the storage system (regardless of the topology), so in these environments it would be ideal if the CSI driver could work with two vdisk copies similar to enhanced stretched clusters (topology:stretched) or Hyperswap (topology:hyperswap). Usually the two pools used for the Volume Mirroring would be provided by two independent backend storage controllers. It provides redundancy in case one of the backend storage system fails.