HP XC System Software Administration Guide Version 3.1

RPCNFSDCOUNT: 8
xc_version: Version number
The table entry golden_image_md5sum identifies the MD5 checksum of the golden image file structure.
The table entry golden_image_modification_time identifies the date and time the current golden
image was created.
The table entry golden_image_tar_valid is set to 1 when the compressed tar file of the golden image
is created. It is set to 0 while the during the creation of the golden image tar file.
The table entry golden_image_valid is set to 1 when the golden image file structure is successfully
created. It is set to 0 while the golden image file structure is created. The startsys command uses these
flags to identify whether it is possible to image nodes successfully imaging operation is possible, based
on the state of the file structure and compressed tar file.
The golden image checksum and timestamp are imaged out to all nodes, by an override file, which allows
client nodes to identify their loaded image, relative to the golden image. The /var/hptc/gi_md5sum
file on each client node contains the checksum and timestamp. You can identify them as follows:
# cat /var/hptc/gi_md5sum
golden_image_md5sum=2e22d69e5c8b0bc0570b0dfffe5883a1
golden_image_modification_time=date and time stamp
A simple method to identify which nodes are running which versions of the golden image is as follows:
# # cexec -a -x `nodename` "cat /var/hptc/gi_md5sum" | dshbak -c
----------------
xc9n[1-511]
----------------
golden_image_md5sum=2e22d69e5c8b0bc0570b0dfffe5883a1
golden_image_modification_time=date and time stamp
10.6 Updating the Golden Image
Before you can deploy your software and configuration updates throughout the HP XC system, you must
update the golden image to synchronize with these changes. The golden image that is created during the
initial HP XC system configuration process is named base_image, and it exists in the file system hierarchy
under the directory /var/lib/systemimager/images.
You can update the golden image by using either of the following:
• The cluster_config utility
• The updateimage command
This section describes both methods.
Note:
Do not update the golden image file system directly. The golden image is a tar file that is compressed
for delivery during the multicast imaging operation. The cluster_config and updateimage utilities
ensure that the golden image file structure and tar file remain synchronized.
The rsync command is the underlying mechanism used by the cluster_config and updateimage
utilities to update the golden image. The rsync command provides an efficient method to update an
existing file set because it transfers only the differences between those two sets of files. As a result, the
update of the golden image is significantly quicker than its initial creation.
Whichever method you use to update the golden image, you can protect the golden image from
contamination with golden client (head node) specific personality by using an exclusion file. This exclusion
file is passed to the rsync command as a list of exclude patterns. For a detailed description of exclusion
files, and how to use exclusion files to manage software updates, see “Exclusion Files” (page 138).
136 Distributing Software Throughout the System