Untangle spaghetti of the bare metal images and modes
summary
Operators favor ramdisk deploy and kexec over building disk images, and one vote for partition images versus two for whole-disk images is reported; most nodes still use legacy boot while UEFI adoption rises and secure boot toggling via Redfish is feasible but uneven. Hardware RAID on iLO lacks a secure-erase path without breaking arrays, image-builder is barely maintained and causes downstream fixes, torrent/rsync and ZFS snapshotting are proposed, and a powered-off snapshot requirement is a practical first step.
AI-written summary · about
chapters (12)
- 0:00Introduction and setup
- 1:53Writing images on nodes today
- 5:08Agent vs Ansible deployment
- 10:05Image types and boot modes
- 15:50Alternative image formats
- 19:12Partitioning and architectures
- 26:47RAID and hardware limitations
- 29:16Snapshotting bare metal
- 36:56Anaconda and kickstart scripts
- 42:17Snapshotting and update steps
- 45:06Image builder maintenance
- 48:20Closing remarks
related talks
49mEmbedded Linux BOF
34mDevice provisioning at the Edge
01h 01mDiskless Booting of RPi 400 Using Bootp, tftp, iscsi and NFS
33mU-Boot's New Standard Boot and What's Next
49mGeneric System for Safe Rootfs/Kernel Upgrades without Single-Point of Failure
41mCase Study: Switching from Asymmetric to Symmetric Software Updates
33mBuilding Secure & Reliable Edge Images Using RHEL for Edge Blueprinting & OSTree
21mGetting started with LinuxBoot Firmware on AArch64 Server