HP XC System Software Release Notes for Version 3.0

Enter s to perform customized services configuration on the nodes in your system.
• The ability to configure a node or nodes as a NIS slave server has been automated, thereby
eliminating the manual process that was required in previous releases.
If you modify the default role assignments and assign a nis_server role to configure one
or more nodes as a NIS slave server, you are prompted to enter the name of your NIS master
server or its IP address as well as your NIS domain name.
All functional changes to the system configuration process are documented in the HP XC System
Software Installation Guide.
1.8 System Imaging
The following changes have been made to the system imaging environment:
• The HP XC imaging environment is based on systemimager-3.4.1.
• The si_ prefix has been added to the names of all SystemImager commands in the
SystemImager open source kit. For example, the updateclient command is now called
si_updateclient.
• The si_updateclient command synchronizes client nodes with the golden image.
• A tar file is created from the golden image to enhance system imaging.
• A checksum of the golden image tar file is created to verify the integrity of the golden image.
The checksum ensures the golden image has not been modified during tar file creation. The
checksum is computed before and after tar file creation. You are notified if changes are
detected, and you have the option to terminate or continue the golden image creation.
A checksum file is also imaged to all nodes to provide a method for client nodes to verify
their loaded image relative to the golden image.
• System imaging logging has been enhanced. The imaging process for all nodes is captured
in the following log files:
— /hptc_cluster/adm/logs/imaging.log
— /var/log/systemimager/rsyncd
— /hptc_cluster/adm/logs/startsys.log
• To improve imaging performance, multicast imaging technology (provided by Flamethrower
and UDPcast) has replaced rsync for transferring the golden image file structure to client
nodes.
1.9 The startsys Command
Significant changes have been made to the startsys command that enable you to determine
which nodes require imaging and to image and boot nodes from a single command line:
• The --image_and_boot option images all the nodes that require imaging before booting
them. You can also select a subset of nodes for imaging and booting. You can specify options
to designate Flamethrower or the rsync utility for imaging the nodes.
• Using both the --image_and_boot and the --force options, you can image a node that
is already running.
• The --image_retry_count specifies the number of times to retry the imaging operation
on the target nodes.
• The --max_at_once limits the number of nodes that are booted at one time, thus helping
to eliminate a considerable drain on the site's power system.
• The --test option returns a list of all the nodes that require imaging.
Refer to the HP XC System Software Administration Guide and startsys(8) for details.
1.8 System Imaging 19