[RFE] promote iPXE to separate boot interface
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Fix Released
|
Wishlist
|
Pavlo Shchelokovskyy |
Bug Description
This bug is related to https:/
Currently we have a global per-conductor setting pxe.ipxe_enabled,
and our current PXEBoot interface code is riddled with "if ipxe_enabled then ...".
The proposed change is to promote iPXE to a separate iPXEBoot interface, that will be using dynamic iPXE configuration.
The upside is that iPXE vs PXE could be than configured per-node by setting an appropriate driver. As enabled_drivers is set in config by the operator, the necessity to deploy/configure the extra TFTP server for PXE or "caching" HTTP server for images with iPXE on each conductor can be inferred from what drivers are enabled.
The downside is of course a new driver explosion (which could be alleviated with driver composition reform).
summary: |
- promote iPXE to separate boot interface + [RFE] promote iPXE to separate boot interface |
Changed in ironic: | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |
tags: | added: needs-spec |
Changed in ironic: | |
assignee: | nobody → Pavlo Shchelokovskyy (pshchelo) |
tags: |
added: rfe-approved removed: needs-spec rfe |
Changed in ironic: | |
status: | Confirmed → Fix Released |
Related fix proposed to branch: master /review. openstack. org/385572
Review: https:/