LSF Version 7.3 - Administering Platform LSF
EGO-enabled SLA scheduling
362 Administering Platform LSF
LSF preemption also supports queues that can be both preemptable and
preemptive. Under the EGO reclaim mechanism, resource ownership guarantees
that some jobs cannot be reclaimed.
Job and queue
priority
Queue priority is respected by EGO-enabled SLA scheduling. You can also
configure priority among SLAs. Configure the consumer rank in your EGO
consumer tree to reflect the priories in your SLAs. See Administering and Using
Platform EGO for information about setting the priority of consumers.
Example: change host groups to EGO resource groups
Host groups are no longer needed with EGO-enabled SLA scheduling. You can
configure resource groups two ways:
◆ By resource requirement, using specific resources, like memory, processor,
operating system, etc,
◆ By host name, selecting specific member hosts
Configure specific
resources 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.
Complete the following steps to configure an SLA to schedule jobs based on specific
resource requirements.
1 Log on to the LSF master host as the LSF administrator (lsfadmin).
2 Log on to the Platform Management Console:
a Create an EGO resource group with specific resource requirements.
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.
3 Edit
lsf.shared and define shared resources for your different host
requirements.