Service domains in Platform License Scheduler

A service domain is a group of one or more FlexNet license servers. License Scheduler manages the scheduling of the license tokens, but the license server actually supplies the licenses. You configure the service domain with the license server names and port numbers that serve licenses to a network.

  • LAN: a service domain serving licenses to a single cluster

  • WAN: a sevic e domain serving licenses to multiple clusters

License Scheduler assumes that any license in the service domain is available to any user who can receive a token from License Scheduler. Therefore, every user associated with a project specified in the distribution policy must meet the following requirements:

  • The user is able to make a network connection to every FlexNet license server host in the service domain.

  • The user environment is configured with permissions to check out the license from every FlexNet license server host in the service domain.

You must configure at least one service domain for Platform License Scheduler. It groups FlexNet license server hosts that serve licenses to LSF jobs and is used when you define a policy for sharing software licenses among your projects.

If a FlexNet license server host is not part of a License Scheduler service domain, its licenses are not managed by License Scheduler (the license distribution policies you configure in LSF do not apply to these licenses and usage of these licenses does not influence LSF scheduling decisions).

Service domain locality

License feature locality allows you to limit features from different service domains to a specific cluster, so that License Scheduler does not grant tokens to jobs from license that legally cannot be used on the cluster requesting the token. The LAN service domains used in cluster mode are configured using single-cluster locality.

Project mode

In project mode, a cluster can access the same license feature from multiple service domains.

If your license servers restrict the serving of license tokens to specific geographical locations, use LOCAL_TO to specify the locality of a license token for any features that cannot be shared across all the locations. This avoids having to define different distribution and allocation policies for different service domains, and allows hierarchical project group configurations.

To use Platform License Scheduler tokens in project mode, a job submission must specify the -Lp (license project) option. The project must be defined for the requested feature in lsf.licensescheduler.

Cluster mode

In cluster mode, each license feature in a cluster can access a single license feature from at most one WAN and one LAN service domain.

Platform License Scheduler does not control application checkout behavior. If the same license is available from both the LAN and WAN service domains, License Scheduler expects jobs to try to obtain the license from the LAN first.