HP XC System Software Administration Guide Version 3.2

Whichever method you use to update the golden image, you can protect the golden image from
contamination with golden client (head node) specific personality by using an exclusion file.
This exclusion file is passed to the rsync command as a list of exclude patterns. For a detailed
description of exclusion files, and how to use exclusion files to manage software updates, see
“Exclusion Files” (page 149).
Note:
Before updating the golden image, make a copy in case you need to revert back. Use the
SystemImager si_cpimage command to perform this task. Ensure that you have enough disk
space in the target directory where the image will be saved; image sizes are typically 3–6 GB and
the size of a compressed tar file of an image is generally 1–3 GB.
The following command makes a copy of the default golden image, base_image, in the
/var/lib/systemimager/images directory. The saved image name in this example is
base_image.orig. You must run this command on the image server node, which is the head
node.
# si_cpimage --verbose --directory /var/lib/systemimager/images \
base_image base_image.orig
If you are preserving multiple images, save earlier versions as compressed archives using your
favorite compression utility to preserve disk space on the image server.
11.6.1 The cluster_config Utility
If you have added your own services to be deployed throughout the HP XC system by using the
per-node service configuration method described in “Using Per-Node Service Configuration”
(page 144), in conjunction with the information in “Adding a New Service” (page 76), you must
run the cluster_config utility on the head node again to ensure the Configuration and
management database (CMDB) is updated with the latest per-node service configuration and
the necessary configuration files updated on the head node. You must be the superuser (root)
to run this utility. The cluster_config utility performs the following tasks:
• Executes the global service configuration scripts.
• Updates the golden image automatically.
• Executes the node-specific configuration scripts on the head node.
NOTE: When the HP XC system is up and running, and you use the cluster_config utility
to change a role, you are prompted to reconfigure SLURM. If you answer no, the existing SLURM
configuration is preserved and is not modified in any way. However, if you made changes with
the cluster_config utility that affect SLURM, such as adding a compute node or moving a
resource management role, HP recommends that you answer yes to update the SLURM
configuration.
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 HP XC System Software Installation Guide fully describes the use of the cluster_config
utility and provides background information to the responses to the utility's prompts.
11.6 Updating the Golden Image 147