Revise ramdisk boot interface for clarity
Change-Id: I55351989793b858aab1dadb55f35f96a758ea5bb
This commit is contained in:
parent
bb0fa3db80
commit
9806258ede
@ -93,6 +93,13 @@ For example,
|
|||||||
--instance-info boot_iso=http://path/to/boot.iso
|
--instance-info boot_iso=http://path/to/boot.iso
|
||||||
baremetal node deploy <NODE>
|
baremetal node deploy <NODE>
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
|
While this interface example utilizes a HTTP URL, as with all fields
|
||||||
|
referencing file artifacts in the ``instance_info`` field, a user is
|
||||||
|
able to request a file path URL, or an HTTPS URL, or as a Glance Image
|
||||||
|
Service object UUID.
|
||||||
|
|
||||||
.. warning::
|
.. warning::
|
||||||
This feature, when utilized with the ``ipxe`` ``boot_interface``,
|
This feature, when utilized with the ``ipxe`` ``boot_interface``,
|
||||||
will only allow a kernel and ramdisk to be booted from the
|
will only allow a kernel and ramdisk to be booted from the
|
||||||
|
Loading…
x
Reference in New Issue
Block a user