IBM Data and AI Ideas Portal for Customers

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:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Future consideration
Workspace Spectrum Symphony
Components Version
Created by Guest
Created on Mar 8, 2021

Ensure "egosh resource open" truly open a host to take new tasks by default

When Symphony opens a host, the common sense understanding of it is "open" means the host is open to "business" i.e. to new workload. However, the current Symphony host open feature is so that, if SOAM_CLOSE_NODE_GRACEFULLY=Y also true, then hosts will remain closed until all the workload that were still running before "open" finish. This behavior in our opinion is incorrect.

When Symphony was released from the beginning, the close feature (egosh resource close) behaves very much against common sesne: "close" means if new workload keep on coming to the allocation that includes the host, then the host can continue to be used i.e. stay open, until naturarally there is no new workload needing this allocation. This behavior seems to surprise every user I know. SOAM_CLOSE_NODE_GRACEFULLY=Y is an enhancement to the original host close feature, but it seems to have introduced another contra-common-sense behavior as described above. Close and open a host should use the common sense expectation as the default behavior - to change from the default behavior, one can sure introduce various settings to handle "exceptions" - it seems the current implementation treats exceptional cases as default, as far as common sense is concerned