6 boot diskless node, 7 diskless check, 6 boot diskless node 8.2.7 diskless check – HP Insight Cluster Management Utility User Manual

Page 144

Advertising
background image

-i

<IP address>

The IP address of the target node to unconfigure.

The unconfigure_node program is expected to unconfigure and/or remove anything related
to the given node. This may include calling /opt/cmu/tools/cmu_remove_node_from_dhcp
to prevent the node from PXE-booting, and to delete any PXE-boot file related to the given compute
node.

8.2.6 Boot diskless node

The boot_node program is called when a compute node is booted from HP Insight CMU into the
HP Insight CMU diskless logical group of type <DISKLESS> (as opposed to a reboot command
from the OS). This program is called with the following arguments:

-l

<CMU diskless logical group name>

The name of the diskless logical group.

-s

<NFS server IP>

The IP address of the NFS server.

-n

<nodename>

The host name of the target node to boot.

-i

<IP address>

The IP address of the target node to boot.

-m

<MAC address>

The MAC address of the target node to boot.

-e

<eth device>

The active Ethernet device of the target node to boot.

The boot_node program is typically a subset of the configure_node program, and ensures
that the given node is ready to be PXE-booted. It may call
/opt/cmu/tools/cmu_add_node_to_dhcp

again, and may check that the correct PXE-boot

file is in place for the given node.

8.2.7 Diskless check

The diskless_check program is called before the configure_node, unconfigure_node,
or boot_node programs are called. This program is called with the following arguments:

-l

<CMU diskless logical group name>

The name of the diskless logical group.

The diskless_check program is intended to contain any sanity checks that should be performed
before the configure_node, unconfigure_node, or boot_node programs are called. It can
also be called directly by the build_image program, to ensure that any prerequisites are met
before the diskless image is created. For example, the system-config-netboot implementation
requires that the system-config-netboot rpm provided by HP Insight CMU be installed on
the HP Insight CMU management server. A check for the existence of this rpm is performed by the
cmu_system-config-netboot_diskless_check

program.

After these programs are created, tested, and installed in the /opt/cmu/
diskless/

<DISKLESS>/ directory, then you are ready to add this implementation "toolkit"

to HP Insight CMU. To do this, add the <DISKLESS> implementation type to the
CMU_VALID_DISKLESS_TOOLKITS

variable in /opt/cmu/etc/cmuserver.conf.

NOTE:

If more than one valid diskless type will be available in HP Insight CMU, this variable

must be comma-separated.

144 Advanced topics

Advertising