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

Search results: Spectrum LSF

Showing 18

Queue level cgroup enablement

Hi - we have a large cluster that services many different types of workloads. To better "bucket" these workloads, we have queues set up with rules that define how the jobs must run (or be submitted). One problem we have is that some of the workloa...
3 months ago in Spectrum LSF / Administration 1 Future consideration

RTM: GPU Utilization and GPU Mem Utilization graphs for jobs based on the Host level graphs

Current state challenges: While there are per job GPU graphs they require DCGM and are restricted to only exclusive process gpu jobs. DCGM adds complexity and precludes a number of GPUs particularly ones that might be considered gamer cards as the...
4 months ago in Spectrum LSF / Operations/RTM 1 Future consideration

Allow user access tokens to have a lifetime similar to 'remember me' support industry best practice

Currently, we have robots that submit jobs using the Web Interface. The tokens expiration is currently static, and there is no API endpoint to determine the validity of the token which means that job submission and controls can fail randomly witho...
almost 3 years ago in Spectrum LSF / End User UI/Applicaton Center 0 Future consideration

Set license ownership per user

All users are assured one (1) license for interactive work. Customer has 100s of users. So, it is not practical to define each user as a leaf in a ProjectGroup.
9 months ago in Spectrum LSF / License Management 0 Future consideration

Allow Flagging Jobs for Reservation Through Rules and/or Through a "bsub --plan" Option

Today, reservations in LSF are handled by the Top X jobs by ordered by Dynamic Priority using the variable MAX_JOB_RESERVE. We believe that this is a shotgun approach. We have millions of jobs a day that require 1 cores and less than 1GB of memory...
over 2 years ago in Spectrum LSF / Administration 0 Future consideration

Do not start jobs with less than X cores per host

It is useful for when ptiles or slots do not fulfill your needs. Using an example, we have an MPI code that requests 100 cores. We don't tell LSF how to grab those cores, and sometimes it will go out and span across 12 nodes, taking 19 cores on on...
10 months ago in Spectrum LSF / Scheduling 0 Future consideration

Currently Job Priority Over Time Impacts all Queue and all Jobs - Instead optionally make it affect only Queues and Jobs that are APS Queues

The Job Priority Over Time is an excellent feature that is designed to be paired with APS dispatch rules. However, some users have setup soft dispatch or dispatch preferences in the normal queue which is not APS enabled that classify jobs by their...
almost 2 years ago in Spectrum LSF / Administration 0 Future consideration

Limit Loans to certain User Groups and/or Project tag patterns in Guarantee Pools

We want to enable more loaning of resources, but the various teams are rather territorial. They would loan to some one in either the same user group tree, and/or the same Project by regular expression. Allow Guarantee Pools to support that loan po...
almost 2 years ago in Spectrum LSF / Administration 1 Future consideration

bjobs -o reserved_mem or bhosts -o reserved_mem

To see how much memory is reserved on a host, we need to parse the bhosts -l <hostname> command, and it doesn't give us info about which job is reserving how much memory. I'd either like to see one of the following: bhosts -o 'jobid reserved...
about 3 years ago in Spectrum LSF / Scheduling 1 Future consideration

Dump configs to standardized format for cluster comparisons

We have multiple stand-alone clusters, and frequently have issues with something working differently in one as opposed to another. The solution from our side is to use something like ansible/chef/cfEngine to build the clusters, but for our existin...
about 3 years ago in Spectrum LSF / Administration 0 Future consideration