Skip to Main Content
IBM Data and AI Ideas Portal for Customers

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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

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

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.

IBM Employees should enter Ideas at

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