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.
In our cluster, we are very often impacted by jobs under reserving cpus (using -n option of bsub). for ex, we have a user group using a GUI for days. When the user close the GUI, it fires thousands of tar/bzip2 -9 to compress log files, making exe...
Today, on many Cacti pages, table headers include tooltips that explain the dimensions that are displayed in the table. It would be nice to have that for the 13 standard load indexes in LSF, and be able to pull the description from lsf.shared for ...
Have LSF track the number of status changes and requeues for a job over time
Basically, right now, there is no way to look at LSF's jobInfo record to know how many times a job has been requeued via either a pre-exec/jobstarter failure, or from a manual requeue. Additionally, there is no way to determine how many times a jo...
Threshold for over allocation in License Scheduler
Based on the license availability and the demand from certain project(s), LSF License scheduler can allocate more license to a project, then its define share of licenses. If limits are defined, it leads to under utilization and wastage of licenses...
The Heuristics plugin trim's Project Names on panels inconsistently:
1) Trims, but does not properly roll-up statistics
2) Does not trim consistently between panels
3) Projects no way to provide Project trimming level (1, 2, 3, x, All)
Today, in LSF, there is a "badmin showstatus" that gives us information such as reconfig time, restart times, host counts, user counts, etc. It would be nice to have an 'lsadmin showstatus' option as well. I would think the following would be good...
Have the gridalarms plugin respect Maintenance Schedules like it parent plugin thold does
The gridalarms Cacti plugin was initially a fork of the thold plugin which supports the concept of a Maintenance Schedules, but this functionality was never implemented in gridalarms. We would like to see if that functionality can be added to grid...
Enhance database_purge_cluster.php to have an 'all' option
This --clusterid=all would remove any clusters not currently found in the grid_clusters table. So, the deletes would look something like:
DELETE FROM some_table WHERE clusterid NOT IN (SELECT clusterid FROM grid_clusters)
Also, the help on this ...
Deprecate License Scheduler DYNAMIC setting and support RUSAGE DURATION natively
Currently License Scheduler does not support jobs that use a DURATION on a license reservation in either Fast Dispatch or Cluster Mode. We would prefer that License Scheduler follow LSF properly in all three modes, and deprecate/remove the DYNAMIC...
Improve Host Automation in RTM to Move a Host that is Moved from Cluster to Cluster
Today, in our operations, we will move a host from cluster to cluster and in RTM that means that there will now be multiple hosts with the same hostname associated with multiple clusters. What we would prefer is that instead of creating a new host...
Do not place IBM confidential, company confidential, or personal information into any field.