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.
We are planning to upgrade the OS to RHEL 8 on the servers hosting Spectrum Conductor 2.5.0. With this there is also a requirement to have automation in place. We would like to get an Ansible Playbook to Deploy Spectrum Conductor.
Allow REST services make use of Kerberos authentication.
Today, any REST API authentication calls (logon) need to be provided with a username and password in order to get a conductor token. We would like to be able to use a kerberos mechanism (for example, keytabs) in order to authenticate with the logo...
Conductor should capture memory details for Jobs finished less than 30 seconds
Currently IBM SC is sending max memory as 0 or no memory for jobs completed less than 30 seconds. PNC application has majority of jobs that runs less than minute in small queues. Memory information is very important for PNC application to queue th...
Support Password Less connections for Service ID's
with Spectrum Conductor currently Service Id's authenticated as local user one time with password. This expose the security concern as password can be viewed in plain text. SAS LSF Service id needs to be authenticated manually once when IBMSC is d...
Currently IBM spectrum conductor has a support cloud bursting for both AWS and Azuer . But not for GCP. In wellsfargo we have need to support GCP . As all our computation goes into GCP. Can we have this integration available with GCP also.
More granular control of EGO_SERVICES_CONTROL for notebook consumers
This has been explained with figures in the slack thread: https://ibmsystemslabservices.slack.com/archives/GTDAWABQX/p1643389039169000 Today, in order for a user to be able to start/stop its own notebook in an instance group, the permission EGO_SE...
For Spectrum Conductor 2.5 - please add slot demand to ibm-cws-reporting-spark-application-metric index
We need this level of visibility to track slot demand by project/team/model/user/job for helping business prioritize usage and better understand current needs. This has already been reviewed to some degree in the past by Tina Langridge at IBM and ...
Do not place IBM confidential, company confidential, or personal information into any field.