Move traits from "high" to "essential" priority
During the weekly Ironic meeting on 11-Dec-2017 it was decided that the traits work was an essential priority, since in Rocky release, nova is planning on replacing the ComputeCapabilitiesFilter with the traits processing in placement API. Added mgoddard as a contact as they have agreed to work on the code. Change-Id: Ibc5e333f7f29ba51c1d63f226ab7703b6c3bdc7f
This commit is contained in:
parent
ca5f9d4e84
commit
2074a39a10
|
@ -34,6 +34,9 @@ Essential Priorities
|
|||
+---------------------------------------+-------------------------------------+
|
||||
| `Reference architecture guide`_ | dtantsur, sambetts |
|
||||
+---------------------------------------+-------------------------------------+
|
||||
| `Traits support planning`_ | johnthetubaguy, TheJulia, dtantsur, |
|
||||
| | mgoddard |
|
||||
+---------------------------------------+-------------------------------------+
|
||||
|
||||
High Priorities
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
@ -57,8 +60,6 @@ High Priorities
|
|||
+---------------------------------------+-------------------------------------+
|
||||
| `Ansible deploy interface`_ | pas-ha, yuriyz |
|
||||
+---------------------------------------+-------------------------------------+
|
||||
| `Traits support planning`_ | johnthetubaguy, TheJulia, dtantsur |
|
||||
+---------------------------------------+-------------------------------------+
|
||||
|
||||
Details
|
||||
~~~~~~~
|
||||
|
|
Loading…
Reference in New Issue