On 6/14/2016 6:19 PM, Chris Hoge wrote:
One would hope that micro-versions would be able to address this exact
issue for vendors by giving them a means to propose optional but
well-defined API response additions (not extensions) that are defined
upstream and usable by all vendors. If it’s not too off topic, can someone
from the Nova team explain how something like that would work (if it
would at all)?
-Chris
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
The 2.4 microversion is about as simple as it gets to adding more data
to a response:
http://docs.openstack.org/developer/nova/api_microversion_history.html#id3
If you're requesting microversion >=2.4 you get the 'reserved' flag back
when showing details on a fixed IP, else it's omitted from the response
(as in v2.0 and v2.1).
--
Thanks,
Matt Riedemann
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
