Platform LSF Administration Guide Version 6.2

What’s New in Platform LSF Version 6.1
Administering Platform LSF
28
License ownership
and distribution
◆ Slot release on license preemption—slots will no longer be held for a job when a
license has been preempted.
This is enabled by default, but can be disabled by setting the following keyword in
the
lsf.conf file:
LSF_LIC_SCHED_PREEMPT_SLOT_RELEASE = n
◆ Default License Scheduler projects—allows job submission without an explicit
project assigned.
If a user submits a job without specifying a license project, it will be assigned to the
default project. This default project does not need to be explicitly defined within the
Begin/End Projects section in the
lsf.licensescheduler file.
Use the reserved keyword
default to configure the default project within a
distribution policy. The following example shows how to use
default to mean all
other jobs not specified to be in
proj1 or proj2:
Begin Feature
NAME = vcs
DISTRIBUTION = LanServer(proj1 3 proj2 1 default 1)
End Feature
You can also use this default license project to configure features that do not have
a scheduling policy, and will simply track the license usage of each job in a “read-
only” mode. The following example shows a feature which will allocate all the
available license tokens for a job submitted without a license project:
Begin Feature
NAME = vcs
DISTRIBUTION = LanServer(default 1)
End Feature
◆ Private licenses—a particular project owns the license and has exclusive rights to it.
No other job can use this specified license.
Use the new optional keyword,
NON_SHARED_DISTRIBUTION in the Feature
section, and define the number for
private. For example:
Begin Feature
NAME = f1 # total 15 on LanServer and 15 on WanServer
FLEX_NAME = VCSRuntime_Net
DISTRIBUTION = LanServer(p1 1 p2 1) WanServer(p1 1 p2 1/3)
NON_SHARED_DISTRIBUTION = LanServer(p1 10) WanServer (p1 5
p2 3)
PREEMPT_RESERVE=Y
End Feature
The new command option blinfo -a displays the configured shared licenses
distribution and non-shared licenses distribution as well.
◆ New -Lp option for License Scheduler projects. This option is used for License
Scheduler projects, while the current -P option is now used exclusively for LSF
projects. This option is useful for distinguishing between LSF projects and License
Scheduler projects. The
-Lp option is available for the following commands:
❖ bsub -Lp lp_name explicitly assigns projects to the License Scheduler
❖ bmod -Lp lp_name jobID attaches the job to the license project
❖ bmod -Lpn lp_name jobID detaches the job from the license project