HP XC System Software Administration Guide Version 3.0

. /shared/lsf/conf/profile.lsf.xc
fi
esac
# cat lsf.csh
if ( "${path}" !~ *-slurm/etc* ) then
if ( -f /shared/lsf/conf/cshrc.lsf.xc ) then
source /shared/lsf/conf/cshrc.lsf.xc
endif
endif
NOTE: The profile.lsf.xc and cshrc.lsf.xc scripts do not exist yet. We will establish
them after installing LSF-HPC in a future step. Be sure to replace /shared/lsf with the location
of LSF_TOP on your system. Note that the names of the setup files are appended with .xc.
After installing LSF-HPC, rename the setup files to avoid disturbing the existing setup files. These
new custom files /etc/profile.d/lsf.sh and /etc/profile.d/lsf.csh must be
propagated to every node in the HP XC system; this is done in an upcoming step.
d. Set up the HP XC LSF-HPC Startup Script
The HP XC controllsf command can double as the Red Hat /etc/init.d/ service script for
starting LSF-HPC when booting the HP XC system and stopping LSF-HPC when shutting it down.
When starting LSF-HPC, the controllsf command establishes the LSF alias and starts the LSF
daemons. This command knows that LSF on HP XC should only be started on one of the resource
management nodes within the cluster, so it's OK (and necessary for failover) to configure it on
every node in the cluster.
Create the appropriate soft link to configure the controllsf command as the "service" script,
:
# which controllsf
/opt/hptc/sbin/controllsf
# ln -s /opt/hptc/sbin/controllsf /etc/init.d/lsf
This configuration must be present on every node in the HP XC system.
This completes the changes to the head node. Now the golden image must be updated with these
changes, so that they can be propagated to the rest of the cluster. See Chapter 8.: Distributing
Software Throughout the System (page 79) for the recommended procedures to update the golden
image and propagate the changes.
If HP XC roles need to be changed to ensure all resource management nodes have direct access
to the external network, the cluster_config command should be used to update the golden
image. Remember to enter 'n' when asked whether or not to install LSF locally.
If additional software such as rsh was not installed, the following procedures can be used to
update the golden image and propagate these changes with minimal impact to a running cluster.
Note that this will only propagate changes to nodes that are up:
i. Update the golden image with the following command:
# updateimage --gc `nodename nh` --image base_image --no-netboot
ii. Use the pdcp command to propagate the specific file changes to all nodes:
# pdcp -a /etc/sysconfig/iptables.proto /etc/sysconfig/iptables.proto
# pdcp -a /etc/profile.d/lsf.sh /etc/profile.d/lsf.sh
# pdcp -a /etc/profile.d/lsf.csh /etc/profile.d/lsf.csh
# pdcp -a /etc/init.d/lsf /etc/init.d/lsf
iii. Refresh the firewall on all nodes with the following command. This will update the
/etc/sysconfig/iptables file on all nodes with the changes made in a previous step:
# pdsh -a /opt/hptc/etc/nconfig.d/C04iptables nconfigure
Installing LSF-HPC
After the HP XC system is properly prepared, install LSF-HPC into the LSF tree:
Installing LSF-HPC 175