Add vmedia boot support in ramdisk element
Bug #1321564 reported by
Ramakrishnan G (rameshg87)
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
diskimage-builder |
Fix Released
|
Wishlist
|
Ramakrishnan G (rameshg87) |
Bug Description
Currently the ramdisk element assumes that the parameters for the deploy are passed through kernel command-line.
But when the kernel/ramdisk is booted over virtual cdrom media (using isolinux instead of pxelinux), the parameters to deploy are passed inside a text file (like parameters.txt) inside the virtual floppy media by the IloDriver. By doing so, saves the creation/
When the parameters is passed through virtual floppy media, there will be a new kernel command line argument added (boot_method=
Changed in diskimage-builder: | |
assignee: | nobody → Ramakrishnan G (rameshg87) |
Changed in diskimage-builder: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
Changed in diskimage-builder: | |
status: | Triaged → In Progress |
Changed in diskimage-builder: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
UseCase:
Currently the main user of this change will be the proposed IloDriver in Ironic Project /review. openstack. org/97744)
(See design spec: https:/
The admin will package the deploy kernel and ramdisk into a bootable iso image. A new kernel argument boot_method=vmedia will be added in the ISO as kernel command-line argument. During deploy, IloDriver will attach this bootable iso image as virtual media on the HP Proliant machine. The arguments to be passed to the ramdisk are passed through virtual media floppy. This is where this change comes in. If the baremetal node booted via virtual media, then the arguments are read from the virtual media floppy.