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.
Ability to determine through Monitoring whether or not sufficient resources to start an R or Notebook runtime environment are available per node
As Data Scientist I frequently need to start runtime environments. Often these are small enough and they quite naturally fit the available resources. Sometimes however, there is a very large environment needed. We would like to easily see and determine whether there are sufficient resources available on one or many nodes of our cluster. Since the resources are constrained by nodes in the cluster this requires a view of available resources per node.
Ideally this should happen through the monitoring page. However that is currently lacking the information how many resources are available for each node. It should be enhanced so that it captures not just used or free resources for the entire cluster, but break this information down onto node level, because that is the relevant metric for starting new pods as they are constrained by a node.
Currently one would try to start a new runtime environment not knowing whether that succeeds or causing a failure due to lack of resources. The benefit thus would be that the Data Scientist doesn't even try to start a new runtime environment when there aren't sufficient resources available.
Do not place IBM confidential, company confidential, or personal information into any field.