HP XC System Software Installation Guide Version 2.1

• Use the static disk configuration procedure (Section H.3) when you want to create partition s
other than the default or if you want to create file system types oth er than the default
on the client disks.
H.2 Dynamic Disk Configuration
Dynamic disk configuration identifies the actual client disk device type and size during the
actual autoinstallation operation based on a list o f possible d isk architectures supported within
an XC conf iguration. This contrasts to attempting to predefine a static client disk configuration
based on the golden client (head ) no de. Doing so helps to avoid issues encountered when the
golden client node disk configuration differs from the client disk configuration.
Dynamic disk configuration uses dynamic logic embedded in the compon ent files described in
this section; these files are s imple shell scripts.
Each component file is responsible for a portion of the client disk configuration during t he
imaging instal lati on and is sourced into the master a ut oin s tall ation scr ipt during t he creation
of the master autoinstallation script. The master autoinstallation script is created each time
the cluster_config command is run.
The component files are:
/opt/hptc/systemimager/etc/make_partitions.sh
This component file is responsible for identifying the client disk type and size and creating
the default partition table. When changing the default sizes of partitions or swap space,
you will edit this file to effect the chan ge. Read the comm ents in the file for more details.
See the example in Section H.2.1 for information about how to make such a change.
OnOpteronorXeonsystems,the/, /boot,and/var partitions are created. On Itanium
systems, the /, /boot/efi,and/var partitions are created.
/opt/hptc/systemimager/etc/make_filesystems.sh
This comp onen t file is responsible for mak ing file systems of type ext3 and swap
space on the partitions th at were mad e by the make_partitions.sh file. No u ser
modifications are required t o this file.
/opt/hptc/systemimager/etc/make_fstab.sh
This component file is responsible for creating a client disk device-specific /etc/fstab
file on the client node. No user modifications are required to this file.
/opt/hptc/systemimager/etc/make_umount.sh
This compo nent file is responsible for unmounting the file systems that w ere 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 au toinstallation 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 m eans is that any customizations made to these
files will be preserved if the package delivering these files is upg raded through an rpm -U
operation. Each customized file is saved to a .rpmsave file extension s o that the original file
and associated customizatio ns are preserved when new versions of the file are delivered.
H.2.1 Example 1: Chang ing Default Partition Sizes and Swap Space Fo r
All Client Nodes
This example modifies the default partition sizes and the available swap space for all client
nodes. The size of the / partition is increased to 70% of available disk space (after accounting
H-2 Customizing Client Node Disks