HP XC System Software Installation Guide Version 2.1

for swap space), the /var partition is decreased to 29% of a vailable disk space (after
accounting for swap space), and the amount of swap space is decreased from 6 GB to 4 GB.
1. Use the text editor of your choice to open the /opt/hptc/systemim-
ager/etc/make_partitions.sh file and search for the block of text that looks
like this:
BOOT_PERCENTAGE=".01"
ROOT_PERCENTAGE=".60"
VAR_PERCENTAGE=".39"
2. Make the following changes to alter th e partitions sizes as a percentage of th e a vailable
disk space:
BOOT_PERCENTAGE=".01"
ROOT_PERCENTAGE=".70"
VAR_PERCENTAGE=".29"
3. Search for the block o f text t hat looks like this:
SWAP_SIZE1="2048"
SWAP_SIZE2="2048"
SWAP_SIZE3="2048"
4. Undefine the SWAP_SIZE3 variable to create a total of two swap partitions with 4 GB
of space:
SWAP_SIZE1="2048"
SWAP_SIZE2="2048"
SWAP_SIZE3=
Make sure there are no trailing or blank characters after the SWAP_SIZE3 variable.
5. Save y our changes to the file.
6. Run the cluster_config uti lit y to create a n e w master autoinstallation script
(/var/lib/systemimager/scripts/base_image.master.0) and generate
an updated version of the golden image:
# /opt/hptc/config/sbin/cluster_config
7. After the cluster_config utility com pletes its processin g, the clien t nodes are ready
to be installed. Do one of the following:
• If the client nodes have not been previously installed wi th th e XC System Software,
see Section 4.10 t o continue the initial installation procedure.
• If the client nodes were prev iou sly installed, issue the following sequence of
commands to set the nodes to network boot and reboot the client nodes:
# setnode --resync --all
# stopsys
# startsys
Wait until the stopsys comman d com pletes be fore inv oking th e startsys
command.
H.2.2 Example 2: Modify a Group of Client Nodes To Have Customized
Partition Sizes
This example increases the size of the /var partition only on the login nodes and retains the
default partition sizes on the com pute-only nodes. In this example, the newly-created copy
of th e master autoinstallation script (base_image.master.0) i s modified rather than
modifying the make_partitions.sh file as described in Section H.2.1; it is simpler to do
it this way. The base_image.master.0 file is not created until the cluster_config
utility is run as described in Section 4.8.
Customizing Client Node D isks H-3