IBM System Storage Ideas Portal
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).
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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
What we need is some empowerment of APIs.
There is NO coverage for Clusters. Cluster should be supported the same way hosts are.
Cluster reading
Associated hosts
Mapped volumes (shared mappings)
Cluster creation and removal
Adding hosts to cluster and removing hosts from cluster
Mapping and unmapping volumes on clusters (shared mapping)
It appears quite strange that a cluster do not have an ID that uniquely identify it. The only identifier appears to the name. If and ID exists it should be exposed to external interface.
API coverage for volumes need to be slightly empowered
When a volume is created using the API there is no possibility to impose its code (LSS + offset). This is only possible using the Cli (mkfbvol)
APIs do not supply the UUID of volume (when it is created or read) We are forced to resort to the Cli just to obtain this essential information (lsfbvol and showfbvol)
There is no way to read ALL volumes without specifying Host/Pool/LSS/… . Again there is no simple equivalent of the Cli (lsfbvol -l)
Other improvements would also be highly beneficial but I suspect they would require more work on internals. I’m just mentioning the most relevant of all that required us a huge work to circumvent the problem
Volumes should have a Name that allows to uniquely identify them, not just a label. Name length need to be reasonably long (64 chars).