Differences

This shows you the differences between two versions of the page.

--- notes:linux_automatic_network_install [2024/05/07 12:14] – [Directory structure] Nikita Kipriyanov
+++ notes:linux_automatic_network_install [2024/05/15 09:53] (current) – [Bootloader configuration] Nikita Kipriyanov
@@ Line 15: / Line 15: @@
 ===== Boot server configuration =====
-We can use ISC DHCPD + BIND + tftpd-hpa, or dnsmasq on the server side, and GRUB or PXELinux/SysLinux as downloadable Linux boot loader. GRUB is beneficial because it is a single piece of software that supports both “legacy” and EFI boot with a single set of configuration files; however, the prior development of this topic was focused on primarily PXELinux. The latter doesn’t support EFI boot, which can be supported by SysLinux (a sibling program), but there is a caveat: it doesn’t have a convenient way to make per-system dedicated boot configuration. Dnsmasq’s feature can be used to fill this gap. Overall, GRUB looks the most promising.
+We can use ISC DHCPD + BIND + tftpd-hpa, or dnsmasq on the server side, and GRUB or PXELinux/SysLinux as downloadable Linux boot loader. GRUB is beneficial because it is a single piece of software that supports both “legacy” and EFI boot with a single set of configuration files; however, the prior development of this topic was focused on primarily PXELinux. The latter doesn’t support EFI boot, which can be supported by SysLinux (a sibling program), but there is a caveat: it doesn’t have a convenient way to make per-system dedicated boot configuration. Dnsmasq’s feature can be used to fill this gap. Overall, GRUB looks more promising.
-==== Directory structure ====
+==== PXE bootloader ====
-All (more or less) dynamic data is t be stored in ''/srv/tftp'', which will be served via TFTP and HTTP. The latter is needed for EL:
+All (more or less) dynamic data is to be stored in ''/srv/tftp''. The structure of the directory:
-<tabbox PXELinux>
+<tabbox GRUB>
-<code>
+GRUB manual is available here: [[https://www.gnu.org/software/grub/manual/grub/]]
-srv/
-┠─ dhcp-hostsfile.cfg
-┗━ tftp/
-   ┠─ pxelinux.0
-   ┠─ ldlinux.c32
-   ┣━ pxelinux.cfg/
-   ┃  ┠─ harddisk
-   ┃  ┠─ menu
-   ┃  ┠─ debian-bookworm
-   ┃  ┠─ ol8u9
-   ┃  ┠─ default → menu
-   ┃  ┠─ docker-vm → harddisk
-   ┃  ┠─ test-pve → debian-bookworm
-   ┃  ┠─ test-lvm → ol8u9
-   ┃  ┠─ 01-bc-24-11-51-cf-fc → docker-vm
-   ┃  ┠─ 01-bc-24-11-4b-ae-dd → test-pve
-   ┃  ┖─ 01-bc-24-11-28-81-76 → test-lvm
-   ┣━ debian-bookworm/
-   ┃  ┠─ initrd.gz
-   ┃  ┠─ linux
-   ┃  ┖─ preseed-noswap.cfg
-   ┣━ debian-bookworm/
-   ┃  ┣━ images/
-   ┃  ┃  ┖─ install.img
-   ┃  ┠─ initrd.img
-   ┃  ┠─ ks.cfg
-   ┃  ┖─ vmlinuz
-   ┗━ gentoo/
-      ┠─ gentoo
-      ┖─ initramfs.igz
-</code>
-The most logic is within ''/srv/tftp/pxelinux.cfg'' directory. There are several boot configurations:
-  * ''harddisk'' — boot from local hard disk
-  * ''menu'' — present a human-friendly menu, with a timeout to do the same thing as ''harddisk''
-  * ''debian-bookworm'' — start an unattended installation of a Debian 12 release
-  * ''ol8u9'' — start an unattended installation of a Oracle Linux 8 release
-The rest items are symlinks to these files:
-  * ''default'' — will be used by PXELinux if no other configuration file was matched; here it symlinks to the ''menu'', but can be diverted anywhere else
-  * ''test-lvm'', ''test-pve'' and ''docker-vm'' are VMs or HW machines which are provisioned using this system, and in particular, ''test-lvm'' is being provisioned with OL8, ''test-pve'' is being provisioned with Debian and the ''docker-vm'' is already installed, so it is instructed to boot locally
-  * ''01-xx-xx-xx-xx-xx-xx'' are symlinks named after the respective system's MAC address. If there are several NICs, we create several files, for each MAC. PXELinux will first try such a file and load it if it exists, and if it doesn't, it will load ''default''. This way, we precisely target each system to divert its boot path independently of each other.
-This is well tested setup. The main downside is that PXELinux doesn't support EFI boot, and we need to use some another bootloader which is capable of targeting computers precisely and manage its configuration separately.
-<tabbox GRUB>
 <code>
@@ Line 92: / Line 46: @@
    ┃  ┠─ ol8u9
    ┃  ┠─ grub.cfg → menu
-   ┃  ┠─ docker-vm → harddisk
+   ┃  ┠─ docker-vm → localboot
    ┃  ┠─ test-pve → debian-bookworm
    ┃  ┠─ test-lvm → ol8u9
@@ Line 102: / Line 56: @@
    ┃  ┠─ linux
    ┃  ┖─ preseed-noswap.cfg
-   ┣━ debian-bookworm/
+   ┣━ ol8u9/
    ┃  ┣━ images/
    ┃  ┃  ┖─ install.img
@@ Line 134: / Line 88: @@
 Then the ''/srv/tftp/grub'' directory was simply archived and transferred to the boot server.
+<tabbox PXELinux>
+<code>
+srv/
+┠─ dhcp-hostsfile.cfg
+┗━ tftp/
+   ┠─ pxelinux.0
+   ┠─ ldlinux.c32
+   ┣━ pxelinux.cfg/
+   ┃  ┠─ harddisk
+   ┃  ┠─ menu
+   ┃  ┠─ debian-bookworm
+   ┃  ┠─ ol8u9
+   ┃  ┠─ default → menu
+   ┃  ┠─ docker-vm → harddisk
+   ┃  ┠─ test-pve → debian-bookworm
+   ┃  ┠─ test-lvm → ol8u9
+   ┃  ┠─ 01-bc-24-11-51-cf-fc → docker-vm
+   ┃  ┠─ 01-bc-24-11-4b-ae-dd → test-pve
+   ┃  ┖─ 01-bc-24-11-28-81-76 → test-lvm
+   ┣━ debian-bookworm/
+   ┃  ┠─ initrd.gz
+   ┃  ┠─ linux
+   ┃  ┖─ preseed-noswap.cfg
+   ┣━ ol8u9/
+   ┃  ┣━ images/
+   ┃  ┃  ┖─ install.img
+   ┃  ┠─ initrd.img
+   ┃  ┠─ ks.cfg
+   ┃  ┖─ vmlinuz
+   ┗━ gentoo/
+      ┠─ gentoo
+      ┖─ initramfs.igz
+</code>
+The most logic is within ''/srv/tftp/pxelinux.cfg'' directory. There are several boot configurations:
+  * ''harddisk'' — boot from local hard disk
+  * ''menu'' — present a human-friendly menu, with a timeout to do the same thing as ''harddisk''
+  * ''debian-bookworm'' — start an unattended installation of a Debian 12 release
+  * ''ol8u9'' — start an unattended installation of a Oracle Linux 8 release
+The rest items are symlinks to these files:
+  * ''default'' — will be used by PXELinux if no other configuration file was matched; here it symlinks to the ''menu'', but can be diverted anywhere else
+  * ''test-lvm'', ''test-pve'' and ''docker-vm'' are VMs or HW machines which are provisioned using this system, and in particular, ''test-lvm'' is being provisioned with OL8, ''test-pve'' is being provisioned with Debian and the ''docker-vm'' is already installed, so it is instructed to boot locally
+  * ''01-xx-xx-xx-xx-xx-xx'' are symlinks named after the respective system's MAC address. If there are several NICs, we create several files, for each MAC. PXELinux will first try such a file and load it if it exists, and if it doesn't, it will load ''default''. This way, we precisely target each system to divert its boot path independently of each other.
+This is well tested setup. The main downside is that PXELinux doesn't support EFI boot, and we need to use some another bootloader which is capable of targeting computers precisely and manage its configuration separately.
 </tabbox>
-Boot menu can contain more entries if needed, for example, it can boot [[https://wiki.gentoo.org/wiki/Installation_alternatives#Diskless_install_using_PXE_from_the_LiveCD|Gentoo LiveCD converted for PXE boot]]. It defaults to booting from hard disk after timeout.
+Boot menu can contain other entries if needed, for example, it can boot [[https://wiki.gentoo.org/wiki/Installation_alternatives#Diskless_install_using_PXE_from_the_LiveCD|Gentoo LiveCD converted for PXE boot]]. It defaults to booting from hard disk after timeout.
 We need some more work in preseed/kickstart/whatever autoinstall partitioning schemes, to support both "legacy" and EFI partitioning and boot settings, or develop another generation of autoinstall files for EFI and select which one to present in a bootloader.
+==== DNS, DHCP and TFTP servers ====
+<tabbox dnsmasq>
-==== dnsmasq ====
 The default Debian's ''dnsmasq'' configuration can use the base configuration //and// the drop directory. We opt to use the latter.
 The most configuration is ''/etc/dnsmasq.d/base.conf'':
 <file - /etc/dnsmasq.d/base.conf>
 no-dhcp-interface = tun0
+# upstream DNS
 server = 10.226.130.130
 server = 10.226.130.131
 no-resolv
-domain = test.ucom.am, 172.31.1.0/24,   local
+domain = auto.example.org, 172.31.1.0/24,   local
-domain = test.ucom.am, 172.31.255.0/24, local
+domain = auto.example.org, 172.31.255.0/24, local
 domain-needed
 expand-hosts
-# no dynamic allocation for DHCP service on this subnet; static allocation via dhcp-host will still be possible
+# no dynamic allocation for DHCP service on these subnets; static allocation via dhcp-host and dhcp-hostsfile will still be possible
 dhcp-range = 192.168.205.224, static
 dhcp-range = 172.31.255.0,    static
@@ Line 177: / Line 184: @@
 dhcp-match = set:http, option:client-arch, 16
-dhcp-boot = tag:bios, pxelinux.0
+dhcp-boot = tag:bios, grub.0
-dhcp-boot = tag:uefi, bootx64.efi
+dhcp-boot = tag:uefi, grub.efi
-#pxe-prompt = "Select a system to boot"
-#pxe-prompt = "Press F8 for menu.", 60
-#pxe-service = x86PC, "Boot from local disk"
-#pxe-service = x86PC, "Run pxelinux", pxelinux
 log-queries
@@ Line 189: / Line 191: @@
 </file>
-It references the ''/srv/dhcp-hostsfile.cfg'' where we can match certain MACs to IP addresses and names. This is mostly convenient for networks defined as "static DHCP ranges" above, since this way only hosts listed in the hostsfile will be provided a service. Also we can put other hosts there, for example, VMs, to fix IP addresses. Example contents is:
+It references the ''/srv/dhcp-hostsfile.cfg'' where we can match certain MACs to IP addresses and names. This is convenient for networks defined as "static DHCP ranges" above, since this way only hosts listed in the hostsfile will be provided a service. Also we can put other hosts there, for example, VMs, to pin IP addresses to somewhere outside the dynamic allocation range. Example contents is:
 <file - /srv/dhcp-hostsfile.cfg>
 BC:24:11:51:CF:FC, 172.31.1.5,  docker-vm
@@ Line 207: / Line 209: @@
 </file>
-I put auxiliary DNS records into a separate file too:
+Auxiliary DNS records are put into yet another separate file:
 <file - /etc/dnsmasq.d/dns-auxiliary.conf>
 cname = boot.test.ucom.am, vmgw.test.ucom.am
 </file>
-==== Mini HTTPD ====
+<tabbox ISC DHCPD, ISC BIND, tftpd-hpa>
-Needed for EL variants to be able to run installer from the network. We only set ''data_dir=/srv/tftp'' in ''/etc/mini-httpd.conf''; this directory is already served by TFTP; we can use a separate directory, but this setup feels simpler.
+  * [[https://www.hpe.com/psnow/resources/ebooks/a00112595en_us_v2/s_config_pxe_uefi.html|Configuring PXE servers for UEFI-based clients in a Linux environment]]
+</tabbox>
+==== HTTP server ====
+Needed for EL variants to be able to run installer from the network. I went as low as using ''mini_httpd'', the simplest I found. Only need to set ''data_dir=/srv/tftp'' in ''/etc/mini-httpd.conf''.
+This directory is already served via TFTP; we can use a separate directory, but this setup feels simpler. If it will be decided to serve private local repositories, which is infeasible to share over TFTP, it might be worth splitting the HTTP-only and TFTP-only parts.
-If it will be decided to serve private local repositories, which are infeasible to share over TFTP, we may revert the decision to serve everything via both protocols, and split HTTP-only part.
 ===== Debian: preseed ====
@@ Line 228: / Line 238: @@
 ==== Bootloader configuration ====
+<tabbox GRUB>
+<file - /srv/tftp/grub/debian-bookworm>
+set timeout=1
+menuentry 'Debian Bookworm PXE installer' {
+    linux debian-bookworm/linux priority=critical debian-installer/language=en debian-installer/country=AM debian-installer/locale=ru_RU.UTF-8 keyboard-configuration/xkb-keymap=ru netcfg/get_hostname=install keyboard-configuration/optionscode=grp:caps_lock_toggle,grp_led:scroll preseed/url=tftp://boot.test.ucom.am/debian-bookworm/preseed-noswap.cfg
+    initrd debian-bookworm/initrd.gz
+}
+</file>
+<tabbox PXELinux>
 <file - /srv/tftp/pxelinux.cfg/debian-bookworm>
 default debian-bookworm-auto
@@ Line 235: / Line 260: @@
     kernel debian-bookworm/linux
     append priority=critical initrd=debian-bookworm/initrd.gz debian-installer/language=en debian-installer/country=AM debian-installer/locale=ru_RU.UTF-8 keyboard-configuration/xkb-keymap=ru netcfg/get_hostname=install keyboard-configuration/optionscode=grp:caps_lock_toggle,grp_led:scroll preseed/url=tftp://boot.test.ucom.am/debian-bookworm/preseed-noswap.cfg
 </file>
+</tabbox>
 ==== Example preseed file ====
 Works for Bullseye too (it was actually originally developed for Bullseye, but worked with Bookworm like a charm)!
+<tabbox BIOS>
 <file - /srv/tftp/debian-bookworm/preseed-noswap.cfg>
@@ Line 365: / Line 394: @@
   in-target chmod 0600 /root/.ssh/authorized_keys;
 </file>
+<tabbox UEFI>
+</tabbox>
 ==== Additional documentation ====
@@ Line 389: / Line 422: @@
 ==== Bootloader configuration ====
+<tabbox GRUB>
+<file - /srv/tftp/grub/ol8u9>
+set timeout=1
+menuentry 'Oracle Linux 8 PXE installer' {
+    linux ol8u9/vmlinuz inst.repo=http://vmgw/ol8u9 inst.ks.sendmac inst.ks=http://vmgw/ol8u9/ks.cfg
+    initrd ol8u9/initrd.img
+}
+</file>
+<tabbox PXELinux>
 <file - /srv/tftp/pxelinux.cfg/ol8u9>
 default ol8u9
@@ Line 397: / Line 444: @@
 # it will append .../images/install.img or .../LiveOS/squashfs.img
 </file>
+</tabbox>
 ==== Example kickstart file ====
+<tabbox BIOS>
 <file - /srv/tftp/ol8u9/ks.cfg>
 #platform=x86, AMD64, or Intel EM64T
@@ Line 505: / Line 557: @@
 %end
 </file>
+<tabbox UEFI>
+</tabbox>
 ==== Additional documentation ====
   * https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/boot_options_for_rhel_installer/index