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.
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....
IBM Spectrum Conductor MUST set ?cache-control' response header to ?no-cache, no-store'.
Bank of America has a Global Information Security Standard that requires that IBM Spectrum Conductor (and all other applications at Bank of America) MUST set ‘cache-control' response header to ‘no-cache, no-store'. IBM Spectrum Conductor (Version ...
Currently Spark Master runs as the execution user specified in the SIG which happens to be different from cluster admin and depends on SIG tenant/consumer group. That spark master resources such as logs are owned by tenant user makes it difficult ...
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...
Do not place IBM confidential, company confidential, or personal information into any field.