xenapi: Added iPXE ISO boot support
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-manuals |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
https:/
commit 2459d0fb2af37d5
Author: Josh Kearney <email address hidden>
Date: Thu Jul 18 13:57:54 2013 -0500
xenapi: Added iPXE ISO boot support
This gives customers (of service-providers running XenAPI) a means to roll
their own image.
The service-provider supplies an ISO with iPXE support rolled into it and then
the customer can choose that image, boot to an OS of their choosing, then the
customize the image in anyway they want.
Two virt-layer modifications were needed. The first was adding configurations
for the iPXE ISO feature (network to use, boot menu, mkisofs_cmd). The second
was the ability to inject networking info into the ISO after it was
downloaded.
This was accomplished via a new post-image-download hook (fixup_disks) and a
new dom0 plugin that knows how to mount an ISO, copy it, inject networking,
rebundle it, and place the modified version back into the SR.
DocImpact
Change-Id: I33acf9dfdff0a5
Changed in openstack-manuals: | |
milestone: | none → havana |
tags: | added: xen |
Changed in openstack-manuals: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in openstack-manuals: | |
milestone: | havana → juno |
Changed in openstack-manuals: | |
milestone: | juno → kilo |
Changed in openstack-manuals: | |
milestone: | kilo → liberty |
This is currently blocked by the blueprint: redocument-xen