Installing LSF-HPC With SLURM Into an Existing Standard LSF Cluster

The LSF documentation and instructions mentioned at the end of the hpc_install script are generic
and do not apply to an HP XC cluster. The following manual procedures describe every task that you
must perform on an HP XC cluster:
1. Restore the original environment setup files.
Change directory back to the existing LSF_TOP/conf directory and rename the environment
setup files to distinguish the XC files and restore the original files. Using the example:
# cd /shared/lsf/conf
# mv profile.lsf profile.lsf.xc
# mv cshrc.lsf cshrc.lsf.xc
# mv profile.lsf.orig profile.lsf
# mv cshrc.lsf.orig cshrc.lsf
The XC environment setup files now match the files configured in /etc/profile.d/lsf.sh
and /etc/profile.d/lsf.csh from the earlier step.
2. Obtain the XC internal network base.
Examine the /opt/hptc/config/base_addr.ini file on the XC cluster and identify the
value of nodeBase. By default, this value is 172.20, representing the internal XC network.
Using this value, edit the LSF_TOP/conf/lsf.cluster.<cluster name> file as follows:
a. In the Host section, find the XC node, and add slurm in the RESOURCES
column. For the example:
Begin Host
HOSTNAME model type server r1m mem swp RESOURCES #Keywords
...
xclsf ! ! 1 3.5 () () (slurm)
End Host
b. In the Parameters section, set up the floating client address range
(FLOAT_CLIENTS_ADDR_RANGE) using the nodeBase entry from Step 1.For the
example:
Begin Parameters
PRODUCTS=LSF_Base ... Platform_HPC
FLOAT_CLIENTS_ADDR_RANGE=172.20
End Parameters
Save and exit the file
3. Edit the LSF_TOP/conf/lsf.conf file.
Make the following changes to the LSF_TOP/conf/lsf.conf file:
a. Create or modify the LSF_SERVER_HOSTS variable to add the XC LSF node,
along with the other LSF Execution Hosts in the cluster:
LSF_SERVER_HOSTS="plain xclsf"
b. Enable HP OEM licensing by adding the following variable:
XC_LIBLIC=/opt/hptc/lib/libsyslic.so
c. Disable LSF_NON_PRIVILEGED_PORTS, by setting its value to N, or remove it
from the file. In standard LSF v6.1, this parameter is not supported, and generates
bad port messages from the sbatchd and mbatchd daemons on a non-XC node.
d. If you intend to use ssh for node-to-node communication, set the following variable
in lsf.conf (assuming you configured the ssh keys to allow access without a
password):