The lsf.shared file contains common definitions that are shared by all load sharing clusters defined by lsf.cluster.cluster_name files. This includes lists of cluster names, host types, host models, the special resources available, and external load indices, including indices required to submit jobs using JSDL files.
This file is installed by default in the directory defined by LSF_CONFDIR.
Defines all cluster names recognized by the LSF system.
All cluster names referenced anywhere in the LSF system must be defined here. The file names of cluster-specific configuration files must end with the associated cluster name.
By default, if MultiCluster is installed, all clusters listed in this section participate in the same MultiCluster environment. However, individual clusters can restrict their MultiCluster participation by specifying a subset of clusters at the cluster level (lsf.cluster.cluster_name RemoteClusters section).
(Required) Lists models of machines and gives the relative CPU scaling factor for each model. All hosts of the same relative speed are assigned the same host model.
LSF uses the relative CPU scaling factor to normalize the CPU load indices so that jobs are more likely to be sent to faster hosts. The CPU factor affects the calculation of job execution time limits and accounting. Using large or inaccurate values for the CPU factor can cause confusing results when CPU time limits or accounting are used.
The first line consists of the mandatory keywords MODELNAME, CPUFACTOR, and ARCHITECTURE.
When you first install LSF, you do not necessarily need to assign models and types to hosts in lsf.cluster.cluster_name. If you do not assign models and types to hosts in lsf.cluster.cluster_name, LIM automatically detects the model and type for the host.
If you have versions earlier than LSF 4.0, you may have host models and types already assigned to hosts. You can take advantage of automatic detection of host model and type also.
Automatic detection of host model and type is useful because you no longer need to make changes in the configuration files when you upgrade the operating system or hardware of a host and reconfigure the cluster. LSF will automatically detect the change.
Automatically detected models are mapped to the short model names in lsf.shared in the ARCHITECTURE column. Model strings in the ARCHITECTURE column are only used for mapping to the short model names.
Begin HostModel
MODELNAME CPUFACTOR ARCHITECTURE
SparcU5 5.0 (SUNWUltra510_270_sparcv9)
PC486 2.0 (i486_33 i486_66)
PowerPC 3.0 (PowerPC12 PowerPC16 PowerPC31)
End HostModel
If an automatically detected host model cannot be matched with the short model name, it is matched to the best partial match and a warning message is generated.
If a host model cannot be detected or is not supported, it is assigned the DEFAULT model name and an error message is generated.
hardware_platform [_processor_speed[_processor_type]]
processor_speed is the optional clock speed and is used to differentiate computers within a single platform
processor_type is the optional processor manufacturer used to differentiate processors with the same speed
Underscores (_) between hardware_platform, processor_speed, processor_type are mandatory.
The first line consists of the keywords. RESOURCENAME and DESCRIPTION are mandatory. The other keywords are optional. Subsequent lines define resources.
Begin Resource
RESOURCENAME TYPE INTERVAL INCREASING CONSUMABLE DESCRIPTION # Keywords
patchrev Numeric () Y () (Patch revision)
specman Numeric () N () (Specman)
switch Numeric () Y N (Network Switch)
rack String () () () (Server room rack)
owner String () () () (Owner of the host)
elimres Numeric 10 Y () (elim generated index)
ostype String () () () (Operating system and version)
lmhostid String () () () (FlexLM's lmhostid)
limversion String () () () (Version of LIM binary)
End Resource
A resource name cannot contain any of the following characters:
A resource name cannot be any of the following reserved names:
To avoid conflict with inf and nan keywords in 3rd-party libraries, resource names should not begin with inf or nan (upper case or lower case). Resource requirment strings, such as -R "infra" or -R "nano" will cause an error. Use -R "defined(infxx)" or -R "defined(nanxx)", to specify these resource names.
For Solaris machines, the keyword int is reserved and cannot be used.
Boolean—Resources that have a value of 1 on hosts that have the resource and 0 otherwise.
Numeric—Resources that take numerical values, such as all the load indices, number of processors on a host, or host CPU factor.
String— Resources that take string values, such as host type, host model, host status.
Explicitly control if a resource is consumable. Applies to static or dynamic numeric resources.
You should only specify consumable resources in the rusage section of a resource requirement string. Non-consumable resources are ignored in rusage sections.
A non-consumable resource should not be releasable. Non-consumable numeric resource should be able to used in order, select and same sections of a resource requirement string.
When LSF_STRICT_RESREQ=Y in lsf.conf, LSF rejects resource requirement strings where an rusage section contains a non-consumable resource.