Open Stack

>From the etherpad [0]:

* We might want to tighten up what the RP traits API allows as per https://pasteboard.co/I3iqqNm.jpg
* although maybe this is better covered in a nova session?
     * If the mechanism is changing how nova-compute reports and
       manipulates traits, then yeah, nova. But if for some reason
       there is a need to change the actual API [1], placement; but I
       would hope that all avenues not involving changing the API
       were first disposed as either not possible, or really really
       terrible.

This came up as part of the work on compute capabilities as traits [2]
and questions about who owns what traits and how to manage them so
that unexpected trait clobbering or trait addition happens.

This is (hopefully) mostly a thing on the nova-compute side of the
equation (when managing inventory), so hopefully someone with more
insight into that situation can drive this thread. What needs to
happen here?


[0] https://etherpad.openstack.org/p/placement-ptg-train

[1] There are degrees of change in the API. Adding a query parameter
is much less of a big deal than adding or changing an attribute in a
request or response body. Adding another method to a URI, while a
big deal in some cases, is much less of a big deal than adding an
entirely new URI.

[2] https://review.openstack.org/#/c/538498/k

-- 
Chris Dent                       ٩◔̯◔۶           https://anticdent.org/
freenode: cdent                                         tw: @anticdent