Move the inspector boot management spec to backlog

When implementing this spec two critical problems were found:
* PXEBoot.validate requires instance image parameters, so we cannot
  use it during inspection.
* PXEBoot.prepare_ramdisk tries to configure DHCP/PXE environment,
  which clashes with inspector's one and requires VIFs to be present.

This change also marks the inspector part as done in 8.0.0 and
puts the unsolved problems into the text for anyone who will want
to revive the spec.

Finally, the RFE link is changed to storyboard.

Change-Id: I5a2920b1416889aaaed725e4cb669c505c2ed0bf
This commit is contained in:
Dmitry Tantsur 2018-08-23 10:53:52 +02:00
parent 389c06994a
commit 53984da2e4
2 changed files with 17 additions and 2 deletions

View File

@ -8,7 +8,7 @@
Boot management for in-band inspection
======================================
https://bugs.launchpad.net/ironic/+bug/1528920
https://storyboard.openstack.org/#!/story/1528920
This is a cross-project (**ironic** and **ironic-inspector**) spec for making
the **ironic-inspector** inspection interface implementation optionally manage
@ -28,6 +28,8 @@ will manage the boot for each inspection.
Inspector changes
-----------------
.. note:: This proposal was implemented in **ironic-inspector** 8.0.0.
#. Modify **ironic-inspector** inspection API to accept ``manage_boot``
parameter (boolean, defaults to ``True``). If it's set to ``False``,
**inspector** won't set boot device or power state
@ -73,6 +75,20 @@ Ironic changes
``boot.prepare_ramdisk`` will be used for this. We will assume
the IPA ramdisk, as it's the only ramdisk supported right now.
Unsolved problems
-----------------
This specification has the following problems that must be solved in its final
version:
#. ``PXEboot.validate`` will not pass without instance image parameters.
#. ``PXEBoot.prepare_ramdisk`` tries to configure DHCP, which requires VIFs and
conflicts with DHCP of **ironic-inspector**.
#. It is not specified how to pass kernel parameters when **ironic-inspector**
DHCP is not used (e.g. for virtual media).
#. The change will be in effect immediately for many deployments without a way
to opt-out.
Alternatives
------------

View File

@ -1 +0,0 @@
../approved/inspector-boot-management.rst