HP XC System Software Administration Guide Version 2.1

nodes m ust be operational. The updateimage com m
and display s any nodes t hat
could not be reached, and thus not set to network
boot. This may be a problem only
on X C6000 systems because each node’s EFI envi
ronment must b e modified. You
must resolve those nodes’ E FI environments m
anually.
The -no-netboot option of the updateimage command overrides this default action and
maintains the boot order for each client node.
Run the following command to upd ate the golden image but keep the c lient nodes fro m network
booting t he next time the no des are rebooted:
# updateimage --gc ‘nodename‘ --no-netbo
ot
7.3.3 Exclusion Files
Exclusion files protect the golden ima
ge from being contaminated with no de-sp ecific conten t
from the golden c li ent. While the gold
en client represents the configuration from which all
other nodes are replicated, the golde
n client is also an actively participating node, and has
its own co nfiguration personality.
A si m ple example of the types of files to b e excluded is a log file, one of many such files
in the /var directory. Log files contain node-specific log informatio n. Other examples ar e
configuration files that reference the no de’s IP address and hostname.
The i mag e replication and distribution environment uses three separate exclu sion files:
• /opt/hptc/systemimager/etc/b
ase_exclude_file
Used during the in itial creation of t he golden im age.
The /opt/hptc/systemimager/etc/base_exclude_file is used during
the initial creation of the golden image, w hich occurs as a result of executing the
cluster_config command. The golden client has very little personality at this time , so
this exclude file is fairly sparse.
After the initial golden ima
ge is created from the golden client, the golden c lien t is
configured, and it take s on i
ts per-node p ersonality. Any subsequ e nt up date to the golden
image sho uld exclud e those
personality-specific files from contaminating the golden image.
• /opt/hptc/systemimager/etc/updgi_exclude_file
Used w hen updating the golden image.
The /opt/hptc/systemimage
r/etc/updgi_exclude_file file has a stricter
set of exclude patterns th
an the base_exclude_file file.
The exclude files follow the rules for pattern exclusion based on the rsync command,
because the rsync command is the underlying method by which the golden image is
created and updated. See the EXCLUDE PATTERNS section of the rsync
(1) manpage
for a detailed description of t he syntax for exclusion files.
If you install additional software on the gold en client that produces node-specific conten t,
you should carefully edit the updgi_exclude_file file to add patterns for each
node-specific file or directory, before updating the gold en image. Note that NFS moun ted
file systems on the golden client are automatically excluded from the golden image, so there
is no need to i nclude t hese in the updgi_exclude_file file.
• /etc/systemimager/u
pdateclient.local.exclude
Used when updating nodes fro m the golden im age with the updateclient command.
The /etc/systemimager/updateclient.local.exclude file lists files and
directories resident on each client node. This exclude file protects these files and directories
from being overw ritten or deleted when the clien t node is updated from the golden image
with the updateclient utility.
7-6 Distributing Software Throughout the System