Skip to Main Content
IBM Data and AI Ideas Portal for Customers


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


Status Future consideration
Workspace Spectrum LSF
Components Administration
Created by Guest
Created on Jun 9, 2023

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 today, and they can always dispatch.  However, we have certain jobs that do any one of the following:

* Have topology that spans more than a single node
* Request more than X GB of memory
* Request more than on scheduling core
* Requests specific licenses or other scarce resources

It would be nice to either create a "Plan" by job, or by a set of resource requirements.  Let's say assuming we do the plan at the cluster level.

lsb.params
RESERVE_FOR=slots>1,mem>40000,blah>blah

lsb.queues
RESERVE_FOR=same_as_above

Still, we would always reserve for the top MAX_JOB_RESERVE variable accross the cluster, but we would not require the bsub option.  In the case a user specifies the bsub option, we should have the opportunity to unwind that in ESUB, or add via ESUB as well.

Needed By Not sure -- Just thought it was cool