Comment on **How** should I properly document my homelab?
fruitycoder@sh.itjust.works 1 week agoYep! Metal3 for servers with BMCs Tinkerbell for everything else.
I also have an ansible playbook that templates everything into a cloud init scripts as a boot strap server.
About 12 nodes in total now, from new servers to freebee junk laptops in it.
hoppolito@mander.xyz 6 days ago
Interesting, so Metal3 is basically kubernetes-managed baremetal nodes?
Over the last years I’ve cobbled together a nice Ansible-driven IaC setup, which provisions Incus and Docker on various machines. It’s always the ‘first mile’ that gets me struggling with completely reproducible bare-metal machines. How do I first provision them without too much manual interference?
Ansible gets me there partly, but I would still like to have e.g. the root file system running on btrfs which I’ve found hard to accomplish with just these tools when first provisioning a new machine.
fruitycoder@sh.itjust.works 5 days ago
Yep! It uses open stacks Ironic under the hood, but tracks config and stack via k8s.
For OS building I’ve been moving to Elemental which builds OS images from container images and cloud init scripts into Suse Micro immutable OSs (which use btrfs for the snapshot management under the hood for updates).