Pxe configuration for booting windows
Currently Ironic uses the kernel and initrd out of the installed image and configures the node to pxe from that kernel and initrd. This behavior will not work when deploying windows images onto iron.
In order to have pxe be the default boot behavior and be able to boot the windows instance, the pxe config for the newly deployed windows image should be "localboot 0" rather than suppling a kernel and initrd. This will allow the node to have a default boot behavior of pxe first while allowing still allowing it to physically boot the newly deployed windows image.
Blueprint information
- Status:
- Complete
- Approver:
- aeva black
- Priority:
- Low
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Superseded
- Series goal:
- Accepted for icehouse
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- aeva black
Related branches
Related bugs
Sprints
Whiteboard
I think the technical work of serving the "localboot 0" pxe option is trivial -- just a change to the template file. The bigger question is, how will the Ironic PXE driver know when to serve that template -- can we conclusively interpret whether the image contains a windows vs. Linux OS from some already-existing metadata, or do we need to introduce a new tag to Nova / Glance?
-Deva, 2012-11-12
Example change from Peter, would need some clean up before we can merge:
https:/
first stab at windows support, to enable just change the default template in config
