HP Integrity rx4640 Server - Manual (Page 7)

Configuring the Rapid Deployment Pack 7
Configuring scripted installs
Configuring scripted install jobs
The scripted install jobs use a small image to partition and format the disk. When deploying to a
server with multiple disks, either DAS or SAN, you might have to specify the system boot disk in the
job for the NTFS.img or GRUB.img images. For more information, see the “Configuring image
installs” section.
To specify a particular disk:
1. In the Deployment Server Console, copy, rename, and edit the job.
2. Modify the Distribute Disk Image task.
3. In the Additional Parameteres box, add the -dx switch, where x is an integer that represents the
appropriate disk number.
Additionally, for Red Hat Linux in a multiple disk scenario, the kickstart file must specify the system
boot disk.
1. On the Deployment Server, copy and rename the kickstart file.
2. Modify the new kickstart file by replacing the
autopart
command with separate part command
lines and adding the ---ondisk=XXX option to each where XXX is the device label.
Example for non-LVM:
part /boot --size 75 --ondisk=cciss/c0d0
part swap –size=1000 --ondisk=cciss/c0d0
part / --size 5120 -–grow --ondisk=cciss/c0d0
Example for LVM:
part /boot --size 100 --fstype=ext3 --ondisk=cciss/c0d0
part pv.01 --size=100 --grow --ondisk=cciss/c0d0
volgroup VolGroup00 -–pesize=32768 pv.01
3. In the Deployment Server Console, copy, rename, and edit the job.
4. Edit the Run Script – Create Boot Environment task in the new job to use the new kickstart file
created in step 2.
Configuring SAN-attached scripted install jobs
In addition to the steps in the “Configuring scripted install jobs” section, some further steps might be
necessary.
For VMware ESX Server 3.0.x:
Disconnect the SAN. After the operating system install is complete, reconnect the SAN and create a
VMFS datastore on it.