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.
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 ...
Normal user to monitor the resource usage of this user only
So currently following three ways are not able to meet the requirements: 1) Cluster admin can see the resource usage from explorer dashboard for all users. 2) read only roles also enable to see resource usage from all other users. 3) adding one ne...
In Explorer dashboard, we need to provide upper management information about how the cluster is being used.1 We need to see CPU slots data by user and SIG at the same time. Now if SIG is chosen for the chart, we don't see usage by users in that SI...
Inference job restarts a few times based on task exit code
During running an inference job, when a task fails and returns non-0 exit code. The inference engine should be able to retry the inference task for defined number of times should it detect non-0 exit code from the inference task.
Do not place IBM confidential, company confidential, or personal information into any field.