Displays information about service class configuration for service-level agreement (SLA) scheduling
bsla displays the properties of service classes configured in lsb.serviceclasses and dynamic information about the state of each configured service class.
If a default system service class is configured with ENABLE_DEFAULT_EGO_SLA in lsb.params but no other service classes are explicitly configured in lsb.serviceclasses, bsla only displays information for the default SLA.
Time-based SLAs include those with throughput, velocity, or dealine goals. A list of service classes is displayed with the following fields:
The name of the service class, followed by its description, if any.
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.
User names or user groups who can submit jobs to the service class.
The configured time window when the service class goal is active. If a throughput or velocity goal has no time window configured, ACTIVE WINDOW is Always Open.
For throughput goals, the configured job throughput (finished jobs per hour) for the service class.
The current throughput for the SLA finished jobs per clean period.
For goals with a time window, estimated finish time of the SLA. If the service class status is on time, the finish time is before the configured deadline. If the service class status is delayed, the service class is missing its goal and bsla shows a finish time later than the deadline.
For goals with a time window, the optimum number of jobs that should be running in the service class for the SLA to meet its goal.
The current number of jobs in the specified service class. A parallel job is counted as 1 job, regardless of the number of job slots it uses.
The number of user-suspended jobs in the specified service class.
The number of jobs in the specified service class in EXITED or DONE state.
Resource-based SLAs are those with guarantee goals. A list of service classes is displayed with the following fields:
The name of the service class, followed by its description, if any.
Configured access restrictions for the guarantee SLA, if any.
Number of resources within the guarantee in use by the SLA. Resource use includes both running and suspended jobs.
Number of resources in the pool currently in use by the SLA. This may exceed the number of guaranteed resources for the SLA if other guarantee SLAs using the same resource pool are not running at capacity. Resource use includes both running and suspended jobs.
In addition to the general output, EGO-enabled SLA service classes display the following fields:
The name of the EGO consumer from which hosts are allocated to the SLA.
How long the SLA holds its idle hosts before LSF releases them to EGO.
The number of hosts allocated to the SLA that EGO has reclaimed.
The amount of time EGO gives to LSF to clean up its workload before EGO reclaims the host.
Begin ServiceClass
NAME = Duncan
CONSUMER = Duncan
PRIORITY = 23
USER_GROUP = user1 user2
GOALS = [VELOCITY 8 timeWindow (9:00-17:30)] \
[DEADLINE timeWindow (17:30-9:00)]
DESCRIPTION = Daytime/Nighttime SLA
End ServiceClass
bsla Duncan
SERVICE CLASS NAME: Duncan
-- Daytime/Nighttime SLA
PRIORITY: 23
CONSUMER: Duncan
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
GOAL: DEADLINE
ACTIVE WINDOW: (17:30-9:00)
STATUS: Inactive
SLA THROUGHPUT: 0.00 JOBS/CLEAN_PERIOD
NJOBS PEND RUN SSUSP USUSP FINISH
0 0 0 0 0 0
The following resource pools named linuxPool and solarisPool are configured in lsb.resources:
Begin GuaranteedResourcePool
NAME =linuxPool
TYPE = hosts
HOSTS = linuxHG
DISTRIBUTION = [[sla1,10%] [sla2,25%]
DESCRIPTION = A linux resource pool used by sla1, and sla2.
End GuaranteedResourcePool