| ... | @@ -12,7 +12,7 @@ After a successful CentOS installation a kickstart file can be found at ``/root/ |
... | @@ -12,7 +12,7 @@ After a successful CentOS installation a kickstart file can be found at ``/root/ |
|
|
The kickstart file is machine specific with regards to networking and partitioning configuration. But it can be made quite universal, if dhcp is used for the network setup and all nodes you want to install contain the same number of disks (and a minimum amount of space on each disk).
|
|
The kickstart file is machine specific with regards to networking and partitioning configuration. But it can be made quite universal, if dhcp is used for the network setup and all nodes you want to install contain the same number of disks (and a minimum amount of space on each disk).
|
|
|
|
|
|
|
|
## How do you (we) kickstart
|
|
## How do you (we) kickstart
|
|
|
* the node to be installed is konfigured for PXE boot (via ipmi configuration)
|
|
* the node to be installed is configured for PXE boot (via ipmi configuration)
|
|
|
* a DHCP server is present in the network and provides the PXE boot information (TFTP server address and path to bootstrap kernel)
|
|
* a DHCP server is present in the network and provides the PXE boot information (TFTP server address and path to bootstrap kernel)
|
|
|
* the node loads the bootstrap kernel (syslinux) and interprets the boot config file (default filename is known to PXE)
|
|
* the node loads the bootstrap kernel (syslinux) and interprets the boot config file (default filename is known to PXE)
|
|
|
* the config file either tells the node to boot from disk (regular boot) or to load another kernel with an initramfs and parameters (this triggers the installation)
|
|
* the config file either tells the node to boot from disk (regular boot) or to load another kernel with an initramfs and parameters (this triggers the installation)
|
| ... | | ... | |
