Comment 0 for bug 1528920

Ironic Inspector works by managing firewall access to a PXE port. It's done so that we can do inspection for nodes when ports are not known yet. Often enough, however, we do know ports. Also some boot procedures might not require PXE booting at all (e.g. virtual media). Ironic Inspector itself can't handle such cases, but Ironic can. This RFE suggests optional support for configuring DHCP properties and boot options for node on inspection.

1. Modify ironic inspector API to accept 'manage_boot' parameter (boolean, defaults to True). If it's set to False, inspector won't manage firewall or set boot device for this node, only power it on.
2. Modify InspectorInspect. Look at inspection_kernel and inspection_ramdisk in driver_info. If they're present, use the boot interface to configure booting them on a node, set boot device accordingly (PXE for pxe_ipmitool, but can be different for other drivers).
3. Add [inspector]require_manage_boot option defaulting to False. If it's True, inspect interface validation won't pass if inspection_{ramdisk,kernel} are not supplied.