Skip to Main Content
IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform 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 updates on 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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com



ADD A NEW IDEA

Clear

Ideas

Showing 61

Use the engines of the lakehouse in Git integrated projects

We have an instance of watsonx.data in CP4D, installed on Openshift in Azure Cloud. Within watsonx.data we have buckets representing azure containers within a Azure Blob storage. In projects that are integrated with Git, when we need to configure ...

A Github integration ensures enterprise-grade governance, automation, and agility for data engineering workflows. By leveraging GitHub and LevelUp tooling, clients gain robust version control, rollback capabilities, and automated testing/deployment for pipelines and DAGs. It reduces operational risk, accelerates delivery, and aligns with modern DevOps practices.

Large enterprise clients like AT&T, who manage complex data pipelines across hybrid environments, will benefit from streamlined CI/CD processes, improved security, and consistent governance across services. How should it work? GitHub Integra...

Native LSF support for Kubernetes

K8's support similar to support for Docker would be helpful for teams using LSF and K8's for their CI/CD pipeline.
19 days ago in Spectrum LSF / Scheduling 3 Needs more information

Support new connection type for watsonx.data and support for Spark engines in it

Documentation: https://ibm-my.sharepoint.com/:w:/p/shrinivas_kulkarni_in/EcUbCoYhyVRJmWrwscDVUx8B0jxHp5cqCLtr4E7xuCGDMw?e=tbj8w8 Future State Support for new connection type to point to a specific Spark Engine of watsonx.data, either on SaaS or so...

Consider AMD ccd in affinity string

Hello, Currently, using affinity string, we can target a core, a numa, a socket or memory, but not an AMD CCD (Core Complex Dies, L3 cache shared by 8 or 16 cores) Allowing jobs requesting less cores than available in a CCD (8 or 16 currently) to ...
6 months ago in Spectrum LSF / Scheduling 2 Planned for future release

allow bresize request on job using affinity string.

due to AMD Zen arch processor, we plan to use affinity string for all jobs to force job processes to run into the smallest number of ccd, to improve performance. but bresize increase command refuse to work when an affinity string is present in the...
3 months ago in Spectrum LSF / Scheduling 1 Future consideration

Merge RES_REQ also when alternative RES_REQs are used

Currently settings from the app-profile are not merges with the job/queue settings when a alternative RES_REQ is provided in the submission command (bsub). We require this because we have a need to specify alternative RES_REQs in the submission an...
6 months ago in Spectrum LSF / Scheduling 2 Future consideration

Increase available number of global job ids for LSF

Current job id is limited to 32b. With ever growing number of jobs and scaling of multi-cluster use, the job id should be extended beyond 32b to avoid frequent rollover situations and/or cases of redundant ids. Recommend to increase to 64b or more.
10 months ago in Spectrum LSF / Scheduling 0 Planned for future release

GSLA Resource Loaning - Add the ability to loan to specific users or projects

When a GSLA resource pool is defined for a specific type of workload, it is not practical or desirable to loan to just any other type of job profile. The work-a-round today is to include a resource limit definition to prevent this from occurring. ...
7 months ago in Spectrum LSF / Scheduling 2 Future consideration

Job packing on GPUs when MIG is enabled

When MIGs (Multi-instance GPU) are enabled on a multi-GPU server, LSF should pack jobs with smaller number of MIGs on one physical GPU to keep a room for jobs with larger number of MIGs. Currently LSF is distributing the jobs on different physical...
4 months ago in Spectrum LSF / Scheduling 1 Planned for future release