A service domain is a group of one or more FlexNet license servers. Platform License Scheduler manages the scheduling of the license tokens, but the license server actually supplies the licenses.
In cluster mode, each cluster can access licenses from 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.
WAN configuration includes all clusters sharing the WAN service domain. As for a LAN service domain, you set this in the CLUSTER_DISTRIBUTION parameter in the Feature section of the lsf.licensescheduler file.
For a WAN service domain, you can optionally configure dynamic license sharing based on past license use across all clusters served by the WAN service domain, and if required set minimum and maximum allocations for each cluster.
To allow a cluster to be able to use licenses only when another cluster does not need them, you can set the cluster distribution for the cluster to 0, and specify an allocation buffer for the number of tokens that the cluster can request.
When no jobs are running, the token allocation for CL1 is 5. CL1 can get more than 5 tokens if CL2 does not require them.
Static example (no allocation buffer set):
Begin FeatureNAME=verilogCLUSTER_DISTRIBUTION=MyWanServer(tokyo_cl 1 newyork_cl 1 toronto_cl 2)End Feature
In this example, licenses are statically allocated based solely on the number of shares assigned to each cluster. If the number of licenses is not evenly divisible by the number of shares, the additional licenses are distributed round-robin to clusters in the order they appear in CLUSTER_DISTRIBUTION. Thus if there are 98 licenses in total, tokyo_cl receives 25, newyork_cl receives 25, and toronto_cl receives 48. Each cluster limits the total rusage of running jobs based on the allocated license tokens.
Dynamic example (allocation buffer set):
Begin FeatureNAME=verilogCLUSTER_DISTRIBUTION=MyWanServer(tokyo_cl 1 newyork_cl 1 toronto_cl 2/10/50)ALLOC_BUFFER=tokyo_cl 5 newyork_cl 1 toronto_cl 2End Feature
In this example, licenses are initially distributed according to the assigned shares. Since allocation buffers are set, dynamic sharing based on past use is enabled. Based on the allocation buffers, toyko_cl receives license tokens the fastest when there is demand within the cluster. Minimum amd maximum allocations of 10 and 50 respectively are set for toronto_cl, which also has the largest share.
Begin FeatureNAME=verilogCLUSTER_DISTRIBUTION=MyWan(c1 1/1/25 c2 1/1/30 c3 2/5/100) MyLan(c1 1)ALLOC_BUFFER=c3 5 default 2End Feature
In this example the verilog license feature is available from both WAN and LAN service domain, however only cluster c1 receives the license feature from both servers. Licenses from the WAN service domain are initially distributed according to the assigned shares. Since allocation buffers are set, dynamic sharing based on past use is enabled. Based on the allocation buffers cluster c3 receives license tokens the fastest when there is demand within the cluster.