LSF Version 7.3 - Platform LSF Configuration Reference

Example
NAME=Tofino
Default
None. You must provide a unique name for the service class.
PRIORITY
Syntax
PRIORITY=integer
Description
Required. The 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 runs 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.
Default
1 (lowest possible priority)
USER_GROUP
Syntax
USER_GROUP=all | [user_name] [user_group] ...
Description
Optional. A space-separated list of user names or user groups who can submit jobs to the
service class. Administrators, root, and all users or groups listed can use the service class.
Use the reserved word all to specify all LSF users. LSF cluster administrators are automatically
included in the list of users, so LSF cluster administrators can submit jobs to any service class,
or switch any user’s jobs into this service class, even if they are not listed.
If 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. If the group can define fairshare among its members, the SLA
defined by the service class enforces the fairshare policy among the users of the SLA.
User names must be valid login names. User group names can be LSF user groups (in
lsb.users) or UNIX and Windows user groups.
lsb.serviceclasses
356 Platform LSF Configuration Reference