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,
Post an idea
Upvote ideas that matter most to you
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.
Request to release notebook resources in spectrum conductor when no workload running
The spectrum conductor currently doesn't release the jupyter notebook resources unless the user manually stops the jupyter notebook or the slots gets reclaimed by EGO. We do have a urgent requirement to allow the notebook resources to be released ...
Currently spark executors and drivers are allocated same number of slots based on a configuration at the resource group level. This request is provide a separate configuration for driver slot allocation.
Spectrum conductor provides APIs and UI functionality to deploy SIGs to all or selected cluster members. There are at times corruption on the member nodes due to disk out of space or misconfiguration, or state issues. This feature should clean up ...
dynamically move nodes from a resource group to another by the means of updating node attributes
Background: today, it's hard to move nodes from one RG to another one using dynamically selection of hosts based on arttributes. We can tag a node with an attribute, but changing its value requires one to change ego.conf, remove the host from the ...
Do not place IBM confidential, company confidential, or personal information into any field.