LSF Version 7.3 - Administering Platform LSF

EGO-enabled SLA scheduling
360 Administering Platform LSF
You can create resource groups by resource requirement (dynamic—specific
member hosts not specified) or by host name (static—only hosts currently in
the cluster are members; if you add new hosts to the cluster, you must manually
add them to a static resource group.)
NOTE: Unlike host groups in LSF, hosts should not overlap between resource groups.
Resource groups determine the distribution of resources in your EGO resource plan. Having
overlaps causes the hosts to be double counted in the resource plan, resulting in
overcommitment of hosts to some consumers.
4 Associate resource groups to consumers.
So that Platform EGO allocates resources how and when you want them, create
a resource plan to distribute resources from each resource group to each
consumer.
See “Create or modify a resource plan” in Administering and Using
Platform EGO for detailed steps.
5 Configure a default SLA in or service classes in
lsb.serviceclasses to use
these consumers.
Submit jobs to an EGO-enabled SLA
1 Run bsub -sla to submit jobs to an EGO-enabled SLA.
You can use
-g with -sla to attach all jobs in a job group to a service class and
have them scheduled as SLA jobs.
Jobs submitted without
-sla are attached to the SLA defined in
ENABLE_DEFAULT_EGO_SLA in lsb.params.
View jobs running in an EGO-enabled SLA (bsla)
The bsla command displays additional keywords for EGO-enabled SLA.
1 Run bsla to display jobs running in a service class:
bsla Kyuquot
SERVICE CLASS NAME: Kyuquot
-- Daytime/Nighttime SLA
PRIORITY: 23
CONSUMER: Kyuquot
EGO_RES_REQ: any host
MAX_HOST_IDLE_TIME: 120
USER GROUP: user1 user2
GOAL: VELOCITY 8
ACTIVE WINDOW: (9:00-17:30)
STATUS: Active:On time
SLA THROUGHPUT: 0.00 JOBS/CLEAN_PERIOD
NJOBS PEND RUN SSUSP USUSP FINISH