Follow-up on iso boot spec

Following up on some discussion related changes (both in review)
and in chat to the spec document for the purposes of clarity.

Change-Id: I342bffbc320c1f6296f4d9d0fcbd5add87059d3a
This commit is contained in:
Julia Kreger 2020-05-18 07:27:50 -07:00
parent 9baf915d7a
commit ec01f7e4c9
1 changed files with 4 additions and 7 deletions

View File

@ -36,18 +36,14 @@ Proposed change
* Allow a ``instance_info/boot_iso`` parameter to be leveraged to be
the medium utilized for booting from an explicit ISO image which the
conductor would support downloading, caching, and providing to the
baremetal machine.
baremetal machine. This change would be focused on the virtual media
boot interface code in relation to usage of Redfish.
* Teach the code related to the pass-through to provide the same basic
capability to append parameters to the command line through decomposition
of the ISO, appending to ``grub2`` and ``isolinux`` configurations with
the supplied values, and repackaging of the ISO file for deployment.
* Optionally: Enable the glance image ``image_source`` code to support this
path for iso booting. This could potentially allow the OpenStack Nova
virt driver for ironic to enable booting of instances from ISO mediums,
however this is out of scope.
Alternatives
------------
@ -167,7 +163,8 @@ Work Items
* Implement support to pass an explicit boot ISO into the ramdisk interface.
* Implement support to inject configuration into the boot ISO.
* Document this functionality for the ramdisk interface.
* Document this functionality for the ramdisk interface covering how to
leverage this feature.
Dependencies
============