HP XC System Software Installation Guide Version 4.0

issues encountered when the golden client node disk configuration differs from the client disk
configuration.
You also have the flexibility to configure client node disks on a per-image and per-node basis
and to create an optional scratch partition. Partition sizes can be fixed or can be based on a
percentage of total disk size. You can set the appropriate variables in the /opt/hptc/
systemimager/etc/make_partitions.sh file or in user-defined files with a .part extension.
This section addresses the following topics:
• “Component Files Required for Dynamic Configuration of Client Node Disks” (page 206)
• “Example 1: Modifying Partitions Using Fixed Sizes and Defining an Additional Partition”
(page 207)
• “Example 2: Changing Default Partition Sizes and Swap Space for All Client Nodes” (page 208)
• “Example 3: Customizing Partition Sizes on a Group of Client Nodes” (page 209)
• “Example 4: Customizing Partition Sizes to Maximize File System Performance” (page 210)
E.2.1 Component Files Required for Dynamic Configuration of Client Node Disks
Dynamic disk configuration uses dynamic logic embedded in the component files described in
this section; these files are simple shell scripts.
Each component file is responsible for a portion of the client disk configuration during the
imaging installation and is sourced into the master autoinstallation script when the script is
created. The master autoinstallation script is created each time the cluster_config utility is
run.
The component files are as follows:
• /opt/hptc/systemimager/etc/make_partitions.sh
Identifies the client disk type and size and creates the default partition table. You edit the
variables in this file to modify the default partition sizes or swap space. Partition sizes can
be based on a fixed size or as a percentage of total disk size. Read the comments in the file
for more details.
• /var/lib/systemimager/scripts/{image_name}.part or
/var/lib/systemimager/scripts/{host_name}.part
Defines partition modifications on a per-image or per-node basis. These files are user-defined.
See “Example 1: Modifying Partitions Using Fixed Sizes and Defining an Additional Partition”
(page 207) for an example.
• /opt/hptc/systemimager/etc/make_filesystems.sh
Makes file systems of type ext3 and swap space on the partitions that were made by the
make_partitions.sh file. No user modifications to this file are required.
• /opt/hptc/systemimager/etc/make_fstab.sh
Creates a client disk device-specific /etc/fstab file on the client node. No user
modifications to this file are required.
• /opt/hptc/systemimager/etc/make_umount.sh
Unmounts the file systems that were created and mounted in the make_filesystems.sh
file. File systems are unmounted before the reboot of the client node, signalling the completion
of the autoinstallation imaging operation.
Each component file is a protected configuration file with respect to an RPM upgrade of the
package that delivers these files. What this means is that any customizations made to these files
will be preserved if the package delivering these files is upgraded through an rpm -U operation.
Each customized file is saved to an .rpmsave file extension so that the original file and associated
customizations are preserved when new versions of the file are delivered.
206 Customizing Client Node Disks