Group license ownership

Group license ownership lets you distribute license features to license projects. Defining groups is optional. A license project should only belong to one group.

License Scheduler first balances license distribution at the group level based on group license ownership. The total number of licenses owned by all group members is the number of licenses owned by the group. License Scheduler then balances license distribution among license projects.

With group license ownership, projects can trigger preemption either when the project is using fewer licenses than it owns (the project is underfed) or when the group to which the project belongs is using fewer licenses than the group owns (the group is underfed).

Examples of preemption with group license ownership

The following tables show changes in preemption behavior based on group license ownership of a total of 20 licenses.

Project license ownership only


License project

Licenses owned

Licenses used

Lp1

5

6

Lp2

5

0

Lp3

5

7


Group license ownership


Group

License projects

Project licenses owned

GroupA

Lp1

Lp2

5

5

GroupB

Lp3

Lp4

5

5

Group

License projects

Project licenses owned


Project license ownership within a group


Group

License projects

Project licenses owned

GroupA

Lp1

Lp2

5

5

GroupB

Lp3

Lp4

5

5

Group

License projects

Project licenses owned


Configuration

Use the GROUP parameter in the Feature section of the lsf.licensescheduler file to define groups and their members.

Example

Begin Feature NAME = AppY DISTRIBUTION = LanServer1(Lp1 5/5 Lp2 5/5 Lp3 5/5 Lp4 5/5) GROUP = GroupA(Lp1 Lp2) GroupB (Lp3 Lp4) End Feature

In this example, Lp1 and Lp2 belong to the group GroupA. Lp3 and Lp4 belong to the GroupB group.