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 (https://ideas.ibm.com).
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 updateson 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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
Agnostic/Generic Instance Groups and Resource Scheduler
We are in need of agnostic/generic instance groups and an agnostic/genericresource scheduler.*) agnostic/genericresource schedulerThere is a common need for our data scientists to schedule a "pure" non-Spark TensorFlow Python application to run....
Optimize SIG package deployment for upgrade or rollback
SIG package deployment takes upto 10 minutes or so in a 50+ SIGs and 1000+ nodes cluster. Refactoring SIG deployment such that package distribution and enablement are independently managed. This will allow scheduling new SIG package distribution a...
SIG configuration update currently does full SIG deployment which includes Spark package as well. That on a large cluster with many SIGs can run into hours of deployment. This RFE is requesting to optimize SIG deployment process for Spark configur...
Add slot demand as part of the spark application metric pushed out to elastic search
We would like to have slot demand included as part of the spark application metric that are currently pushed out to elastic search which would help us identify the slot demand vs provisioned for the spark job submitted by the users.
Conductor 2.5 log retrieval feature back porting to Conductor 2.4.1. That is, to allow specifying arbitrary limit for number of executors to lookup in the RESTful call to retrieve specific executor log by its executor's id only.
Need for a better, configurable dashboard, that communicates the (usable) slots and memory utilization of the grid, provides some context, shows where the actual work is happening, and can be used by developers, grid admins, and regular business u...
Do not place IBM confidential, company confidential, or personal information into any field.