2026-02-03, 16:00–16:25, B.1.031
Foreman is a powerful - and complex - piece of software, especially if you want to use its Metal-as-a-Service functionality, or just simply provision bare metal on it.
What if we could strip it down to just a Rails service, without losing any of that functionality?
Setting up fully featured installs of Foreman with all its MaaS and lifecycle-management functionality requires a lot of surrounding configuration and software, and not just with static configuration either.
What if we could strip down Foreman to its Rails core, and still be able to do full Metal-as-a-Service with it?
This talk explores how to strip out the pieces of Foreman that require the use of Smart Proxies, instead leveraging iPXE, static DHCP configuration snippets, and a few small plugins.
All to allow the MaaS functionality to remain, but without requiring any of the dynamic configuration or network orchestrating that would normally be needed for them.
A Linux sysadmin with a bunch of programming experience.