HP XC System Software Administration Guide Version 2.1

As mentio ned above, the database should be the de
stination for per-node specific data.
However, som e existing services may already pl
ace configuration data used by t he service
in files in known locatio ns. The golden c lien t
file system and the cluster common storage
are available to support such applications.
Global service configuration scripts are located in the /opt/hptc/etc/gconfig.d
directory.
• Node-Specific Configuration
The node-specific service configuration
step uses the results of the global service
configuration step described previousl
y to apply to a specific node its personality with
respect to the service. U ser interactio
n is not permitted because this step runs on a per
node basis.
The configuration of the service is accomplished in a script called by the node-specific
service configuration controller (nconfig)script.Thenconfig controller scri pt runs at
system startup, and identifies whether it is executing as part of the initial bo ot of a client
node after an installation operation. If so, the nconfig controller script queries the cmdb
to determine which node-specific service configuration scripts to execute, thus providing
the per-node personality to each node.
Per node configuration scripts are located in /opt/hptc/etc/nconfig.d directory.
7.3 Updating the Golden Image
Before being able to deploy your softw are a nd co nfiguration up dates th rou ghout the HP
XC system, the golden image must be updated to synchronize with these changes. The
golden im age that is created during the init ial HP XC system configuration process
is named base_image, and exists in the file system hierarchy under the directory
/var/lib/systemimager/images.
The gold en image can b e updated by using either of two utilit ies:
•Thecluster_config utilit
y
•Theupdateimage command
Both methods are described below.
It is not recommended to up
date the golden im a ge file system directly, unless th e golden client
file system is also consis
tently modified. This ensures that the golden client and golden image
remain synchronized.
The rsync command is th e underlying utility used by the cluster_config and
updateimage utilities to update the golden image. The rsync command provides an
efficient method to update an e xisting fileset because it only transfers the differences between
those two sets of files. As a result, the update of the g old en image is significantly quicker
than its initial creation.
Whichever method is used to update the golden image, the golden image is protected from being
contaminated with golden client (head node) specific personality by the use of an e xclu sion
file. T his exclusion file is passed to the rsync command as a list of exclude patterns. See
Section 7.3.3 for a more detailed description of exclu sion files, and how to use ex clusio n files to
manage software u pdates.
_________________________ Note _________________________
Before updating t
he golden image, make a copy in case you need to revert back.
The SystemImager
cpimage command performs this task. Image sizes are
typically on the
order of 2-4G B ; ensure that you have enough disk space in the
target director
y where the image will be saved.
7-4 Distributing Software Throughout the System