LSF Version 7.3 - Administering Platform LSF

EGO-enabled SLA scheduling
364 Administering Platform LSF
Complete the following steps to configure an SLA to schedule jobs using specific
hosts.
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.queues and remove any hosts and host groups from the queues you
want to submit EGO-enabled SLA jobs to.
5 Log on to the Platform Management Console:
a Create an EGO resource group that contains specific hosts (for example,
hostA and hostB).
b Define an EGO consumer for the SLA (for example, LSF_SLA).
c Define the EGO resource plan for the resource group associated with the
consumer LSF_SLA.
6 Edit
lsb.serviceclasses and define an SLA that uses LSF_SLA as the
consumer.
7 Run badmin reconfig to reconfigure mbatchd.
With this configuration, EGO allocates hosts
hostA and hostB to the SLA. All jobs
submitted to SLA
Uclulet can only be scheduled to hosts hostA and hostB.
Example: change host partitions to EGO consumers
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.