beautypg.com

3 autoinstall compute nodes, 6 customization – HP Insight Cluster Management Utility User Manual

Page 47

background image

cmu> add_to_logical_group node1 to rh5u5_autoinst
selected nodes: node1
processing 1 node ...
cmu>

Or:

# /opt/cmu/bin/cmu_add_to_logical_group_candidates -t rh5u5_ autoinstall node1 node2
processing 2 nodes...

4.2.5.3 Autoinstall compute nodes

To autoinstall a node, enter the following command at the cmucli prompt:

cmu> autoinstall "image" node1

For example:

cmu> autoinstall "rh5u5_autoinst" node1

or

/opt/cmu/bin/cmu_autoinstall_node -1 rh5u5_autoinst -f nodes.txt

Where nodes.txt is the list of nodes to autoinstall.

4.2.6 Customization

The /opt/cmu/etc/cmuserver.conf file includes an autoinstall section with several groups
of variables. A brief description follows. For a full description of the autoinstall configuration
variables, see cmuserver.conf.

autoinstall
template files
variables

This is a “read only” section that lists the variables HP Insight CMU can substitute, if
present, in autoinstall templates.

For example, a Red Hat kickstart file normally has a keyword “nfs –server” followed
by the IP address of the server exporting the Red Hat repository. When running HP
Insight CMU autoinstall for Red Hat kickstart, replace the IP address with CMU_MGT_IP.
HP Insight CMU makes the substitution.

For another example, you normally specify the default gateway to configure on the
node in the autoinstall template files. With HP Insight CMU autoinstall, you can replace
the real IP address of the default gateway with the variable CMU_MGT_GW. HP Insight
CMU replaces the variable. If you do not want HP Insight CMU to make the replacement,
do not use the variable in your template. Instead, use the real value.

customized title
bars

The variable CMU_CLUSTER_NAME can be changed to an arbitrary string (or left unset)
to provide GUI and CLI title customization.

pxelinux
parameters

Variables in this section contain the HP Insight CMU default parameter list for pxelinux.
Change the pxelinux parameters by editing variables in this section.

For example, if your compute nodes use ttyS1 as the console port for a Red Hat
autoinstall, change the value of CMU_KS_KERNEL_PARMS by replacing “console=ttyS0”
with “console=ttyS1”. For all subsequent creations of Red Hat autoinstall logical groups,
ttyS1 is used as the default value for the console port instead of ttyS0. To change
pxelinux parameters for a single compute node, edit the
pxelinux-[compute_node_hostname]

file in the autoinstall logical group directory.

The changes are permanent because this file is not overwritten by subsequent
autoinstalls. To change pxelinux parameters for a single autoinstall logical group, edit
the pxelinux_template file in the autoinstall logical group directory.

timeout
parameters

Allow modification of timeout values for different phases of the autoinstall process. For
example, if disk formatting takes a long time due to large disk size, you may need to
increase CMU_AUTOINST_INSTALL_TIMEOUT.

4.2 Autoinstall

47