LSF Version 7.3 - Administering Platform LSF

Administering Platform LSF 79
Working with Hosts
Add local resources on a dynamic host to the cluster
Prerequisites: Ensure that the resource name and type are defined in lsf.shared,
and that the ResourceMap section of lsf.cluster.cluster_name contains at least one
resource mapped to at least one static host. LSF can add local resources as long as
the ResourceMap section is defined; you do not need to map the local resources.
1 In the slave.config file, define the parameter LSF_LOCAL_RESOURCES.
For numeric resources, define name-value pairs:
"[resourcemap value*resource_name]"
For Boolean resources, the value is the resource name in the following format:
"[resource resource_name]"
For example:
LSF_LOCAL_RESOURCES="[resourcemap 1*verilog] [resource linux]"
TIP: If LSF_LOCAL_RESOURCES are already defined in a local lsf.conf on the dynamic
host, lsfinstall does not add resources you define in LSF_LOCAL_RESOURCES in
slave.config.
When the dynamic host sends a request to the master host to add it to the
cluster, the dynamic host also reports its local resources. If the local resource is
already defined in
lsf.cluster.cluster_name as default or all, it cannot be
added as a local resource.
Install LSF on a dynamic host
1 Run lsfinstall -s -f slave.config.
lsfinstall creates a local lsf.conf for the dynamic host, which sets the
following parameters:
LSF_CONFDIR="/path"
LSF_GET_CONF=lim
LSF_LIM_PORT=port_number (same as the master LIM port number)
LSF_LOCAL_RESOURCES="resource ..."
TIP: Do not duplicate LSF_LOCAL_RESOURCES entries in lsf.conf. If local resources are
defined more than once, only the last definition is valid.
LSF_SERVER_HOSTS="host_name [host_name ...]"
LSF_VERSION=7
IMPORTANT: If LSF_STRICT_CHECKING is defined in lsf.conf to protect your cluster in
untrusted environments, and your cluster has dynamic hosts, LSF_STRICT_CHECKING must
be configured in the local lsf.conf on all dynamic hosts.