Spectrum LSF

Showing 475

use "bconf" command to delete host and create or delete resource

It would be helpful for administrators. Simplify the management of HPC clusters.

5 months ago in Spectrum LSF / Administration 0 Future consideration

Update lsf.shared with up-to-date CPU models

The file `lsf.shared` provided with Spectrum LSF is outdated. The CPU models listed seem to be 10 years old and older and there don't seem to be any updates from IBM. I suggest that IBM regularly updates this file with up-to-date CPU models and me...

10 months ago in Spectrum LSF / Administration 1 Not under consideration

1 VOTE

Run LSF file IO operations within the container.

LSF jobs using containers depend on mounts within the container. These mounts are not available on bare metal where LSF runs file operations. The bare metal dependency means that LSF file related operations, -o, -f, -E, -Ep, etc. will not have acc...

5 months ago in Spectrum LSF / Scheduling 1

4 VOTE

bsub should accept a cpu_efficiency parameter to allow cpu over-commiting in the pool

It's rare for a job to achieve close to 100% cpu efficiency. Often, jobs have a peak cpu requirement during its execution lifetime but use less cpus in average. If bsub could be told that a job is expected to run with a given cpu efficiency, LSF c...

over 1 year ago in Spectrum LSF / Simulation & Prediction 2 Not under consideration

4 VOTE

Change job submit time to include milliseconds for precision.

Job submit time to include milliseconds for precision. Instead of HH:MM:SS, make it like 12:29:05.1234. This will enable this column to be used as a unique identifier when generating data in an incremental fashion. We are extracting the RTM data a...

over 1 year ago in Spectrum LSF / Reporting/Explorer 4 Not under consideration

1 VOTE

be able to add (and remove) new type of metadata

to manage other metadata that the ones already defined: LSF user extra limit & TTL, license quota, etc ... currently, we must update several scripts & conf files to add (or remove) other metadata type than the built-in ones.

5 months ago in Spectrum LSF / Operations/RTM 0 Planned for future release

1 VOTE

provide a mechanism to avoid manually inserting hash code into thold.php and settings.php for new thold alerts to view details.

When we add our own thold alerts, we must add manually the hash code recorded into a mysql table into thold.php and settings.php scripts to be able to display details. Can you please redesign the code to avoid these steps ?

5 months ago in Spectrum LSF / Operations/RTM 1 Planned for future release

1 VOTE

support 5 or more arguments in thold.php

To create versatile alerts, we sometimes needs more than 2 or 3 max arguments to set the alert. For ex, for a LSF server load alert, we should need clusterid, server hostgroup, load index, comparison operator, etc ....

5 months ago in Spectrum LSF / Operations/RTM 1 Planned for future release

1 VOTE

Expanding the host list for bjobs-m

If we puts a list variable containing about 1300 equipment into the bjobs(bjobs -u all -m "$list"), a segmentation fault (core dump) occurs. Dev checked code. The host list in bjobs -m supports 512 hostnames at most. The host to put in bjobs ...

5 months ago in Spectrum LSF / Administration 1 Not under consideration

4 VOTE

Ability to limit user's views in RTM to select clusters

Reduces support because users can't flip to other clusters via Cluster drop-down menu to then ask questions about resources and usage or see other information that should only be for users of a particular cluster or why can't they find their infor...

almost 2 years ago in Spectrum LSF / Operations/RTM 1 Not under consideration

Please enter your email address

FILTER BY CATEGORY