Figure 23 Cloning statusWhen cloning is complete, a popup window displays the results.

The correctly cloned compute nodes appear in the chosen logical group. The compute nodes that failed remain in the default logical group.

The cloning feature duplicates the software installation configuration from an installed Linux system to systems with similar hardware configurations. This function eliminates the time-consuming task of system installation and configuration for each node in the cluster.

The cloning procedure has the following limitations:

•The cloning procedure does not clone the HP Smart Array hard drive configuration. This type of cloning must be done manually before the cloning.

•The cloning procedure does not setup the BIOS parameters as PXE-enabled and Wake-On-LAN enabled. This configuration must be done by the system administrator during cluster integration.

For more information about cloning mechanisms, see “Cloning mechanisms” (page 120).

Use the following conditions to determine if cloning was successful:

•Successfully cloned nodes are added to the logical group containing the image. The remaining nodes are added to the default logical group.

•In the logical group that contains the image, if the node name is preceded by an I (Inactive), then the cloning process failed on the node. If the node name is preceded by an A (Active), then the cloning process is successful on the node.

•The list of successfully cloned nodes is in the /opt/cmu/log/cmucerbere.log file.

4.4.1Preconfiguration

You can customize the actions to perform on each compute node before starting the cloning process. During cloning, after the node netboots and downloads the cloning image header files, an automatic preconfiguration script is launched on each node. This pre_reconf.sh script is unique for each image.

When a new backup image is created, a default reconfiguration file is copied from /opt/cmu/ etc/pre_reconf.sh to /opt/cmu/image/myimage/pre_reconf.sh. You can customize this template by editing the /opt/cmu/image/myimage/pre_reconf.sh file.

The script is executed before hard drive partitioning and formatting begins on each of the nodes. The pre_reconf.sh script can be used, for example, to flash the hard drive firmware and enable write cache with hdparm.

4.4 Cloning 51