[openstack-dev] [neutron] [API]Make API errors conform to the common error message without microversion
xiexs at cn.fujitsu.com
Mon Apr 11 13:32:49 UTC 2016
From: Xie, Xianshan [mailto:xiexs at cn.fujitsu.com]
Sent: Friday, April 08, 2016 4:24 PM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Cao, Shufeng/曹 树烽; dougwig at parkside.io
Subject: [openstack-dev] [neutron] [API]Make API errors conform to the common error message without microversion
We are attempting to make the neutron API conform to the common error message format recommended by API-WG . As this change will introduce a new error format into neutron which is different from existing format , we should think of some solutions to preserve the backward compat.
The easiest way to do that is microversion, just like the cinder does  although which is still in progress. But unfortunately, there are many projects in which the microversion haven't been landed yet, e.g. neutron, glance, keystone etc. Thus during the interim period we have to find other approaches to keep the backward compat.
According to the discussion, a new header would be a good idea to resolve this issue , we think.
curl -X DELETE "http://xxx:9696/v2.0/networks/xxx" -H "Neutron-Common-Error-Format: True"
But we haven't decided which header name will be used yet.
So how do you think which is the best appropriate one?
C: other (Could you please specify it? Thanks in advance)
Any comments would be appreciated.
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev