MAAS has very interesting workflow where it makes sure that BMC is provisioned (with custom user and password) before operating system provisioning takes place. This is very useful, because when large batch of servers comes you just plug your machines and it automatically provisions your BMC, auto discovers facts and the powers off machine through BMC till the time when admin is ready to deploy operating system on it (in our case this could be weeks) and then it even automatically sets boot to pxe. You can even run hardware tests BEFORE installing operating system to make sure machines are not faulty or DOA. It is not acceptable for machine to be powered on and sitting in discovery for weeks. It is not acceptable to install operating system right away because we don’t know fqdn for those machines till we need them. I can’t imagine how to do such workflow in foreman. It seems discovery image doesn’t do anything with BMC (except only discovering network details of already configured BMC interface) and there is no place in the workflow before installing operating system itself, when/where to configure BMC. Help?
BMC is configured before operating system is installed. BMC ip should be taken from foremans ipam.
Foreman and Proxy versions:
Foreman and Proxy plugin versions:
Distribution and version:
Other relevant data: