HP XC System Software Administration Guide Version 3.1

• You should also be familiar with the normal procedures in adding a node to an existing LSF cluster,
such as:
— Establishing default communications (rhosts or ssh keys)
— Setting up shared directories
— Adding common users
• You should also have read Chapter 15: Managing LSF (page 177) in this document.
A.2 Requirement
LSF-HPC for HP XC can only be added to an existing standard LSF cluster running the most up-to-date
version of LSF V6.2 or later.
Newer versions of Standard LSF contain the schmod_slurm module necessary to interface properly with
LSF-HPC with SLURM for HP XC systems.
A.3 Sample Case
This section describes the sample case used throughout this appendix.
There is an existing Standard LSF cluster installed on a single node with the host name plain. It will be
added to the HP XC LSF node with the host name xclsf. Note that xclsf host name will be the LSF
alias associated with the HP XC system.
Using an independent IP and host name as the HP XC LSF alias allows you to continue to take advantage
of the LSF-HPC with SLURM failover capability on the HP XC system, which will set up another HP XC
node to host this alias if the currently selected HP XC LSF node fails. For more details on setting up HP
XC LSF-HPC with SLURM failover on the HP XC system, see controllsf(8).
The head node of the HP XC system is will be xc-head.
The node plain will also be NFS-serving the LSF "tree" to the HP XC system.
Table A-1 summarizes the IP Addresses and Host Names used in this example.
Table A-1 Host Names and IP Address Used in the Sample Case
CommentInternet Protocol
Address
Host Names
Non-HP XC node in pre-existing LSF cluster16.32.1.24
plain
Head node of HP XC system16.32.2.128
xc-head
HP XC cluster alias (not used by LSF)16.32.2.130
xc
IP and host name to be used as the external HP XC LSF alias16.32.2.140
xclsf
The HP XC cluster alias is mentioned here to prevent confusion between the HP XC cluster alias and the
HP XC LSF alias. There is the potential for two separate aliases on HP XC and, depending on the
configuration, they may even reside on the same node. However, their purposes are distinct from each
other. The existing system will have been installed with LSF_TOP set to /shared/lsf. It will have
lsfadmin configured as the Primary LSF Administrator.
The name of the existing LSF cluster is corplsf.
A.4 HP XC Preparation
There are a series of steps to perform on the HP XC system to prepare it for inclusion into an existing
Standard LSF cluster.
All steps are carried out on the HP XC head node. Most steps involve propagating changes to the other
nodes in the HP XC system.
Before proceeding, read through all these steps first to ensure that you understand what is to be done:
1. Log in as superuser (root) on the head node of the HP XC system.
2. Make sure any current LSF application on the HP XC system is shut down and won't interfere.
If LSF-HPC with SLURM is currently installed and running on the HP XC system, shut it down with
the controllsf command:
# controllsf stop
252 Installing LSF-HPC with SLURM into an Existing Standard LSF Cluster