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.
TLSV1 Vulnerability for spectrum conductor Cluster
We are getting TLSV1 Vulnerability on GPU Cluster other CPU cluster, Could you please review and let us know how it fix this ASAP?Current java on GPU Cluster : /usr/lib/jvm/java-1.8.0-openjdk-22.214.171.124.b10-0.el7_6.ppc64le/jre//bin/java
Address security concern related to user notebook folders in spectrum conductor
Spectrum conductor is being used in the bank for workload/resource management for spark cluster and would like to see a new enhancement to improve the security of the user data stored within the jupyter notebook folder. Currently the notebook fold...
As part of Logstash Vulnerability remediation ->we would like to upgrade logstash version to 7.4, current version after Spectrum upgraded to 2.4.1 is 7.2. Also one more point, once delivered the patch it would be good, it deletes the older vers...
Do not place IBM confidential, company confidential, or personal information into any field.