Unsupported LSF features with EGO-enabled SLA scheduling (Obsolete)

LSF with EGO-enabled SLA scheduling is no longer supported and is obsolete.

The following LSF features are not supported with EGO-enabled SLA scheduling (that is, when ENABLE_DEFAULT_EGO_SLA=Y is defined in the lsb.params file).

Most of the LSF features that are not supported with EGO-enabled SLA scheduling are related to hosts or host lists that must be specified in configuration files or on the command line. These features are not supported because hosts and job slots in LSF with EGO-enabled SLA scheduling are all dynamically allocated on demand. LSF cannot request specific hosts in these cases.

• Resource limits on hosts or host groups
• Advance reservation on hosts or host groups
• Guaranteed resource pool
• Compute unit
• Host partition
• User-based fair share at the LSF service class or host partition level
• Any configuration or job specification where a list of hosts or host groups can be specified, such as queues, host groups, or bsub -m (run the job on one of the specified hosts or host groups)
• Resizable parallel jobs
• RES_REQ in a queue, application profile, or bsub -R (run the job on a host that meets the specified resource requirements)
• Guaranteed service level agreements (SLAs)
• IBM® Spectrum LSF multicluster capability