Platform LSF Administration Guide Version 6.2

Chapter 17
Goal-Oriented SLA-Driven Scheduling
Administering Platform LSF
315
Configuring Service Classes for SLA Scheduling
Configure service classes in
LSB_CONFDIR/cluster_name/configdir/lsb.serviceclasses. Each
service class is defined in a ServiceClass section.
Each service class section begins with the line Begin ServiceClass and ends with the line
End ServiceClass. You must specify:
◆ A service class name
◆ At least one goal (deadline, throughput, or velocity) and a time window when the
goal is active
◆ A service class priority
All other parameters are optional. You can configure as many service class sections as
you need.
IMPORTANT
The name you use for your service classes cannot be the same as an
existing host partition or user group name.
User groups for service classes
You can control access to the SLA by configuring a user group for the service class. If
LSF user groups are specified in
lsb.users, each user in the group can submit jobs to
this service class. If a group contains a subgroup, the service class policy applies to each
member in the subgroup recursively. The group can define fairshare among its members,
and the SLA defined by the service class enforces the fairshare policy among the users
in the user group configured for the SLA.
By default, all users in the cluster can submit jobs to the service class.
Service class priority
A higher value indicates a higher priority, relative to other service classes. Similar to
queue priority, service classes access the cluster resources in priority order.
LSF schedules jobs from one service class at a time, starting with the highest-priority
service class. If multiple service classes have the same priority, LSF run all the jobs from
these service classes in first-come, first-served order.
Service class priority in LSF is completely independent of the UNIX scheduler’s priority
system for time-sharing processes. In LSF, the NICE parameter is used to set the UNIX
time-sharing priority for batch jobs.
Service class configuration examples
◆ The service class Uclulet defines one deadline goal that is active during working
hours between 8:30 AM and 4:00 PM. All jobs in the service class should complete
by the end of the specified time window. Outside of this time window, the SLA is
inactive and jobs are scheduled without any goal being enforced:
Begin ServiceClass
NAME = Uclulet
PRIORITY = 20
GOALS = [DEADLINE timeWindow (8:30-16:00)]
DESCRIPTION = "working hours"
End ServiceClass