Installing Platform LSF on UNIX and Linuxsunray2.mit.edu/kits/platform-lsf/7.0.6/1/guides/kit_lsf_guide... · Installing Platform LSF on UNIX and Linux ... PLATFORM SYMPHONY, PLATFORM

Installing Platform LSF on UNIX and Linux

Platform LSFVersion 7.0 Update 6

Release date: August 2009Last modified: August 17, 2009

Copyright © 1994-2009 Platform Computing Inc.

Although the information in this document has been carefully reviewed, Platform Computing Corporation (“Platform”) does notwarrant it to be free of errors or omissions. Platform reserves the right to make corrections, updates, revisions or changes to theinformation in this document.

UNLESS OTHERWISE EXPRESSLY STATED BY PLATFORM, THE PROGRAM DESCRIBED IN THIS DOCUMENT ISPROVIDED “AS IS” AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NOEVENT WILL PLATFORM COMPUTING BE LIABLE TO ANYONE FOR SPECIAL, COLLATERAL, INCIDENTAL, ORCONSEQUENTIAL DAMAGES, INCLUDING WITHOUT LIMITATION ANY LOST PROFITS, DATA, OR SAVINGS, ARISINGOUT OF THE USE OF OR INABILITY TO USE THIS PROGRAM.

We’d like to hearfrom you

You can help us make this document better by telling us what you think of the content, organization, and usefulness of the information.If you find an error, or just want to make a suggestion for improving this document, please address your comments [email protected].

Your comments should pertain only to Platform documentation. For product support, contact [email protected].

Documentredistribution andtranslation

This document is protected by copyright and you may not redistribute or translate it into another language, in part or in whole.

Internalredistribution

You may only redistribute this document internally within your organization (for example, on an intranet) provided that you continueto check the Platform Web site for updates and update your version of the documentation. You may not make it available to yourorganization over the Internet.

Trademarks LSF is a registered trademark of Platform Computing Corporation in the United States and in other jurisdictions.

ACCELERATING INTELLIGENCE, PLATFORM COMPUTING, PLATFORM SYMPHONY, PLATFORM JOBSCHEDULER,PLATFORM ENTERPRISE GRID ORCHESTRATOR, PLATFORM EGO, and the PLATFORM and PLATFORM LSF logos aretrademarks of Platform Computing Corporation in the United States and in other jurisdictions.

UNIX is a registered trademark of The Open Group in the United States and in other jurisdictions.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Microsoft is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.

Windows is a registered trademark of Microsoft Corporation in the United States and other countries.

Intel, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States andother countries.

Other products or services mentioned in this document are identified by the trademarks or service marks of their respective owners.

Third-partylicenseagreements

http://www.platform.com/Company/third.part.license.htm

ContentsExample installation directory structure ................................................................................. 5Plan your installation ............................................................................................................. 6

EGO in the LSF cluster ................................................................................................... 6Prepare your systems for installation .................................................................................... 7Install a new Platform LSF cluster (lsfinstall) ......................................................................... 8After installing Platform LSF .................................................................................................. 9If you install LSF as a non-root user .................................................................................... 11Add hosts ............................................................................................................................. 12

Running host setup remotely (rhostsetup) .................................................................... 12Optional LSF HPC configuration ................................................................................... 13

install.config ......................................................................................................................... 15About install.config ........................................................................................................ 15Parameters ................................................................................................................... 15

Installing Platform LSF on UNIX and Linux 3

4 Installing Platform LSF on UNIX and Linux

Example installation directory structure

Example installation directory structure


Plan your installation• Choose a primary LSF administrator (owns the LSF and EGO configuration files and log files; e.g.,

LSF_ADMINS="lsfadmin")• Choose a shared LSF installation directory (e.g., LSF_TOP="/usr/share/lsf")• Choose LSF hosts (master host, master candidates, server hosts, and client-only hosts; e.g.,

LSF_ADD_SERVERS="hostm hostb hostc hostd" LSF_MASTER_LIST="hostm hostd"LSF_ADD_CLIENTS="hoste hostf")

Important:Do not use the name of any host, user, or user group as the name of your cluster.

• Choose LSF server hosts that are candidates to become the master host for the cluster, if you are installing a newhost to be dynamically added to the cluster (for example, LSF_MASTER_LIST="hosta hostb"

• Choose a cluster name (39 characters or less with no white spaces; for example, LSF_CLUSTER_NAME="cluster1")

• If you choose to install the HPC Portal and Platform LSF Reports (PERF), make sure at least one master candidatein LSF_MASTER_LIST runs Linux. If you choose to use the Derby database for demo purposes, choose the databasehost; e.g., DERBY_DB_HOST="hostd". If EGO does not manage HPC Portal or PERF, you must also choose HPCPortal and PERF hosts, otherwise it is optional. For example, PERF_HOST="hostr", PMC_HOST="hostp".

• If you are planning to use AFS with MPICH-GM and have made any custom changes to your existing AFS orMPICH-GM esub, create a backup of these.

EGO in the LSF clusterWhen EGO is enabled in the cluster, EGO may control services for components such as the HPC Portal or LSF Reports(PERF). This is recommended. It allows failover among multiple management hosts, and allows EGO cluster commandsto start, stop, and restart the services.

See the LSF administrator documentation for more details on the benefits of enabling EGO and using EGO to controlthe services.

Installation choicesWhen you install the cluster and enable EGO, you can configure the following separately:

• EGO control of sbatchd and res• EGO control of the HPC Portal (webgui)• EGO control of PERF services (plc, jobdt, purger, and derbydb)

For example, you could choose EGO control for PERF services, but not sbatchd and res.

Note:The HPC Portal requires PERF services to be running.

Plan your installation


Prepare your systems for installation• Ensure the installation file system on the file server host has enough disk space for all host types (approximately

300 MB per host type).• Ensure top-level LSF installation directory (LSF_TOP=EGO_TOP) is accessible with the same path name from all

hosts in the LSF cluster (e.g., /usr/share/lsf).• Ensure the installation file system containing LSF_TOP (EGO_TOP) is writable by the user account that is running

lsfinstall.• Create user accounts for LSF administrators (e.g., lsfadmin).• If you need help to download LSF distribution tar files, read the Release Notes for Platform LSF.• Get the LSF installation script tar file lsf7Update6_lsfinstall.tar.Z and extract it (e.g., # zcat

lsf7Update6_lsfinstall.tar.Z | tar xvf -)• Get the LSF distribution tar files for all host types you need, and put them in the same directory as

lsf7Update6_lsfinstall.tar.Z (e.g., for Linux 2.6 kernel glibc version 2.3: lsf7Update6_linux2.6-glibc2.3-x86.tar.Z). Do not extract the distribution tar files.

• If you choose to install the HPC Portal with Platform LSF Reports, get the distribution file hpc_portal7_linux-x86_64.tar.Z and put it in the same directory as lsf7Update6_lsfinstall.tar.Z. Do not extract the tarfile.

• Get the Knowledge Center tar file knowledge_center7Update6.tar.Z and put it in the same directory aslsf7Update6_lsfinstall.tar.Z. Do not extract the tar file.

• If you choose to install the Session Scheduler for Platform LSF, get the distribution file from my.platform.com,and put it in the same directory as lsf7Update6_lsfinstall.tar.Z. Do not extract the tar file.

• Get an LSF license key and create an LSF license file (license.dat) in the same directory as the distribution filesand lsf7Update6_lsfinstall.tar.Z

You must have a valid license file to install. If lsfinstall cannot find a license file, it exits.

Integrating LDAP with LSFTo install LSF in an LDAP environment, check the following are satisfied:

• LSF admin is a defined user in LDAP.• The OS is configured to use LDAP for authentication.• LDAP admin grants privileges to the LSF installer user (usually root) to retrieve the user list from the LDAP server.

To allow LDAP users HPC Portal logon access, check the following are satisfied:

• The OS is configured to use LDAP for authentication.• LDAP admin grants privileges to the HPC Portal process startup user (usually root) to retrieve the password list

from the LDAP server.

Prepare your systems for installation


Install a new Platform LSF cluster (lsfinstall)1. Log on as root to the LSF installation file server.

If you are not root, see If you install LSF as a non-root user on page 11.2. Change to lsf7update6_lsfinstall/.3. Edit ./install.config or ./slave.config to specify the installation variables you want.

Uncomment the options you want in the template file, and replace the example values with your own settings.

Tip:The sample values in the install.config and slave.config template files areexamples only. They are not default installation values.

4. Run ./lsfinstall -f install.config.5. Select both LSF and HPC Portal.6. Install the Knowledge Center.

Install a new Platform LSF cluster (lsfinstall)


After installing Platform LSF1. Optional. Run hostsetup to set up LSF hosts.

a) Log on to each LSF server host as root. Start with the LSF master host. If you are not root, you can continuewith host setup, but by default, only root can start the LSF daemons.

b) Run hostsetup on each LSF server host. For example, to use the LSF cluster installed in /usr/share/lsfand configure LSF daemons to start automatically:# cd /usr/share/lsf/7.0/install

# ./hostsetup --top="/usr/share/lsf" --boot="y"

For complete hostsetup usage, enter hostsetup -h.2. Log on to the LSF master host as root, and set your LSF environment:

• For csh or tcsh:% source LSF_TOP/conf/cshrc.lsf

• For sh, ksh, or bash:$ . LSF_TOP/conf/profile.lsf

3. Optional. Enable Platform LSF for users.

Ensure all users Include LSF_CONFDIR/cshrc.lsf or LSF_CONFDIR/profile.lsf in their .cshrcor .profile.

4. Run lsfstartup to start the cluster.

If your cluster administrator lsfadmin is a local account, and you allow EGO to control HPC Portal, start thecluster as root.

5. If you do not want to allow EGO to control HPC Portal, log onto the HPC Portal host and do the following.a) Start the HPC Portal. Run:

pmcadmin start

If your cluster administrator lsfadmin is a local account, start HPC Portal as root.b) Optional. Enable setrc for HPC Portal. Run:

pmcsetrc.sh

6. If you do not want to allow EGO to control PERF daemons, do the following.a) Start PERF daemons. Log onto the PERF host and run:

perfadmin start all

b) Optional. Enable setrc for PERF daemons. Log onto the PERF host and run:perfsetrc.sh

c) If you use Derby database and the database host is not the PERF host, start the PERF database daemon. Logonto the Derby DB host and run:perfadmin start all

d) Optional. If you use Derby database and the database host is not the PERF host, enable setrc for PERF databasedaemons. Log onto the Derby DB host and run:perfsetrc.sh

7. Test your cluster by running some basic LSF commands (e.g., lsid, lshosts, bhosts). After testing your cluster,be sure all LSF users include LSF_CONFDIR/cshrc.lsf or LSF_CONFDIR/profile.lsf in their .cshrcor .profile.

8. Test the HPC Portal. Browse to the web server URL and log in to the HPC Portal using the LSF administrator nameand password.

After installing Platform LSF


The web server URL is:http://host_name:8080/platform

The host name is the HPC Portal host you specified.

If HPC Portal is controlled by EGO and you did not specify the HPC Portal host, log on as LSF administrator andrun:egosh client view GUIURL_1

The additional information shows the full URL including the host name and port.

After installing Platform LSF


If you install LSF as a non-root userIf you install without root permissions, you must choose either a multi-user cluster or a single-user cluster:

• Single-user : Your user account must be primary LSF administrator. This account will be able to start LSF daemons,but it is the only user account that can submit jobs to the cluster. To display load information this user accountmust also be able to read the system kernel information, such as /dev/kmem.

• Multi-user: By default, only root can start the LSF daemons. Any user can submit jobs to your cluster. To make thecluster available to other users, you must manually change the ownership and setuid bit for lsadmin and badminto root, and the file permission mode to -rwsr-xr-x (4755) so that the user ID bit for the owner is setuid.

Use the following commands to set the correct owner, user ID bit, and file permission mode for a multi-user cluster:# chown root lsadmin badmin eauth swtbl_api ntbl_api# chmod 4755 lsadmin badmin eauth swtbl_api ntbl_api

Running IBM POE jobs in Platform LSF• Single-user: To run IBM POE jobs, you must manually change the ownership and setuid bit for swtbl_api and

ntbl_api to root, and the file permission mode to -rwsr-xr-x (4755) so that the user ID bit for the owner is setuid.

Use the following commands to set the correct owner, user ID bit, and file permission mode:# chown root swtbl_api ntbl_api# chmod 4755 swtbl_api ntbl_api

If you install LSF as a non-root user


Add hostsSet up hosts to join the cluster.

Note:You must run hostsetup on SGI hosts (IRIX, TRIX, and Altix), HP-UX hosts, andLinux QsNet hosts. Running hostsetup is optional on all other systems.

1. # hostsetup --top="/usr/share/lsf" --boot="y"

This sets up a host to use the cluster installed in /usr/share/lsf. It also configures the LSF daemons to startautomatically (--boot="y").

For Platform LSF on the following systems, running hostsetup does the following things:

• For SGI IRIX, TRIX, and Altix cpuset hosts, hostsetup adds the cpuset Boolean resource to the HOSTS sectionof lsf.cluster.cluster_name for each cpuset host.

• For HP-UX pset hosts, hostsetup adds the pset Boolean resource to the HOSTS section oflsf.cluster.cluster_name for each pset host.

• For Linux QsNet hosts, hostsetup:

• Configures lsf.cluster.cluster_name to assign the Boolean resource rms defined in lsf.shared to allLSF hosts that run on an RMS partition.

• Creates a table named lsfrids in the RMS database. This table is used internally by LSF.

Running host setup remotely (rhostsetup)Before using rhostsetup, you must configure the following parameters at the top of the script:

• LSF_RSHCMD: Remote shell command (e.g, rsh or ssh) accessing the remote host.• LSF_HOSTS: Lists hosts to run hostsetup on.• LSF_TOPDIR: Sets the hostsetup --top option. Specify the full path to the top-level installation directory.

rhostsetup tries to detect this from lsf.conf if it is not defined here.• LSF_BOOT: Sets the hostsetup --boot option. Default is no (n).• LSF_QUIET: Sets the hostsetup --quiet option. Default is no (n).

Use the rhostsetup script to launch hostsetup on remote hosts.

rhostsetup uses either ssh or rsh. It is included in the installation script tar filelsf7Update6_lsfinstall.tar.Z and is located in the lsf7Update6_lsfinstall directory created when youuncompress and extract installation script tar file.

After installation, rhostsetup is located in LSF_TOP/7.0/install/.

1. Run the rhostsetup script.

For example:LSF_RSHCMD="ssh -n"LSF_HOSTS="hostA hostB hostC"LSF_TOPDIR=/usr/local/lsLSF_BOOT=yLSF_QUIET=n

Add hosts


Optional LSF HPC configurationAfter installing LSF HPC, you can define the following in lsf.conf:

• LSF_LOGDIR=directory

In large clusters, you should set LSF_LOGDIR to a local file system (for example, /var/log/lsf).• LSB_RLA_WORKDIR=directory parameter, where directory is the location of the status files for RLA. Allows RLA

to recover its original state when it restarts. When RLA first starts, it creates the directory defined byLSB_RLA_WORKDIR if it does not exist, then creates subdirectories for each host.

You should avoid using /tmp or any other directory that is automatically cleaned up by the system. Unless yourinstallation has restrictions on the LSB_SHAREDIR directory, you should use the default:LSB_SHAREDIR/cluster_name/rla_workdir

On IRIX or TRIX, you should not use a CXFS file system for LSB_RLA_WORKDIR.• On Linux hosts running HP MPI, set the full path to the HP vendor MPI library libmpirm.so.

For example, if HP MPI is installed in /opt/hpmpi:LSF_VPLUGIN="/opt/hpmpi/lib/linux_ia32/libmpirm.so"

• LSB_RLA_UPDATE=time_seconds

Specifies how often the LSF scheduler refreshes information from RLA.

Default: 600 seconds• LSB_RLA_HOST_LIST="host_name ..."

On Linux/QsNet hosts, the LSF scheduler can contact the RLA running on any host for RMS allocation requests.LSB_RLA_HOST_LIST defines a list of hosts to restrict which RLAs the LSF scheduler contacts.

If LSB_RLA_HOST_LIST is configured, you must list at least one host per RMS partition for the RMS partition tobe considered for job scheduling.

Listed hosts must be defined in lsf.cluster.cluster_name.• LSB_RLA_UPDATE=seconds

On Linux/QsNet hosts, specifies how often RLA should refresh its RMS information map.

Default: 600 seconds• LSB_RMSACCT_DELAY=time_seconds

If set on Linux/QsNet hosts, RES waits the specified number of seconds before exiting to allow LSF and RMS jobstatistics to synchronize.

If LSB_RMSACCT_DELAY=0, RES waits forever until the database is up to date.• LSB_RMS_MAXNUMNODES=integer

Maximum number of nodes in a Linux/QsNet system. Specifies a maximum value for the nodes argument to thetopology scheduler options specified in:

• -extsched option of bsub• DEFAULT_EXTSCHED and MANDATORY_EXTSCHED in lsb.queues

Default: 1024• LSB_RMS_MAXNUMRAILS=integer

Maximum number of rails in a Linux/QsNet system. Specifies a maximum value for the rails argument to thetopology scheduler options specified in:

Add hosts



Default: 32• LSB_RMS_MAXPTILE=integer

Maximum number of CPUs per node in a Linux/QsNet system. Specifies a maximum value for the RMS[ptile]argument to the topology scheduler options specified in:


Default: 32

Add hosts


install.configAbout install.configThe install.config file contains options for LSF installation and configuration. Use lsfinstall -finstall.config to install LSF using the options specified in install.config.

Template locationA template install.config is included in the installation script tar file lsf7Update6_lsfinstall.tar.Z andis located in the lsf7Update6_lsfinstall directory created when you uncompress and extract installation scripttar file. Edit the file and uncomment the options you want in the template file. Replace the example values with yourown settings to specify the options for your new installation.

Important:The sample values in the install.config template file are examples only. They arenot default installation values.

After installation, the install.config containing the options you specified is located in LSF_TOP/7.0/install/.

FormatEach entry in install.config has the form:NAME="STRING1 STRING2 ..."

The equal sign = must follow each NAME even if no value follows and there should be no spaces around the equal sign.

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

Blank lines and lines starting with a pound sign (#) are ignored.

Parameters• DERBY_DB_HOST• EGO_DAEMON_CONTROL• EGO_PERF_CONTROL• EGO_PMC_CONTROL• ENABLE_DYNAMIC_HOSTS• ENABLE_EGO• ENABLE_HPC_CONFIG• EP_BACKUP• LSF_ADD_SERVERS• LSF_ADD_CLIENTS• LSF_ADMINS• LSF_CLUSTER_NAME• LSF_DYNAMIC_HOST_WAIT_TIME• LSF_LICENSE• LSF_MASTER_LIST

install.config


• LSF_QUIET_INST• LSF_TARDIR• LSF_TOP• PATCH_BACKUP_DIR• PATCH_HISTORY_DIR• PERF_HOST• PMC_HOST

DERBY_DB_HOSTSyntax

DERBY_DB_HOST="host_name"

DescriptionReporting database host. This parameter is used when you install the HPC Portal package forthe first time, and is ignored for all other cases.

Specify the name of a reliable host where the Derby database for Reporting data collection willbe installed. You must specify a host from LSF_MASTER_LIST. Leave this parameterundefined if you will use another database for Reporting.

ExampleDERBY_DB_HOST="hostd"

DefaultDatabase is undefined.

EGO_DAEMON_CONTROLSyntax

EGO_DAEMON_CONTROL="Y" | "N"

DescriptionEnables EGO to control LSF res and sbatchd. Set the value to "Y" if you want EGO ServiceController to start res and sbatchd, and restart if they fail. To avoid conflicts, leave thisparameter undefined if you use a script to start up LSF daemons.

Note:If you specify EGO_ENABLE="N", this parameter is ignored.

ExampleEGO_DAEMON_CONTROL="N"

DefaultN (res and sbatchd are started manually)

install.config


EGO_PERF_CONTROLSyntax

EGO_PERF_CONTROL="Y" | "N"

DescriptionEnables EGO Service Controller to control PERF daemons. Set the value to "N" if you want tocontrol PERF daemons manually. If you do this, you must define PERF_HOST in this file.


Note:This parameter only takes effect when you install the HPC portalpackage for the first time.

ExampleEGO_PERF_CONTROL="N"

DefaultY (PERF daemons are controlled by EGO unless EGO is disabled)

EGO_PMC_CONTROLSyntax

EGO_PMC_CONTROL="Y" | "N"

DescriptionEnables EGO Service Controller to control the HPC Portal. Set the value to "N" if you want tocontrol the HPC Portal manually.


Note:This parameter only takes effect when you install the HPC Portalpackage for the first time.

ExampleEGO_PMC_CONTROL="N"

DefaultY (HPC Portal is controlled by EGO unless EGO is disabled)

install.config


ENABLE_DYNAMIC_HOSTSSyntax

ENABLE_DYNAMIC_HOSTS="Y" | "N"

DescriptionEnables dynamically adding and removing hosts. Set the value to "Y" if you want to allowdynamically added hosts.

If you enable dynamic hosts, any host can connect to cluster. To enable security, configureLSF_HOST_ADDR_RANGE in lsf.cluster.cluster_name after installation andrestrict the hosts that can connect to your cluster.

ExampleENABLE_DYNAMIC_HOSTS="N"

DefaultN (dynamic hosts not allowed)

ENABLE_EGOSyntax

ENABLE_EGO="Y" | "N"

DescriptionEnables Platform EGO functionality in the LSF cluster.

ENABLE_EGO="Y" causes lsfinstall uncomment LSF_EGO_ENVDIR and setsLSF_ENABLE_EGO="Y" in lsf.conf.

ENABLE_EGO="N" causes lsfinstall to comment out LSF_EGO_ENVDIR and setsLSF_ENABLE_EGO="N" in lsf.conf.

Set the value to "N" if you do not want to take advantage of the following LSF features thatdepend on EGO:

• LSF daemon control by EGO Service Controller• EGO-enabled SLA scheduling• HPC Portal• LSF reporting

DefaultY (EGO is enabled in the LSF cluster)

ENABLE_HPC_CONFIGSyntax

ENABLE_HPC_CONFIG="Y" | "N"

install.config


DescriptionSet the value to "Y" to add LSF HPC configuration parameters to the cluster.

DefaultY (Platform LSF HPC is enabled.)

EP_BACKUPSyntax

EP_BACKUP="Y" | "N"

DescriptionEnables backup and rollback for enhancement packs. Set the value to "N" to disable backupswhen installing enhancement packs (you will not be able to roll back to the previous patchlevel after installing an EP, but you will still be able to roll back any fixes installed on the newEP).

You may disable backups to speed up install time, to save disk space, or because you have yourown methods to back up the cluster.

DefaultY (backup and rollback are fully enabled)

LSF_ADD_SERVERSSyntax

LSF_ADD_SERVERS="host_name [ host_name...]"

DescriptionList of additional LSF server hosts.

The hosts in LSF_MASTER_LIST are always LSF servers. You can specify additional serverhosts. Specify a list of host names two ways:

• Host names separated by spaces• Name of a file containing a list of host names, one host per line.

Valid ValuesAny valid LSF host name.

Example 1List of host names:LSF_ADD_SERVERS="hosta hostb hostc hostd"

Example 2Host list file:LSF_ADD_SERVERS=:lsf_server_hosts

install.config


The file lsf_server_hosts contains a list of hosts:hostahostbhostchostd

DefaultOnly hosts in LSF_MASTER_LIST are LSF servers.

LSF_ADD_CLIENTSSyntax

LSF_ADD_CLIENTS="host_name [ host_name...]"

DescriptionList of LSF client-only hosts.

Tip:After installation, you must manually editlsf.cluster.cluster_name to include the host model and typeof each client listed in LSF_ADD_CLIENTS.

Valid ValuesAny valid LSF host name.

Example 1List of host names:LSF_ADD_CLIENTS="hoste hostf"

Example 2Host list file:LSF_ADD_CLIENTS=:lsf_client_hosts

The file lsf_client_hosts contains a list of hosts:hostehostf

DefaultNo client hosts installed.

LSF_ADMINSSyntax

LSF_ADMINS="user_name [ user_name ... ]"

DescriptionRequired. List of LSF administrators.

install.config


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

Typically this account is named lsfadmin. It owns the LSF configuration files and log files forjob events. It also has permission to reconfigure LSF and to control batch jobs submitted byother users. It typically does not have authority to start LSF daemons. Usually, only root haspermission 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.

Caution:You should not configure the root account as the primary LSFadministrator.

Valid ValuesExisting user accounts

ExampleLSF_ADMINS="lsfadmin user1 user2"

DefaultNone—required variable

LSF_CLUSTER_NAMESyntax

LSF_CLUSTER_NAME="cluster_name"

DescriptionRequired. The name of the LSF cluster.

ExampleLSF_CLUSTER_NAME="cluster1"

Valid ValuesAny alphanumeric string containing no more than 39 characters. The name cannot containwhite spaces.

Important:Do not use the name of any host, user, or user group as the nameof your cluster.

DefaultNone—required variable

install.config


LSF_DYNAMIC_HOST_WAIT_TIMESyntax

LSF_DYNAMIC_HOST_WAIT_TIME=seconds

DescriptionTime in seconds slave LIM waits after startup before calling master LIM to add the slave hostdynamically.

This parameter only takes effect if you set ENABLE_DYNAMIC_HOSTS="Y" in this file. Ifthe slave LIM receives the master announcement while it is waiting, it does not call the masterLIM to add itself.

Recommended valueUp to 60 seconds for every 1000 hosts in the cluster, for a maximum of 15 minutes. Selectinga smaller value will result in a quicker response time for new hosts at the expense of an increasedload on the master LIM.

ExampleLSF_DYNAMIC_HOST_WAIT_TIME=60

Hosts will wait 60 seconds from startup to receive an acknowledgement from the master LIM.If it does not receive the acknowledgement within the 60 seconds, it will send a request for themaster LIM to add it to the cluster.

DefaultSlave LIM waits forever

LSF_LICENSESyntax

LSF_LICENSE="/path/license_file"

DescriptionFull path to the name of the LSF license file, license.dat.

You must have a valid license file to install LSF.

Caution:If you do not specify LSF_LICENSE, or lsfinstall cannot finda valid license file in the default location, lsfinstall exits.

ExampleLSF_LICENSE="/usr/share/lsf_distrib/license.dat"

install.config


DefaultThe parent directory of the current working directory. For example, if lsfinstall is runningunder usr/share/lsf_distrib/lsf_lsfinstall the LSF_LICENSE default value isusr/share/lsf_distrib/license.dat.

LSF_MASTER_LISTSyntax

LSF_MASTER_LIST="host_name [ host_name ...]"

DescriptionRequired for a first-time installation. List of LSF server hosts to be master or master candidatesin the cluster.

You must specify at least one valid server host to start the cluster. The first host listed is theLSF master host.

During upgrade, specify the existing value.

Valid ValuesLSF server host names

ExampleLSF_MASTER_LIST="hosta hostb hostc hostd"

DefaultNone — required variable

LSF_QUIET_INSTSyntax

LSF_QUIET_INST="Y" | "N"

DescriptionEnables quiet installation.

Set the value to Y if you want to hide the LSF installation messages.

ExampleLSF_QUIET_INST="Y"

DefaultN (installer displays messages during installation)

install.config


LSF_TARDIRSyntax

LSF_TARDIR="/path"

DescriptionFull path to the directory containing the LSF distribution tar files.

ExampleLSF_TARDIR="/usr/share/lsf_distrib"

DefaultThe parent directory of the current working directory. For example, if lsfinstall is runningunder usr/share/lsf_distrib/lsf_lsfinstall the LSF_TARDIR default value isusr/share/lsf_distrib.

LSF_TOPSyntax

LSF_TOP="/path"

DescriptionRequired. Full path to the top-level LSF installation directory.

Valid ValueThe path to LSF_TOP must be shared and accessible to all hosts in the cluster. It cannot bethe root directory (/). The file system containing LSF_TOP must have enough disk space forall host types (approximately 300 MB per host type).

ExampleLSF_TOP="/usr/share/lsf"

DefaultNone — required variable

PATCH_BACKUP_DIRSyntax

PATCH_BACKUP_DIR="/path"

DescriptionFull path to the patch backup directory. This parameter is used when you install a new clusterfor the first time, and is ignored for all other cases.

install.config


The file system containing the patch backup directory must have sufficient disk space to backup your files (approximately 400 MB per binary type if you want to be able to install and rollback one enhancement pack and a few additional fixes). It cannot be the root directory (/).

If the directory already exists, it must be writable by the cluster administrator (lsfadmin).

If you need to change the directory after installation, edit PATCH_BACKUP_DIR inLSF_TOP/patch.conf and move the saved backup files to the new directory manually.

ExamplePATCH_BACKUP_DIR="/usr/share/lsf/patch/backup"

DefaultLSF_TOP/patch/backup

PATCH_HISTORY_DIRSyntax

PATCH_HISTORY_DIR="/path"

DescriptionFull path to the patch history directory. This parameter is used when you install a new clusterfor the first time, and is ignored for all other cases.

It cannot be the root directory (/). If the directory already exists, it must be writable bylsfadmin.

The location is saved as PATCH_HISTORY_DIR in LSF_TOP/patch.conf. Do not changethe directory after installation.

ExamplePATCH_BACKUP_DIR="/usr/share/lsf/patch"

DefaultLSF_TOP/patch

PERF_HOSTSyntax

PERF_HOST="host_name"

DescriptionDedicated host for PERF daemons. Required if EGO_PERF_CONTROL="N". To allowfailover, we recommend that you leave this parameter undefined when EGO control is enabledfor the PERF daemons.

Specify the name of one host that will run PERF daemons: plc, jobdt, and purger. If EGOcontrols PERF daemons, you must specify a host from LSF_MASTER_LIST.

Note:

install.config


This parameter only takes effect when you install the HPC Portalpackage for the first time.

ExamplePERF_HOST="hostp"

DefaultUndefined.

PMC_HOSTSyntax

PMC_HOST="host_name"

DescriptionDedicated host for HPC Portal. Required if EGO_PMC_CONTROL="N". To allow failover,we recommend that you leave this parameter undefined when EGO control is enabled for theHPC Portal.

Specify the name of one host that will always run the HPC Portal. If EGO controls HPC Portal,you must specify a host from LSF_MASTER_LIST.

Note:This parameter only takes effect when you install the HPC Portalpackage for the first time.

ExamplePMC_HOST="hostg"

DefaultUndefined.

install.config


IndexC

cluster namelsfinstall command 6

D

DB_HOSTinstall.config file 16

E

EGO_DAEMON_CONTROLinstall.config file 16

EGO_PERF_CONTROLinstall.config file 17

EGO_PMC_CONTROLinstall.config file 17

ENABLE_DYNAMIC_HOSTSinstall.config file 18

ENABLE_EGOinstall.config file 18

ENABLE_HPC_INSTinstall.config file 18

EP_BACKUPinstall.config file 19

I

install.config filedescription 15

L

LSF_ADD_CLIENTSinstall.config file 20

LSF_ADD_SERVERS

install.config file 19LSF_ADMINS

install.config file 20LSF_CLUSTER_NAME

install.config file 21LSF_DYNAMIC_HOST_WAIT_TIME

install.config file 22LSF_LICENSE

install.config file 22LSF_MASTER_LIST

install.config file 23LSF_QUIET_INST

install.config file 23LSF_TARDIR

install.config file 24LSF_TOP

install.config file 24

M

master host candidateslsfinstall command 6

P

PATCH_BACKUP_DIRinstall.config file 24

PATCH_HISTORY_DIRinstall.config file 25

PERF_HOSTinstall.config file 25

PMC_HOSTinstall.config file 26

R

rhostsetup scriptlsfinstall command 12


Documents

Installing Platform LSF on UNIX and Linuxsunray2.mit.edu/kits/platform-lsf/7.0.6/1/guides/kit_lsf_guide... · Installing Platform LSF on UNIX and Linux ... PLATFORM SYMPHONY, PLATFORM