IBM Data and AI Ideas Portal for Customers


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:

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

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.

Additional Information

To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


Status Future consideration
Workspace Spectrum LSF
Components Scheduling
Created by Guest
Created on Dec 4, 2020

Enhance GSLA to enable in-queue preemption

The Guaranteed SLA system allows sharing of Resources defined by ServiceClasses. We would like to use that to allow two or more groups to pool and share compute slots, wherein they typically unused slots would be available to all of the groups. The GSLA attempts to keep the usage of these balanced according to the ALLOCATION. However, it does not have a mechanism to force rapid re-balancing when one groups Demand surges, and other groups are using the starved group's share.
There is a SIMPLIFIED_GUARANTEE, which supports PREEMPTION from one queue to jobs in another queue. But, the jobs from the groups will be sharing the same queue. Thus, the preemption needs to be between jobs in the same queue. Therefore, like with License Scheduler, we would like a ServiceClass to have an OWN, and be able to preempt borrowing jobs when the OWN'er needs the slots back.

Suggested Implementation:
Each ServiceClass will have an OWN of a Pool. Not sure if that should be defined in the Pool Resources or the ServiceClasses.
To define preemption paths:
The mechanism that tracks the jobs (pool resources) used in each ServiceClass, will (for some ServiceClasses) have a string that says whether these jobs are PREEMPTABLE by (Sc1,Sc2 ..), or PREEMPTIVE to (Sc1, Sc2). And will have another string that defines the conditions under which preemption happens. For example, PREEMPT_FOR = "PEND 300", would mean that jobs in the ServiceClass that have been in PEND for 300 seconds BECAUSE of a lack of the pooled resources, will preempt preemptable jobs in other service classes that are over their share limit.

That would be the basics of the intra-GSLA preemption. There are, of course, a lot of caveats to consider. For example, jobs that are PEND'ing need to have a sole and only PEND reason being the lack of the pool resources. If they are also pending for Licenses, there is no benefit in them preempting jobs that already have licenses and slots. Assuming that the PEND'ing job's License resources can be met, then it needs to choose wisely the jobs to PREEMPT. That would be the jobs which, first order, were the last to use the excess of shared resources. That is, if the borrowing ServiceClass jobs have exceeded their share by 20 slots, then the jobs on top of that would be the first to be checked. The Second order check is to verify that the resources that the target job is using (the machine, memory) will satisfy the preempting job's needs. If not, there is again, no benefit to preempting it. Finally (third order check), concerns the Priority stacks of the candidate jobs. It is presumed that the job triggering the PREEMPTION is already the highest priority, since LSF chose it. But, the job to be preempted should be the lowest priority in the set of jobs that could be preempted. So, although the First Order check is to find the job(s) which have piled on top of the over-fed stack, the Third Order check is to sort them by their Priorities.
Those priorities, I believe, are calculated from a complex formula involving the various priority ranking systems (Queue Priority, Fairshare, Job-Level, License Scheduler).

  • Guest
    Jan 4, 2021

    This request will not be delivered within the release currently under development, but the theme is aligned with our multi-year strategy. We are looking for more feedback for this request through activities such as voting. We will update this request in the future.