| ... | @@ -14,6 +14,7 @@ The kickstart file is machine specific with regards to networking and partitioni |
... | @@ -14,6 +14,7 @@ The kickstart file is machine specific with regards to networking and partitioni |
|
|
## How do you (we) kickstart
|
|
## How do you (we) kickstart
|
|
|
* the node to be installed is configured 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 DHCP server identifies the node by MAC address, so it has to be known beforehand
|
|
|
* 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 (in our setup 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 (in our setup this triggers the installation)
|
|
|
* the kernel and initramfs were part of the CentOS 7 iso and the additional parameters specify a NFS path to a kickstart file
|
|
* the kernel and initramfs were part of the CentOS 7 iso and the additional parameters specify a NFS path to a kickstart file
|
| ... | | ... | |
