HP XC System Software Administration Guide Version 3.0

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.
• /etc/systemimager/updateclient.local.exclude
Used when updating nodes from the golden image with the si_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 overwritten or
deleted when the client node is updated from the golden image with the si_updateclient utility.
Note
The updateclient.local.exclude file is used specifically by the si_updateclient utility; it
has no effect when nodes are reimaged as a result of a client autoinstallation operation.
The updateclient.local.exclude file is resident on each node and referenced locally during
the si_updateclient operation. Update this file as you would update other software throughout
the HP XC system; that is, edit the /etc/systemimager/updateclient.local.exclude file on
the golden client, then incorporate it into the golden image with the updateimage command. The
updated image is distributed as described in “Propagating the Golden Image to All Nodes” (page 86).
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
re-installation of the node software.
The --dry-run option enables you to verify which files would be added and deleted without performing
the operation.
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.
86 Distributing Software Throughout the System