beautypg.com

6 diskless check, 3 hp insight cmu remote hardware control api – HP Insight Cluster Management Utility User Manual

Page 117

background image

-n

<nodename>

The hostname 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.

7.2.6 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.

7.3 HP Insight CMU remote hardware control API

As of version 5.0, HP Insight CMU supports a remote hardware control API. This hardware API
makes it possible to integrate HP Insight CMU power and UID control with any computer that has
remote power control capability. The /opt/cmu/bin/cmu_power command interacts with this
API to provide remote power and UID control for HP Insight CMU.

As of CMU v7.1 the existing hardware APIs are:

ILO

The most common method of interacting with HP BL/DL/SL servers.

lo100i

The legacy method of interacting with low-end HP servers.

None

The fallback method of interacting with workstations and other servers that do not provide
remote power control.

IPMI

The industry standard method, useful with non-HP (or non-iLO HP) hardware.

7.3 HP Insight CMU remote hardware control API

117