slave.config

Deprecated. Use the server.config file instead. The slave.config file will be removed in a future release. The slave.config file contains options for installing and configuring a server host that can be dynamically added or removed.

Dynamically added LSF hosts that are not management candidate hosts are server hosts. Each dynamic server host has its own LSF binary files, local lsf.conf file, and shell environment script files (cshrc.lsf and profile.lsf). You must install LSF on each server host.

Use the lsfinstall -s -f slave.config command to install LSF with the options that are specified in theslave.config file.

Template location

A template slave.config file is located in the installation script directory that is created when you extract the installer script package. Edit the file and uncomment the options that you want in the template file. Replace the example values with your own settings to specify the options for your new LSF installation.
Important:

The sample values in the slave.config template file are examples only. They are not default installation values.

Format

Each entry in the slave.config file has the form:
NAME="STRING1 STRING2 ..."

Do not use spaces around the equal sign =, which must follow each NAME even if no value follows.

A value that contains multiple strings that are separated by spaces must be enclosed in quotation marks.

Blank lines and lines that begin with a number sign (#) are ignored.

Parameters

  • EGO_DAEMON_CONTROL
  • ENABLE_EGO
  • EP_BACKUP
  • LSF_ADMINS
  • LSF_ENTITLEMENT_FILE
  • LSF_LIM_PORT
  • LSF_SERVER_HOSTS
  • LSF_TARDIR
  • LSF_LOCAL_RESOURCES
  • LSF_TOP

  • SILENT_INSTALL

  • LSF_SILENT_INSTALL_TARLIST

EGO_DAEMON_CONTROL

Enables EGO to control the LSF res and sbatchd daemons.

Syntax

EGO_DAEMON_CONTROL="Y" | "N"

Description

Set the value to "Y" if you want the EGO service controller to start the res and sbatchd daemons, and restart if they fail.

All hosts in the cluster must use the same value for this parameter. Therefore, the value of the EGO_DAEMON_CONTROL parameter in the slave.config file must be the same as the specification for the EGO_DAEMON_CONTROL parameter in the install.config file).

To avoid conflicts, leave this parameter undefined if you use a script to start the LSF daemons.

Note:

If you specify ENABLE_EGO="N", this parameter is ignored.

Example

EGO_DAEMON_CONTROL="N"

Default

N (the res and sbatchd daemons are started manually)

ENABLE_EGO

Enables EGO functions in the LSF cluster.

Syntax

ENABLE_EGO="Y" | "N"

Description

ENABLE_EGO="Y"
Causes the lsfinstall command to uncomment the LSF_EGO_ENVDIR parameter and sets the LSF_ENABLE_EGO parameter to "Y" in the lsf.conf file.
ENABLE_EGO="N"
Causes the lsfinstall command to comment out the LSF_EGO_ENVDIR parameter and sets the LSF_ENABLE_EGO parameter to "N" in the lsf.conf file.
Set the value to "Y" to take advantage of the following LSF features that depend on EGO:
  • LSF daemon control by the EGO service controller
  • EGO enabled SLA scheduling

Default

N (EGO is disabled in the LSF cluster)

EP_BACKUP

Enables backup and rollback for enhancement packs.

Syntax

EP_BACKUP="Y" | "N"

Description

Set the value to "N" to disable backups when you install enhancement packs. You will not be able to roll back to the previous patch level after you install an enhancement pack, but you will still be able to roll back any fixes that are installed on the new enhancement pack.

You might disable backups to speed up installation time, to save disk space, or because you have your own methods to back up the cluster.

Default

Y (backup and rollback are fully enabled)

LSF_ADMINS

Required. List of LSF administrators.

Syntax

LSF_ADMINS="user_name [ user_name ... ]"

Description

The first user account name in the list is the primary LSF administrator. It cannot be the root user account.

Typically this account is named lsfadmin. It owns the LSF configuration files and log files for job events. It also has permission to reconfigure LSF and to control batch jobs that are submitted by other users. It typically does not have authority to start LSF daemons. Usually, only root has permission to start LSF daemons.

All the LSF administrator accounts must exist on all hosts in the cluster before you install LSF. Secondary LSF administrators are optional.

Valid Values

Existing user accounts

Example

LSF_ADMINS="lsfadmin user1 user2"

Default

None - required variable

LSF_ENTITLEMENT_FILE

Full path to the LSF entitlement file.

Syntax

LSF_ENTITLEMENT_FILE=path

Description

LSF uses the entitlement to determine which feature set to enable or disable based on the edition of the product. The entitlement file for LSF Standard Edition is lsf_std_entitlement.dat. For LSF Express Edition, the file is lsf_exp_entitlement.dat. For LSF Advanced Edition, the file is lsf_adv_entitlement.dat. The entitlement file is installed as <LSF_TOP>/conf/lsf.entitlement.

You must download the entitlement file for the edition of the product you are running, and set LSF_ENTITLEMENT_FILE to the full path to the entitlement file you downloaded.

After LSF is installed and running, run the lsid command to see which edition of LSF is enabled.

Example

LSF_ENTITLEMENT_FILE=/usr/share/lsf_distrib/lsf.entitlement

Default

None - required variable

LSF_LIM_PORT

TCP service port for the server host.

Syntax

LSF_LIM_PORT="port_number"

Description

Use the same port number as the value of the LSF_LIM_PORT parameter in the lsf.conf file on the management host.

Default

7869

LSF_SERVER_HOSTS

Required for non-shared server host installation. This parameter defines a list of hosts that can provide host and load information to client hosts.

Syntax

LSF_SERVER_HOSTS="host_name [ host_name ...]"

Description

If you do not define this parameter, clients contact the management host LIM for host and load information. List of LSF server hosts in the cluster to be contacted.

Define this parameter for large clusters to decrease the load on the management host LIM. Do not specify the management host in the list. Client commands query the LIMs on these defined hosts, which offload traffic from the management host LIM.

Define this parameter to ensure that commands run successfully when no LIM is running on the local host, or when the local LIM is started.

Include the list of hosts that are defined in the LSF_MASTER_LIST parameter in the lsf.conf file; specify the primary management host last. For example,
LSF_MASTER_LIST="lsfmanagement hostE"

LSF_SERVER_HOSTS="hostB hostC hostD hostE lsfmanagement"
Specify a list of host names two ways:
  • Host names that are separated by spaces
  • Name of a file that contains a list of host names, one host per line.

Valid Values

Any valid LSF host name

Examples

The following definition specifies a list of host names:
LSF_SERVER_HOSTS="hosta hostb hostc hostd"
The following definition specifies a host list file:
LSF_SERVER_HOSTS=:lsf_server_hosts
The lsf_server_hosts file contains a list of hosts:
hosta hostb hostc hostd

Default

None

LSF_TARDIR

Full path to the directory that contains the LSF distribution .tar files.

Syntax

LSF_TARDIR="/path"

Example

LSF_TARDIR="/usr/local/lsf_distrib"

Default

The parent directory of the current working directory. For example, if the lsfinstall command is running under the usr/share/lsf_distrib/lsf_lsfinstall directory, the default value for the LSF_TARDIR parameter is usr/share/lsf_distrib.

LSF_LOCAL_RESOURCES

Defines instances of local resources on the server host.

Syntax

LSF_LOCAL_RESOURCES="resource ..."

Description

  • For numeric resources, define name-value pairs:
    "[resourcemap value*resource_name]"
  • For Boolean resources, define the resource name in the form:
    "[resource resource_name]"

When the server host calls the management host to add itself, it also reports its local resources. The local resources to be added must be defined in the lsf.shared file.

If the same resource is already defined in the lsf.shared file as default or all, it cannot be added as a local resource. The shared resource overrides the local one.
Tip:

The LSF_LOCAL_RESOURCES parameter is set in the slave.config file during installation. If the LSF_LOCAL_RESOURCES parameter is already defined in a local lsf.conf file on the server host, the lsfinstall command does not add resources that you define in the LSF_LOCAL_RESOURCES parameter in the slave.config file. Do not have duplicate LSF_LOCAL_RESOURCES entries in the lsf.conf file. If local resources are defined more than once, only the last definition is valid.

Important:

Resources must already be mapped to hosts in the ResourceMap section of the lsf.cluster.cluster_name file. If the ResourceMap section does not exist, local resources are not added.

Example

LSF_LOCAL_RESOURCES="[resourcemap 1*verilog] [resource linux]"

Default

None

LSF_TOP

Required. Full path to the top level LSF installation directory.

Syntax

LSF_TOP="/path"

Description

Important: You must use the same path for every server host you install.

Valid value

The LSF_TOP file path cannot be the root directory (/).

Example

LSF_TOP="/usr/local/lsf"

Default

None - required variable 

SILENT_INSTALL

Enables silent installation.

Syntax

SILENT_INSTALL="Y" | "N"

Description

Enabling the silent installation (that is, setting this parameter to Y) means that you want to do the silent installation and accept the license agreement.

Default

N

LSF_SILENT_INSTALL_TARLIST

A string that contains all LSF package names to be installed.

Syntax

LSF_SILENT_INSTALL_TARLIST="ALL" | "Package_Name ..."

Description

This name list applies only to the silent installation mode. Supports keywords all, ALL, and All, which can install all packages in the LSF_TARDIR directory.

Example

LSF_SILENT_INSTALL_TARLIST="ALL" | "lsf10.1_linux2.6-glibc2.3-x86_64.tar.Z"

Default

None