iPXE dynamic configuration
The current iPXE support depends on configuration files to be cached in the disk. This creates a dependency between a given ironic-conductor a given node (even without a conductor lock on a node) because that ironic-conductor is the only one able to boot that node. This also makes take-over more complicated because the new ironic-conductor will need to regenerate the iPXE configuration files for the new nodes it's now managing and update the DHCP server accordingly.
This blueprint adds support for dynamically generating iPXE configuration files when booting a node.
Blueprint information
- Status:
- Started
- Approver:
- None
- Priority:
- Low
- Drafter:
- Lucas Alvares Gomes
- Direction:
- Approved
- Assignee:
- Lucas Alvares Gomes
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Started
- Milestone target:
- None
- Started by
- Lucas Alvares Gomes
- Completed by
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Change return value of [driver_
Addressed by: https:/
Refactor node's and driver's vendor passthru to a common place
Gerrit topic: https:/
Addressed by: https:/
Allow vendor methods to serve static files
Hi Lucas, please track further work here - https:/
//vdrok 2015-12-15
