Re: [openstack-dev] [neutron] [API]Make API errors conform to the common error message without microversion

As a note, there will be a design session around the API refactor efforts going on. Microversioning will be a topic. On Tue, 2016-04-12 at 14:59 +0200, Ihar Hrachyshka wrote: > Xianshan wrote: > > > Hi, Duncan & michael, > > Thanks a lot for your replies. > > > >

Re: [openstack-dev] [neutron] [API]Make API errors conform to the common error message without microversion

Xianshan wrote: Hi, Duncan & michael, Thanks a lot for your replies. Definitely I agree with you that the microversion is the best approach to solve the backwards compat, and the neutron is also going to adopt it [1]. But it will take a long time to totally introduce

Re: [openstack-dev] [neutron] [API]Make API errors conform to the common error message without microversion

: Re: [openstack-dev] [neutron] [API]Make API errors conform to the common error message without microversion please forgive my lack of direct knowledge about the neutron process and how this fits in. i'm just commenting from the perspective of someone looking at this from the api-wg. On 04/11/

Re: [openstack-dev] [neutron] [API]Make API errors conform to the common error message without microversion

On 04/11/2016 11:11 AM, michael mccune wrote: > please forgive my lack of direct knowledge about the neutron process and > how this fits in. i'm just commenting from the perspective of someone > looking at this from the api-wg. > > On 04/11/2016 09:52 AM, Duncan Thomas wrote: >> So by adding the

Re: [openstack-dev] [neutron] [API]Make API errors conform to the common error message without microversion

please forgive my lack of direct knowledge about the neutron process and how this fits in. i'm just commenting from the perspective of someone looking at this from the api-wg. On 04/11/2016 09:52 AM, Duncan Thomas wrote: So by adding the handling of a header to change the behaviour of the

Re: [openstack-dev] [neutron] [API]Make API errors conform to the common error message without microversion

On 04/08/2016 03:23 AM, Xie, Xianshan wrote: > According to the discussion, a new header would be a good idea to resolve > this issue [4], we think. > For instance: > curl -X DELETE "http://xxx:9696/v2.0/networks/xxx; -H > "Neutron-Common-Error-Format: True" > > But we haven't decided which

Re: [openstack-dev] [neutron] [API]Make API errors conform to the common error message without microversion

So by adding the handling of a header to change the behaviour of the API, you're basically implementing a subset of microversions, with a non-standard header (See the API WG spec on non-proliferation of headers). You'll find it takes much of the work that implementing microversions does, and

Re: [openstack-dev] [neutron] [API]Make API errors conform to the common error message without microversion

Ping. -Original Message- From: Xie, Xianshan [mailto:xi...@cn.fujitsu.com] Sent: Friday, April 08, 2016 4:24 PM To: OpenStack Development Mailing List (not for usage questions) Cc: Cao, Shufeng/曹 树烽; doug...@parkside.io Subject: [openstack-dev] [neutron] [API]Make API errors conform

[openstack-dev] [neutron] [API]Make API errors conform to the common error message without microversion

Hi, all, We are attempting to make the neutron API conform to the common error message format recommended by API-WG [1]. As this change will introduce a new error format into neutron which is different from existing format [2], we should think of some solutions to preserve the backward