Skip to Main Content
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
  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 (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.

Status Planned for future release
Created by Guest
Created on Feb 3, 2023

To simplify the deployment of workloads in the cloud, IBM must improve the performance of the Scale command "mmaddnode" to allow for faster spin up/down of resources.

Nodes in the cloud need to be spun up quickly as needed.  Currently mmaddnode takes too long to add a significant number of nodes as it sequentially adds nodes to the cluster; not only that, but other commands like mmchlicense, mmchnodeclass, and mmchconfig can also take a long time due to locks on the SDR.  This means that node provisioning often timeouts before the nodes are in the cluster and ready to be used.  These operations need to be able to complete much faster – and maybe it would be appropriate to have options to mmaddnode to include setting licenses and becoming members of a node class.

Cloud nodes are expected to have a dynamic IP address; adding new nodes to the cluster with an IP address that has been used before requires the initial entry to be deleted first with mmdelnode. mmdelnode suffers from the same serialization issues as mmaddnode so any solution should cover both the addition and removal of nodes. Perhaps mmaddnode could be enhanced with an --ephemeral-ip-address switch that would take care of deleting any stale entries (or simply override them.)

Idea priority Urgent
  • Guest
    Reply
    |
    Feb 24, 2023

    +1 to this proposal, as it is the key blocker to running in dynamic cloud environments where clients dynamically grow and shrink very quickly.


    I would add that ideal behavior would be similar to NFS, where all packages and config information is pre-packaged into a VM Image, and all permission/security info is pre-configured on the storage cluster, so that when a gpfs client VM starts, the only command required to access the storage cluster is to mount the fs....and unmounting (or VM shutdown) simply removes the client from the cluster (although running some simple startup/shutdown script on the client VM may also be reasonable)