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.
Ability to specify cores or exclusive host for Benchmark job
Currently all benchmark jobs submitted via RTM use 1 core. Also, one cannot specify node to be exclusively used via bsub -x. This allows other jobs to land on same node and thus tainting benchmark numbers
bhosts and lshosts should have an option to let them perform more like the scheduler
Currently, if I have a host with two exclusive resources in the lsf.cluster file <hostname> <model> <type> 1 () () () (!res1 !res2) If I run the following bhosts command, it acts like "grep" instead of like the scheduler, and rep...
In our environment, a few different teams will make use of different reporting capabilities in LSF Explorer in different scopes. Therefore they will be creating different reports and dashboards. So there is the need to introduce something like a p...
We are facing the need to limit access to certain data columns/fields in LSF Explorer for certain roles. In our environment a few different teams will make use of the reporting capabilities of LSF Explorer in different scopes. Nevertheless, LSF Ex...
Move away from having to set job_end_logged on every gridjobs and gridpend poller runs
The setting of job_end_logged to 0 every polling cycle can add as much as 100 seconds to every gridjobs or gridpend run. If instead, the poller were to capture the following
SELECT MAX(last_updated) FROM grid_jobs* WHERE clusterid = ?
blusers improvement to show both external and hoarding jobs in one listing
I didn't find an option in "blusers" command that will give me the full list of jobs that use specific license token. There are two options available, each gives partial picture and the output is in different format. So it takes unnecessary e...
Currently, a bmod is a very expensive activity in LSF, but running a bmod to simply change a jobs priority, should be a low impact changes. What we would request is to have the bmod that simply does an '-sp' to be handled in a way that has the lea...
Improve Various Components of the Current Scheduler Adlgorithm
Currently, though the Scheduler supports threads, the processing is not a thread per bucket, but rather a threads that are used on a per bucket basis and buckets are still handled serially, which has led us to Host Match times around 400 seconds.
Enable the Scheduler Debug to Run Continually and Provide JSON Output via 'badmin' Standard Output
Currently the Scheduler debug must be written to a file, and the scheduler debug information is not easily accessible through the management CLI. What would be better would be to have an MBD parameter to enable all the time as is done with 'badmin...
Do not place IBM confidential, company confidential, or personal information into any field.