openstack
/
ironic
Code Issues Proposed changes

Documentation for 'ramdisk' deploy with 'ilo-virtual-media' boot 

This patch updates documentation of 'ilo' hardware type for
'ramdisk' deploy with 'ilo-virtual-media' boot interface.

Change-Id: I1568f6f9a33c13a0d43898065095fe59c4f43305
This commit is contained in:
Shivanand Tendulker 2018-10-04 05:28:53 -04:00
parent c80e912b3a
commit e25dfdcc44
2 changed files with 12 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/admin/drivers/ilo.rst
View File

@ -221,7 +221,13 @@ Node configuration
- ``ilo_deploy_iso``: The glance UUID of the deploy ramdisk ISO image.
- ``instance info/ilo_boot_iso`` property to be either boot iso
Glance UUID or a HTTP(S) URL. This is optional property and is used when
``boot_option`` is set to ``netboot``.
``boot_option`` is set to ``netboot`` or ``ramdisk``.
.. note::
When ``boot_option`` is set to ``ramdisk``, the ironic node must be
configured to use ``ramdisk`` deploy interface. See :ref:`ramdisk-deploy`
for details.
- ``ilo_rescue_iso``: The glance UUID of the rescue ISO image. This is optional
property and is used when ``rescue`` interface is set to ``agent``.

13
doc/source/admin/interfaces/deploy.rst
View File

@ -124,15 +124,16 @@ it, see :doc:`Ansible deploy interface <../drivers/ansible>`.
../drivers/ansible
.. _ramdisk-deploy:
Ramdisk deploy
==============
The ramdisk interface is intended to provide a mechanism to "deploy" an
instance where the item to be deployed is in reality a ramdisk.
Most commonly this is peformed when an instance is booted via PXE or iPXE,
with the only local storage contents being those in memory. Initially this
is only supported by the ``pxe`` boot interface, but other boot interfaces
could support this funtionality in the future.
Most commonly this is peformed when an instance is booted via PXE, iPXE or
Virtual Media, with the only local storage contents being those in memory.
It is suported by ``pxe`` and ``ilo-virtual-media`` boot interfaces.
As with most non-default interfaces, it must be enabled and set for a node
to be utilized:
@ -171,7 +172,3 @@ or desired. As such, this interface does come with several caveats:
* As with all deployment interfaces, automatic cleaning of the node will
still occur with the contents of any local storage being wiped between
deployments.
.. warning::
As of the Rocky release of the BareMetal service, only the ``pxe`` boot
interface is supported.