[ Platform Documentation ]

[ Title ]

[ Contents ]

[ Previous ]

[ Next ]

[ Index ]

---

bsla

---

displays information about service class configuration for goal-oriented service-level agreement (SLA) scheduling

SYNOPSIS

bsla [service_class_name]

bsla [-h | -V]

DESCRIPTION

bsla displays the properties of service classes configured in LSB_CONFDIR/cluster_name/configdir/lsb.serviceclasses (see lsb.serviceclasses(5)) and dynamic information about the state of each configured service class.

OPTIONS

service_class_name

The name of a service class configured in lsb.serviceclasses.

-h

Prints command usage to stderr and exits.

-V

Prints LSF release version to stderr and exits.

OUTPUT

A list of job groups is displayed with the following fields:

SERVICE CLASS NAME

The name of the service class, followed by its description, if any.

PRIORITY

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 GROUP

User names or user groups who can submit jobs to the service class.

GOAL

The type of service class goal and its configured value:

• THROUGHPUT
• VELOCITY
• DEADLINE

ACTIVE WINDOW

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.

STATUS

Current status of the service class goal:

• Active:On time--the goal is active and meeting its target.
• Active:Delayed--the goal is active but is missing its target.
• Inactive--the goal is not active; its time window is closed. Jobs are scheduled as if no service class is defined. LSF does not enforce any service-level goal for an inactive SLA.

THROUGHPUT

For throughput goals, the configured job throughput (finished jobs per hour) for the service class.

SLA THROUGHPUT

The current throughput for the SLA finished jobs per clean period.

ESTIMATED FINISH TIME

For goals with a time window, estimated finish time of the SLA. If the service class status is on time, the finish time will be 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.

OPTIMUM NUMBER OF RUNNING JOBS

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.

NJOBS

The current number of job slots used by jobs in the specified service class. A parallel job is counted as 1 job, regardless of the number of job slots it will use.

PEND

The number of pending job slots used by jobs in the specified service class.

RUN

The number of job slots used by running jobs in the specified service class.

SSUSP

The number of job slots used by the system-suspended jobs in the service class.

USUSP

The number of job slots used by user-suspended jobs in the specified service class.

FINISH

The number of jobs in the specified service class in EXITED or DONE state.

EXAMPLE

For the following service class named Kyuquot is configured in lsb.serviceclasses:

Begin ServiceClass
NAME = Kyuquot
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 shows the following properties and current status:

% bsla Kyuquot 
SERVICE CLASS NAME:  Kyuquot 
 -- Daytime/Nighttime SLA
PRIORITY:  23
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

SEE ALSO

bacct(1), bhist(1), bjobs(1), bkill(1), bmod(1), bsub(1), lsb.acct(5), lsb.serviceclasses(5)

[ Top ]

---

[ Platform Documentation ]

[ Title ]

[ Contents ]

[ Previous ]

[ Next ]

[ Index ]

---

Date Modified: February 24, 2004 Platform Computing: www.platform.com Platform Support: support@platform.com Platform Information Development: doc@platform.com Copyright © 1994-2004 Platform Computing Corporation. All rights reserved.