openstack
/
ironic-specs
Code Issues Proposed changes

Follow-up to Stein priorities 

Change-Id: I8fe11d7a9c66a3fb3f75de04cbb2583f886922c4
This commit is contained in:
Julia Kreger 2018-10-01 11:13:50 -07:00
parent 1a5e28867a
commit d37539b26a
1 changed files with 43 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

62
priorities/stein-priorities.rst
View File

@ -33,21 +33,21 @@ Smaller Goals
+---------------------------------------+-------------------------------------+
| Priority | Primary Contacts |
+=======================================+=====================================+
| `Upgrade Checker`_ | TheJulia |
| `Upgrade Checker`_ | TheJulia, rloo |
+---------------------------------------+-------------------------------------+
| `Python3 First`_ | ? |
| `Python3 First`_ | derek, TheJulia |
+---------------------------------------+-------------------------------------+
| `iPXE/PXE interface split`_ | TheJulia |
| `iPXE/PXE interface split`_ | TheJulia, stendulker |
+---------------------------------------+-------------------------------------+
| `UEFI First`_ | ? |
| `UEFI First`_ | hshiina |
+---------------------------------------+-------------------------------------+
| `HTTPClient booting`_ | ?TheJulia? |
| `HTTPClient booting`_ | TheJulia |
+---------------------------------------+-------------------------------------+
| `Nova conductor_group awareness`_ | jroll, TheJulia |
+---------------------------------------+-------------------------------------+
| `Enhanced Checksum Support`_ | jroll, kaifeng |
+---------------------------------------+-------------------------------------+
| `DHCP-less/L3 virtual media boot`_ | shekar |
| `DHCP-less/L3 virtual media boot`_ | shekar, stendulker |
+---------------------------------------+-------------------------------------+
@ -78,9 +78,9 @@ Inter-Project Goals
-------------------
+---------------------------------------+-------------------------------------+
| `Deployment state callbacks to nova`_ | TheJulia, ?jroll? |
| `Deployment state callbacks to nova`_ | TheJulia, jroll |
+---------------------------------------+-------------------------------------+
| `Smartnic Support`_ | TheJulia, mkrai |
| `Smartnic Support`_ | TheJulia, mkrai, moshele |
+---------------------------------------+-------------------------------------+
@ -95,6 +95,7 @@ mean a new command called ``ironic-status upgrade check``. This command is
intended to return an error for things that would be fatal for an upgrade
such as new required configuration missing, or schema/data upgrades not
yet performed.
The story can be found at `story 2003657 <https://storyboard.openstack.org/#!/story/2003657>`_.
Python3 First
-------------
@ -105,6 +106,10 @@ are explicitly testing on Python3. We can't do this for every test at the
moment, but we should be able to change most and still ensure the bulk of
the code paths are covered by tests labeled with ``python2``.
We also desire for third party CI to begin to leverage Python3, with a goal
of approximately 50% of third party CI jobs until we stop supporting Python2.
The story can be found at `story 2003230 <https://storyboard.openstack.org/#!/story/2003230>`_.
iPXE/PXE interface split
------------------------
@ -119,7 +124,8 @@ AArch64 can be booted using iPXE, no pre-built binaries are available.
As such, we need to no longer make this global for the conductor, but
specific to the node, and splitting the interfaces apart begins to make
much more sense. The original specification can be found
`here <http://specs.openstack.org/openstack/ironic-specs/specs/not-implemented/ipxe-boot-interface.html>`.
`ipxe-boot interface <http://specs.openstack.org/openstack/ironic-specs/specs/approved/ipxe-boot-interface.html>`_.
The story can be found at `story 1628069 <https://storyboard.openstack.org/#!/story/1628069>`_.
UEFI First
----------
@ -131,6 +137,7 @@ To ensure our success, we need to improve our testing and prepare for the time
when UEFI is the only boot mode available for newer hardware. As a result,
this will become a multi-cycle focus to enable the default boot mode to be
changed to ``uefi`` in a future cycle.
The story can be found at `story 2003936 <https://storyboard.openstack.org/#!/story/2003936>`_.
HTTPClient Booting
------------------
@ -141,14 +148,16 @@ split and improved UEFI testing.
The nature of this work is to enable an explict HTTP booting scenario where
the booting node does not leverage PXE.
The story can be found at `story 2003934 <https://storyboard.openstack.org/#!/story/2003934>`_.
Nova conductor_group awareness
------------------------------
This work is exlusively in the ironic virt driver in the `openstack/nova`
This work is exclusively in the ironic virt driver in the `openstack/nova`
repository. This would enable us to define a ``conductor_group`` to which
the nova-compute process leverages for the view of baremetal nodes it is
responsible for.
The story can be found at `story 2003942 <https://storyboard.openstack.org/#!/story/2003942>`_.
Enhanced Checksum Support
-------------------------
@ -156,6 +165,7 @@ Enhanced Checksum Support
Ironic presently defaults to use of MD5 checksums for the ``image_checksum``
which is far from ideal. During the Rocky cycle, Glance has enhanced their
support for checksum storage, which means we should enhance ours as well.
The story can be found at `story 2003938 <https://storyboard.openstack.org/#!/story/2003938>`_.
DHCP-less/L3 virtual media boot
-------------------------------
@ -164,8 +174,9 @@ Some operators and vendors wish to enable ironic to manage deployments where
DHCP is not something that is leveraged or utilized in the deployment process.
In order to do this, we need to enable some additional capabilities in terms of
enabling information to be attached to a deployment ramdisk. The
specification can be found
`here <http://specs.openstack.org/openstack/ironic-specs/specs/not-implemented/L3-based-deployment.html>`.
specification can be found at the
`L3 based deployments specification <http://specs.openstack.org/openstack/ironic-specs/specs/approved/L3-based-deployment.html>`_.
The story can be found at `story 1749193 <https://storyboard.openstack.org/#!/story/1749193>`_.
Deploy Templates
----------------
@ -175,6 +186,8 @@ ironic from Nova describing the instance's expected state or behavior.
This will allow us to take actions and influence the deployment steps, and
as such is a continuation of the Deploy Steps work from the Rocky cycle.
The story can be found at `story 1722275 <https://storyboard.openstack.org/#!/story/1722275>`_.
Graphical Console
-----------------
@ -184,7 +197,8 @@ that support it. We reached agreement on the specification in the Rocky cycle
and have started to work through the patches to enable this. Our goal being
to have a framework and preferably at least one vendor driver to support
Graphical console connectivity. The specification can be found
`here <http://specs.openstack.org/openstack/ironic-specs/specs/not-implemented/vnc-graphical-console.html>`_.
`vnc graphical console specification <http://specs.openstack.org/openstack/ironic-specs/specs/approved/vnc-graphical-console.html>`_.
The story can be found at `story 1567629 <https://storyboard.openstack.org/#!/story/1567629>`_.
Federation Capabilities
-----------------------
@ -195,30 +209,34 @@ of ironic deployments can be useful and extremely powerful.
In order to better support this emerging use case, we want to try and agree
on a viable path forward that meets several different use cases and
requirements. The objective for this effort is an agreed upon specification.
The story can be found at `story 2001821 <https://storyboard.openstack.org/#!/story/2001821>`_.
Task execution improvements
---------------------------
We realize that our task execution and locking model is problematic, and while
it does scale in some ways, it does not scale in other ways. This work will
consist of worker execution improvments, an evaluation and possible
consist of worker execution improvements, an evaluation and possible
implementation of different worker thread execution models, and careful
improvement of locking.
The story can be found at `story 2003943 <https://storyboard.openstack.org/#!/story/2003943>`_.
No IPA to conductor communication
---------------------------------
Larger operators need much more strict security in their deployments,
where they wish to prevent all outbound network connectivity to the
control plane. Presently the design model requires nodes are able to
control plane. Presently the design model requires that nodes are able to
reach ironic's API in order to perform heartbeat and lookup operations.
The concept with this is to optionally enable the conductor to drive the
deployment by polling IPA using the already known IP address. That being
said, this is realistically going to require `Task execution improvements`_
to be complete to help ensure that operators are able to have performant
deployments. The specification can be found
`here <https://review.openstack.org/#/c/212206/>`.
deployments. The specification can be found at
`change 212206 <https://review.openstack.org/#/c/212206/>`_.
The story can be found at `story 1526486 <https://storyboard.openstack.org/#!/story/1526486>`_.
Getting steps
-------------
@ -231,8 +249,9 @@ providing the mechanisms to raise that visibility.
This may also involve state machine states to enable the agent to sit in a
holding pattern pending operator action.
The goal is ultimately to provide a CLI user to be able to understand the
available steps that can be utilized.
The goal is ultimately to provide a CLI for the user to be able to understand
the available steps that can be utilized.
The story can be found at `story 1715419 <https://storyboard.openstack.org/#!/story/1715419>`_.
Neutron Event Processing
------------------------
@ -241,6 +260,8 @@ Currently ironic has no way to determine when certain asynchronous events
actually finish in neutron, and with what result. Nova, on the contrary, uses
a special neutron driver, which filters out notifications and posts some of
them to a special nova API endpoint. We should do the same.
The story can be found at `story 1304673 <https://storyboard.openstack.org/#!/story/1304673>`_.
Conductor role splitting
------------------------
@ -252,6 +273,7 @@ can optionally break the conductor into many pieces, to enable edge
conductors, or edge local boot management. The goal here is to try and
obtain a matrix of distinct actions taken, which will hopefully further
guide us as time moves on.
The story can be found at `story 2003940 <https://storyboard.openstack.org/#!/story/2003940>`_.
Smartnic Support
----------------
@ -266,6 +288,7 @@ sufficient security is still present. The primary objective is to have
a joint specification written in advance of the Berlin summit to reach
consensus with the Neutron team as to the mechanics, information passing,
and setting storage.
The story can be found at `story 2003346 <https://storyboard.openstack.org/#!/story/2003346>`_.
Deployment state callbacks to nova
----------------------------------
@ -275,3 +298,4 @@ callbacks exist. Due to this, the virt driver polls the ironic API
endpoint repeatedly, which increases overall system load. In an ideal
world, ironic would utilize a mechanism to indicate deployment state
similar to how neutron informs nova that networking has been configured.
The story can be found at `story 2003939 <https://storyboard.openstack.org/#!/story/2003939>`_.