... | @@ -17,7 +17,7 @@ The kickstart file is machine specific with regards to networking and partitioni |
... | @@ -17,7 +17,7 @@ The kickstart file is machine specific with regards to networking and partitioni |
|
* 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
|
|
* the kernel fetches the kickstart file from the NFS server and starts the install process
|
|
* the new kernel fetches the kickstart file from the NFS server and starts the install process
|
|
* the packages for the installation are also available over NFS (path is specified in the kickstart file)
|
|
* the packages for the installation are also available over NFS (path is specified in the kickstart file)
|
|
* the installation is fully automatic (if no problems occur) and can be monitored via ipmi sol
|
|
* the installation is fully automatic (if no problems occur) and can be monitored via ipmi sol
|
|
|
|
|
... | | ... | |