Let me answer to all of you, thanks for comments!
As the current maintainer of FDI, I’d learned over the past years that building and giving support for the current design is difficult. I want to shift from running multiple stacks and components on the image (smart-proxy, discovery service, network configuration and download services and TUI) to more simple approach when discovered node would simply register and bootstrap SSH channel with Foreman. All the rest (reboot, kexec, upgrade firmware) would be done via Remote Execution plugin. That’s the ultimate goal I would like to achieve at some point.
Debugging FDI is difficult, fixing bugs or development and rebuilding takes a lot of time. If there was just a minimum set of features (configure network, simple TUI for PXE-less, register and establish SSH keys) we would not need to update FDI that often.
There is a reason why FDI is based off CentOS, that is RHEL hardware certification. If a hardware is guranteed to work in RHEL, it will likely work on CentOS too. By the way, not much is really changing with CentOS Stream for majority of users, it was just poorly communicated. But this is not the right place for this discussion, if we simplify FDI enough, you can more easily build your very own FDI.
Also, if you compare size of FDI for the last 5 years, it has grown by about 200% because more and more firmware and drivers are added into RHEL kernel. We need to bring it back to reasonable size and I was trying hard to do this by removing some unwanted files (or drivers). The less software and dependencies we have, the better.
Good, I can bump this in my TODO a bit higher.
That does not mean I am starting next week tho, to clarify false expectations.