HP XC System Software Administration Guide Version 3.0

When the cluster_config 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
Nodes that have had their configuration changed are set to network boot. This causes the nodes to reinstall
themselves automatically, thus receiving the latest golden image. For nodes to be set to network boot, the
nodes must be operational. The cluster_config 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 environment manually for those nodes.
The updateimage Command
The updateimage command updates the golden image from the golden client; it does not run any service
configuration scripts. As superuser, you must run this command on the golden client node. The updateimage
command provides a --dry-run option. This option enables you to inspect the files that will be added to
(or deleted from) the golden image, without making any changes.
In the following example, the nodename command is executed and resolves to the node name of the golden
client:
# updateimage --gc `nodename` --dry-run
If you are satisfied with the list of files that will be updated in the golden image, issue the command to
perform the update:
# updateimage --gc `nodename`
When the updateimage command completes, the golden image is synchronized with the golden client
and the golden image tar file is updated. 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 administrative 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 command to update the golden image but keep the client nodes from network booting the
next time the nodes are rebooted:
# updateimage --gc `nodename` --no-netboot
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
Updating the Golden Image 85