Ironic Hardware Types & Interface Families Diagram

• 1. You create the node with driver=redfish; the API just stores that string in the node's driver column.
• 2. On load, the conductor looks up redfish in the ironic.hardware.types entry points and builds that class.
• 3. The class lists supported_<x>_interfaces - power, boot, deploy and ten more - in preference order.
• 4. The conductor intersects that list with enabled_<x>_interfaces from ironic.conf; the first survivor wins.
• 5. The winner's name is written to node.power_interface, node.deploy_interface and so on - one per family.
• 6. Out-of-band work (power, management, bios, firmware, console, vendor) goes to the BMC over Redfish or IPMI.
• 7. In-band work (deploy, rescue) needs the IPA ramdisk booted first; inspect, raid and boot can go either way.
• A hardware type is a bundle, not a driver: it only says which drivers are allowed and in what order.
• Deploy interfaces are exactly: anaconda, ansible, autodetect, bootc, custom-agent, direct, fake, noop, ramdisk - there is no iscsi one.