HP XC System Software Administration Guide Version 3.2

# updateimage --gc `nodename` --no-netboot
11.6.3 Exclusion Files
Exclusion files protect the golden image from being contaminated with node-specific content
from the golden client. While the golden client represents the configuration from which all other
nodes are replicated, the golden client is also an actively participating node, and has its own
configuration.
A simple example of the types of files to be excluded is a log file, one of many such files in the
/var directory. Log files contain node-specific log information. Other examples are configuration
files that reference the node's IP address and host name.
The image replication and distribution environment uses three separate exclusion files:
• /opt/hptc/systemimager/etc/base_exclude_file
Used during the initial creation of the golden image, which 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 image is created from the golden client, the golden client is configured,
and it takes on its node-specific personality. Any subsequent update to the golden image
should exclude those node-specific files from contaminating the golden image.
• /opt/hptc/systemimager/etc/updgi_exclude_file
Used when updating the golden image.
The /opt/hptc/systemimager/etc/updgi_exclude_file file has a stricter set of
exclude patterns than 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. For a detailed description of the syntax for exclusion files, see the EXCLUDE
PATTERNS section of rsync(1).
If you install additional software on the golden client that produces node-specific content,
you must edit the updgi_exclude_file file to add patterns for each node-specific file or
directory that you want to exclude, before updating the golden image. NFS-mounted file
systems on the golden client are automatically excluded from the golden image. You do not
need to include these in the updgi_exclude_file file.
11.6.4 Ensuring That the Golden Image Is Current
Use the updateimage command or thecluster_config command to ensure that the golden
image contains all the latest software for all the nodes. If you copy software directly to client
nodes without updating the golden image first, that software will be deleted from the client
nodes the next time the clients are re-imaged.
Choose the --no-netboot option to update the image if you do not want the client nodes to
network boot the next time they are rebooted or power cycled. Otherwise, the reboot or power
cycle causes a full reinstallation of the node software.
The --dry-run option enables you to verify which files would be added and deleted without
performing the operation.
11.7 Propagating the Golden Image to All Nodes
After you update the golden image successfully, and all nodes are optionally set to network boot,
you are ready to deploy the updated image to all client nodes. This section describes the methods
for distributing files to all the client nodes.
11.7 Propagating the Golden Image to All Nodes 149