LSF Version 7.3 - Administering Platform LSF

EGO-enabled SLA scheduling
358 Administering Platform LSF
Turn on basic
EGO-enabled SLA
scheduling
Prerequisites: To use EGO-enabled SLA scheduling, all hosts that the SLA will use
must be dynamically allocated by EGO.
All hosts that the SLA will use must be dynamically allocated by EGO:
◆ Edit lsb.hosts to remove static hosts and host groups containing the hosts you
want EGO to allocate.
IMPORTANT: The lsb.hosts file must contain a "default" host line. For example:
Begin Host
HOST_NAME MXJ r1m pg ls tmp DISPATCH_WINDOW # Keywords
default ! () () () () () # Example
End Host
◆ Edit lsb.queues to remove static hosts and host groups containing the hosts
you want EGO to allocate from the queues you want to submit EGO-enabled
SLA jobs to.
◆ Queues and host partitions must be configured with HOSTS = all.
ENABLE_DEFAULT_EGO_SLA in lsb.params configures a global SLA for all
jobs in the system. Jobs submitted without
-sla are attached to the default service
class. All LSF scheduling policies apply.
1 Log on to the LSF master host as the LSF administrator (lsfadmin).
2 Let all LSF workload run to completion.
3 Shut down the LSF cluster.
4 Edit
lsb.params and set ENABLE_DEFAULT_EGO_SLA to the name of the
the default SLA.
ENABLE_DEFAULT_EGO_SLA=Venezia
The value of ENABLE_DEFAULT_EGO_SLA is the name of a valid EGO
consumer. If a service class containing a consumer with the same name does
not exist in
lsb.servieclasses, LSF creates a dynamic service class with the
specified consumer name, a velocity of 1, and a time window that is always
open.
5 Run badmin reconfig to reconfigure mbatchd.
Configure service
classes for
EGO-enabled SLA
Prerequisites: EGO-enabled SLA scheduling must be turned on with
ENABLE_DEFAULT_EGO_SLA in
lsb.params.