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.
It would be useful to set a limit in lsb.resources for Serive Class "SLA" in order give some minimum guarantee with SLA and set a maximium number of resorucese usable in this SLA.It would be excellent to indicate the limit with the number of nodes...
ssched jobs missing task information to calculate job run time
We graph job run time from the data in Elasticsearch provided from LSF Explorer. ssched jobs do not contain enough information to calculate job run time. We believe task jobs should contain the same data as regular LSF jobs
Availability of Max used License Scheduler managed license token in LSF job records
License Scheduler keeps updating LSF job records for the actual number of license tokens used by the job. At the end, only the last used value of the license token is kept in the job records. LSF should record the maximum number of token used by L...
Allow RTM to define the level of pending reasons to collect
Currently RTM does not provide any pending reason precision to be collected. As such, in our case, there are way to many pending reasons in the system which makes the feature unusable. We would like to have a global setting that does the following...
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. Th...
Set the "+pref_level" for hosts or host_groups in lsb.hosts
Currently it's possible in lsb.queues to set the "+pref_level" for hosts or host_groups in the "HOSTS" section to prioritize some hosts for job submission. We have various host groups defined in lsb.hosts and would like to set the +pref_level for ...
Allow the user to save multiple cluster dashboard layouts by name
Right now, the Cluster Dashboard is very monolithic, you every time you go there, you have to set it up the way you like it. Yes, you can save the dashboard, but it would be nice to have multiple saved dashboards so that you can quickly obtain the...
Allow Tagging of LSF Clusters and Filtering from Dashboard and Managmenet pages
Currently we have a lot of clusters for various functions and purposes. It would be nice to be able to tag clusters by function, production/test/dev, etc and then be able to filter the various pages by tagname. It would help cut down on clutter wh...
Do not place IBM confidential, company confidential, or personal information into any field.