Spectrum LSF

Showing 505

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...

almost 4 years ago in Spectrum LSF / License Management 1 Not under consideration

4 VOTE

LSF Explorer support for multiple clusters with the same name

Customer has multiple clusters with the same cluster name. Changing LSF cluster names to be unique is not an option. Their environment is large. Other products in the LSF family support this. LSF_LIC_SCHED_CLUSTER_ALIAS addresses the concern for L...

over 5 years ago in Spectrum LSF / Reporting/Explorer 0 Not under consideration

3 VOTE

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. Th...

about 4 years ago in Spectrum LSF / Scheduling 1 Not under consideration

4 VOTE

Allow functionality to save report selections in explorer GUI

Currently there is no option to save selections( time, dimensions, mesures, filters) made by a user on a given Explorer report.

over 5 years ago in Spectrum LSF / Reporting/Explorer 1 Not under consideration

1 VOTE

Cleanup user details with bqueues -lr output if they don't have running/done jobs in system

Currently, we can find thousands of entries for all users even though they have ZERO STARTED jobs as listed in bqueues -lr output. For some of larger farms, these entries are close to 7M records and bqueues -lr takes long time to return the data. ...

over 1 year ago in Spectrum LSF / Scheduling 2 Planned for future release

1 VOTE

Add those 'HOSTS:' column for Queues, Pools, and Host Groups as defined in the lsb.* files

RTM does a good job normalizing the display of hosts in each of these categories, but having the raw value, as entered by the administrator is also very useful for operations. Currently, these values are not collected.

over 1 year ago in Spectrum LSF / Operations/RTM 2 Not under consideration

2 VOTE

Extend Role-based access control to data columns

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...

almost 3 years ago in Spectrum LSF / Reporting/Explorer 2 Not under consideration

1 VOTE

LSF Resource Connecter should allow start/stop of existing AWS VMs.

We have procedural limitations with creating new instances in AWS on-demand by LSF Resource Connector (RC) for security reasons. Our preference would be to create instances ahead of time and let LSF RC start and stop the instances based on demand....

over 1 year ago in Spectrum LSF / Cloud Bursting 3 Functionality already exists

1 VOTE

Enhance bmod to not allow modifying a jobs memory reservation to not exceed the total additional reservable memory on the host if the job is running

This is important if a users wants to either decrease of increase a memory reservation for a running job. We have some applications that reserved multiple CPU's and large amounts of memory. These jobs are long tailed, and once they reach the long ...

over 1 year ago in Spectrum LSF / Administration 1 Not under consideration

1 VOTE

Add additional bhist information about personnel who modified the LSF job

Enhance bhist to show who modifies the job. The information is not presented in JOB_MODIFY2 event record. Current user info in JOB_MODIFY2 is job owner and user auth for remote job in MC

over 1 year ago in Spectrum LSF / Administration 0 Future consideration

Please enter your email address

FILTER BY CATEGORY