HP Insight Cluster Management Utility - Manual (Page 154)

rm -f ${CMU_RCFG_PATH}/var/log/spooler*
rm -f ${CMU_RCFG_PATH}/var/log/lastlog*
rm -f ${CMU_RCFG_PATH}/var/log/cron*
if [ -d ${CMU_RCFG_PATH}/var/log/collectl ]; then
rm -f ${CMU_RCFG_PATH}/var/log/collectl/*
fi
rm -f ${CMU_RCFG_PATH}/opt/cmu/log/*
exit 0
8.7.3 HP Insight CMU oneSIS diskless file system support for independent addressing
of Intel Xeon Phi cards
HP Insight CMU oneSIS diskless support provides two scripts for modifying the oneSIS single system
image. The reconf-onesis-image.sh script runs as the last step after the oneSIS diskless
logical group is created. This script contains all of the general changes to make to the image. The
reconf-onesis-snapshot.sh
script is run each time a node is added to the oneSIS diskless
logical group, and performs all node-specific changes to the image. Typically these scripts work
together to prepare the image. For example, the reconf-onesis-image.sh script configures
a file as being node-specific in oneSIS, and then the reconf-onesis-snapshot.sh script
creates the node-specific version of that file for each node.
In the following examples, portions of the /opt/intel/mic/filesystem/ subdirectory are
manually constructed as writeable directories. This is because the /opt/intel/mic/
filesystem/
directory must be writeable, but some of the subdirectories contain many binaries
that do not need to be writeable. Thus the management of this file system was manually crafted to
optimize the use of the writeable in-memory file system.
The following examples only focus on the Intel Xeon Phi support. You might need to add additional
scripting to support your specific environment. Also, these examples are only provided to display
one way of implementing Intel Xeon Phi support. They are not absolute requirements, and may be
subject to change depending on the Intel Xeon Phi software. These scripts were written to work
with Intel Xeon Phi software driver version 6720-19 on a RHEL 6.3 Linux distribution.
The following is the content of the reconf-onesis-image.sh script. To invoke, this script must
be present in the appropriate image directory before the image is created:
#!/bin/bash
#
# CMU - oneSIS post-image building customizable script
#
# environment variables available:
#
# CMU_RCFG_PATH = path where the diskless filesystem is currently mounted
# CMU_RCFG_IMAGENAME = name of this CMU diskless logical group
# CMU_PATH = CMU installation path
#
# Note:
# If you need to make changes to the oneSIS configuration file, for example
# to configure a file to be node-specific, you can use the
# /opt/cmu/diskless/oneSIS/cmu_add_entry_to_file command:
#
# # pwd
# /opt/cmu/diskless/oneSIS
# # ./cmu_add_entry_to_file -h
# usage : ./cmu_add_entry_to_file -h
# ./cmu_add_entry_to_file -f -k -e
#
# file: file to modify
# keyword: commented keyword after which to add the entry
# entry: the entry to add (no duplicates)
#
#
# For example, to add "LINKBACK /etc/sysconfig/network-scripts/ifcfg-eth1 NODE"
# to the 'LINKBACK' section of /etc/sysimage.conf in the diskless image, run:
#
# # /opt/cmu/diskless/oneSIS/cmu_add_entry_to_file -f
${CMU_RCFG_PATH}/etc/sysimage.conf -k 'LINKBACK:' -e "LINKBACK /etc/sysconfig/network-
scripts/ifcfg-eth1 NODE"
#
# Note that for LINKBACK directives you also need to add a default classname,
# even if you don't plan on configuring the directive to use the class.
# An example of configuring nodenames with a syntax of "node[001-XXX]" to a
# "compute" class would be:
#
# # /opt/cmu/diskless/oneSIS/cmu_add_entry_to_file -f
${CMU_RCFG_PATH}/etc/sysimage.conf -k 'NODECLASS_REGEXP:' -e "NODECLASS_REGEXP node\d+
154 Advanced topics