LSF Version 7.3 - Administering Platform LSF

Administering Platform LSF 363
Goal-Oriented SLA-Driven Scheduling
For example:
special Boolean () () (resource locked for group 1)
bigmem Boolean () () (machine with big memory)
4 Edit lsb.queues and remove any existing resource requirements (RES_REQ)
that specify these shared resources.
5 Edit
lsb.serviceclasses and define an SLA that uses LSF_SLA as the
consumer, and requires the shared resources.
Begin ServiceClass
NAME=Uclulet
PRIORITY=20
GOALS=[Velocity timeWindow ()]
CONSUMER=LSF_SLA
EGO_RES_REQ="select(special && bigmem)"
End ServiceClass
6 Edit lsf.cluster.cluster_name and define hosts with the shared resources.
hostA ! RHEL_64 0 (special bigmem)
hostB ! RHEL_64 0 (special)
hostC ! RHEL_64 0 (bigmem)
7 Run badmin reconfig to reconfigure mbatchd.
With this configuration, EGO allocates host
hostA to the service class Uclulet. All
jobs submitted to service class
Uclulet can only be scheduled to host hostA.
Configure specific
hosts for job
scheduling
Prerequisites: EGO-enabled SLA scheduling must be turned on with
ENABLE_DEFAULT_EGO_SLA in
lsb.params. The Platform EGO consumers,
resource groups, and resource plan that you want to use for the EGO-enabled SLA
configuration must already be set up.
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.