HP XC System Software Administration Guide Version 4.0

When the updateimage command completes, the golden image is synchronized with the golden
client. You are ready to deploy the golden image to all the nodes in your HP XC system.
NOTE:
By default, the updateimage command sets all client nodes to network boot from their Ethernet
adapter, connected to the administration network, the next time the nodes are rebooted. This
causes the nodes to reinstall themselves automatically, thus receiving the latest golden image.
On CP6000 systems, for nodes to be set to network boot, the nodes must be operational. The
updateimage command displays any nodes that could not be reached and thus are not set to
network boot. This is a problem only on CP6000 systems because each node's EFI environment
must be modified. You must resolve the EFI environments manually for those nodes. If the node
is not operational when the updateimage command is run, you must set the nonoperational
nodes to network boot from the EFI boot menu the next time the nodes are booted.
The --no-netboot option of the updateimage command overrides this default action and
maintains the boot order for each client node.
Run the following commands to create a completely new golden image but keep the client nodes
from network booting the next time the nodes are rebooted:
# si_rmimage base_image
# updateimage --gc imageserver --no-netboot --init
11.5.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.
150 Distributing Software Throughout the System