Changes between Version 35 and Version 36 of Doc/BasicConfig/AII


Ignore:
Timestamp:
Feb 27, 2011, 1:39:20 PM (13 years ago)
Author:
/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Michel Jouvin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Doc/BasicConfig/AII

    v35 v36  
    1212== AII Site Configuration ==
    1313
     14The typical place to customize AII configuration is the site-specific template pointed by variable `AII_CONFIG_SITE` or [source:templates/trunk/sites/example/site/aii-config.tpl site/aii-config.tpl] if the variable is not defined. 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, file systems configured...
     15
    1416All AII options may be customized through variables. For the complete list, look at the man pages ''aii-pxelinux(8)'' and ''aii-ks(8)''  or the source code [source:templates/trunk/standard/quattor/aii/ks/config.tpl standard/quattor/aii/ks/config.tpl] and [source:templates/trunk/standard/quattor/aii/pxelinux/config.tpl standard/quattor/aii/pxelinux/config.tpl].
     17
    1518
    1619A typical AII configuration is :
     
    2225}}}
    2326
    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
     29Among 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
     35Default 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).
    2536
    2637== Kickstart Site-Specific Installation Actions ==
    2738
    28 AII allows to define in a flexible way site-specific actions that must be done at various points in Kickstart. This is done through several `hooks`.
     39AII allows to define in a flexible way site-specific actions that must be done at various points in Kickstart/Anaconda. This is done through `AII hooks`. Writing and configuring hooks is not yet documented...
    2940
    3041== Configuration of Filesystems: The Recommended Way ==