24 | | The typical place to customize AII configuration is template [source:templates/trunk/sites/example/site/aii-config.tpl site/aii-config.tpl]. This template is executed quite late in the configuration, after completion of all the base OS configuration. Thus it is possible to make reference to most of the variables built during the configuration, in particular those reflecting OS flavour (version and arch) used. |
| 27 | === Controlling disks used by Kickstart === |
| 28 | |
| 29 | Among all the AII-related variables available, a few ones control disk where the GRUB boot loader is written to, which disks can be used by Kickstart during installation and what are the disks whose existing partition table must be cleared. In particular: |
| 30 | * `AII_OSINSTALL_BOOTDISK_ORDER`: list of disk name (without `/dev`) where to write GRUB boot loader. |
| 31 | * `AII_OSINSTALL_OPTION_CLEARPART`: list of disks (without `/dev`) whose existing partition table must be cleared by Kickstart. |
| 32 | * `AII_OSINSTALL_IGNOREDISKS`: list of disks (without `/dev`) whose existing partition table must be cleared by Kickstart. |
| 33 | * `AII_OSINSTALL_CLEARPART_BOOT_ONLY`: if false and nothing is explicitly specified, all disks managed by Quattor (present in `/system/blockdevices/physical_devs`) have their existing partition table cleared. If true, only disk having property `boot` defined to `true` in the hardware configuration (`/hardware/harddisks`) are cleared. Default is `false`. |
| 34 | |
| 35 | Default value for these variables should be appropriate as long as the hardware description for the machine is correct. In particular, all the disks present in the hardware configuration are added either to the list of disks whose existing partitions must be cleared or to the list of disks to ignore. When a machine has several disks, it is possible to define the property `boot` to `true` for the disk entry in `/hardware/harddisks` corresponding to the system disk (if there is only one disk, it is assume to be the system disk). |