HP Insight Cluster Management Utility Support for ScaleMP, Cloning mechanisms, CMUvSMPPREFIX=vSMP

etc/bootopts/AC14000. The hexadecimal IP address AC14000 covers IP addresses 172.20.0.1

-172.20.0.15.

7.5Support for ScaleMP

HP Insight CMU can be integrated to work with ScaleMP. To enable support for ScaleMP, add the following variable and setting to the /opt/cmu/etc/cmuserver.conf file:

CMU_vSMP_PREFIX=vSMP_

This setting configures the prefix that is used to identify HP Insight CMU logical group nodes that can be pxe-booted into the virtual SMP environment. The images that are associated with these logical groups can be created with normal HP Insight CMU methods (such as autoinstall and cloning), or made diskless. The ScaleMP support is activated when nodes that are active members of a logical group named "vSMP_*" are pxe-booted.

If a logical group named "vSMP_*" is a diskless image, then those nodes pxe-boot the diskless image into the virtual SMP environment.

If a logical group named "vSMP_*" is a disk-based image, then those nodes must be actively pxe-booted by selecting network boot in the boot menu.

The first node listed as "active" in the logical group named "vSMP_*" is the primary node in the virtual SMP environment. The remaining nodes are the secondary nodes.

For more details, see the ScaleMP documentation.

7.6 Cloning mechanisms

The cloning process requires you to create logical groups. A logical group is a collection of nodes that share the same operating system image. Each logical group is defined under the /opt/cmu/ image directory on the image server. This directory contains the target system disk partition information and compressed image of the selected partitions from a master disk. The backup utility provides a mechanism to backup the master disk image of the logical group of a node.

A logical group can contain nodes from one or more network entities. By default, HP Insight CMU puts all nodes in the default logical group. HP Insight CMU supports multiple logical groups for a cluster. This enables the cluster to be configured to meet the needs of several user types. A logical group can only contain nodes of similar server machines because they share the same operating system image.

A cluster of nodes generally has several racks. Each rack has one Ethernet switch. For the best network performance during cloning, all nodes belonging to a single rack must be configured in an HP Insight CMU network entity. When you clone a group of nodes belonging to different network entities, one node per network entity is elected as the secondary server. Only one secondary server exists in each network entity. A copy of the TFTP root directory and the cloning database is transferred to each secondary server. All secondary servers boot in a pipeline on the primary server and each one of these servers must boot between 1 (0) and 64 (63) compute nodes.

The TFTP root directory is stored in memory (ramdrive) on each secondary server and on the hard drive for the primary server which is usually the HP Insight CMU management node. The TFTP root directory of the HP Insight CMU management node is shared among all the secondary servers.

The TFTP directory of each secondary server is shared among all nodes of the network entity of the secondary server.

When a node is booted, it mounts the local system disk and checks the partitions against the clone image partition information. If the descriptions differ, the node changes the local disk partition and rebuilds file systems. When the partitioning is correct, each node waits for the clone image to download. In the first part of the propagation, only secondary servers are enabled to receive the clone image.

When all secondary servers own a copy of the clone image, the primary server stops the propagation and each secondary server pushes its clone image to all nodes in the network entity.

120 Advanced topics