Replacing Foreman with Waitron and pixiecore
From my experience provisioning of bare metal hardware is almost always a PITA, the system is either extremely fragile or too complex. The previous setup at my job had all of the above until we sat down and looked at the parts we actually needed. Our setup was based on Foreman which is a good tool but it tries to solve so many problems and we just cared about the base installation which can be solved by simpler and smaller tools. Foreman was basically used as a massive templating engine. So we simplified!
V2 Installation using Waitron and pixiecore
We replaced Foreman with two small applications written in Go, both running in a Docker contanier
- Waitron Templates preseed files and provide pixiecore with boot instructions based on machine definition
- pixiecore “PXE booting for people in a hurry”.
Machine definitions and preseed files moved git(Version control ftw!) instead of a database. The Machine definition is written in YAML.
#BaseURL is this waitron instance url, it is read from the config file
#Hostname is the hostname for this very host, it is read from this file
#Token is generated at runtime by waitron
cmdline: "interface=auto url=//preseed/ ramdisk_size=10800 root=/dev/rd/0 rw auto hostname= console-setup/ask_detect=false console-setup/layout=USA console-setup/variant=USA keyboard-configuration/layoutcode=us localechooser/translation/warn-light=true localechooser/translation/warn-severe=true locale=en_US"
- name: eth0
bar: "Hello world"
The machine definition is then used to template the preseed file and the boot file used by pixiecore
- Machine is set build mode using the Waitron API
curl -X POST http://waitron/<hostname>/build
- Tell machine to reboot and boot on PXE
- Machine boot using pixiecore which will fetch the information from
- Machine downloads the preseed/finish scripts from Waitron and notify waitron using the API when installation is complete.
- Machine is ready to be used by configuration management tool of choice