openstack/ironic-specs
Code Issues Proposed changes

Remove Pike priorities that cannot make it due to recent team changes

Browse Source 
Also add backup assignees for folks who are unlikely to be able to continue
working on ironic upstream, and remove folks who resigned from the team.

Lower priority of rescue, as it's in the process of changing assignees,
and thus is at risk.

Change-Id: Ia1d4f0fbe0dd645241faa23d636adc7a61bc81eb
This commit is contained in:
Dmitry Tantsur 2017-04-26 14:21:03 +02:00
parent 5ca10f6af1
commit 0e07adc653
1 changed files with 4 additions and 34 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

38
priorities/pike-priorities.rst
View File

@ -24,9 +24,9 @@ Essential Priorities
+---------------------------------------+-------------------------------------+
| `Rolling upgrades`_ | rloo, jlvillal |
+---------------------------------------+-------------------------------------+
| `Reference architecture guide`_ | jroll |
| `Reference architecture guide`_ | jroll, dtantsur |
+---------------------------------------+-------------------------------------+
| Python 3.5 compatibility | JayF, hurricanerix |
| Python 3.5 compatibility | Nisha |
+---------------------------------------+-------------------------------------+
| Deploying with Apache and WSGI in CI | vsaienk0 |
+---------------------------------------+-------------------------------------+
@ -34,9 +34,7 @@ Essential Priorities
+---------------------------------------+-------------------------------------+
| `Feature parity between two CLIs`_ | rloo, dtantsur |
+---------------------------------------+-------------------------------------+
| `OSC default API version change`_ | mariojv, dtantsur |
+---------------------------------------+-------------------------------------+
| `Rescue mode`_ | mariojv, JayF |
| `OSC default API version change`_ | dtantsur |
+---------------------------------------+-------------------------------------+
| Finish node tags | zhenguo, dtantsur |
+---------------------------------------+-------------------------------------+
@ -47,7 +45,7 @@ High Priorities
+---------------------------------------+-------------------------------------+
| Priority | Primary Contacts |
+=======================================+=====================================+
| `Specific fault support`_ | JayF, mariojv |
| `Rescue mode`_ | stendulker, aparnav |
+---------------------------------------+-------------------------------------+
| `Post-deploy VIF attach/detach`_ | sambetts, vsaienk0 |
+---------------------------------------+-------------------------------------+
@ -57,8 +55,6 @@ High Priorities
+---------------------------------------+-------------------------------------+
| `Neutron event processing`_ | vdrok, vsaienk0 |
+---------------------------------------+-------------------------------------+
| `Documentation reorganization`_ | JayF, TheJulia |
+---------------------------------------+-------------------------------------+
| `IPA REST API versioning`_ | sambetts |
+---------------------------------------+-------------------------------------+
@ -80,8 +76,6 @@ Optional Priorities
+---------------------------------------+-------------------------------------+
| `E-Tags in API`_ | galyna, vdrok |
+---------------------------------------+-------------------------------------+
| `IPA authentication`_ | jroll, joanna |
+---------------------------------------+-------------------------------------+
Details
~~~~~~~
@ -141,14 +135,6 @@ This is necessary for users that lose regular access to their machine (e.g.
lost passwords). The spec was merged in Newton, the code is partially done,
let's put some effort into making progress here in Pike.
Specific fault support
----------------------
Currently we communicate certain node errors via setting maintenance mode.
This is not obvious, and is a constant source of complaints from operators.
This work allows us to better communicate such failures, by providing a new API
for working with them.
Post-deploy VIF attach/detach
-----------------------------
@ -177,15 +163,6 @@ 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.
Documentation reorganization
----------------------------
For some time, our documentation has grown without strict definition of
structure, as well as difficulties getting documentation into the primary
OpenStack documentation. In the Pike cycle we plan on reaching a consensus of
direction for our documentation structure so we can better self-service as
OpenStack evolves to better support projects such as ironic.
IPA REST API versioning
-----------------------
@ -231,10 +208,3 @@ E-Tags in API
We should add E-Tag support to our API to avoid race conditions during
concurrent updates.
IPA authentication
------------------
Neither IPA API, nor the lookup/heartbeat endpoints it uses are currently
authenticated. While this issue is hard to solve completely in generic case,
we can at least consider reducing potential attack surface.