Re: [openstack-dev] [api][neutron] question on putting an existing tag

I'm considering the tag implementation in neutron. Although I proposed server returns 409 in tag existing case, on the basis of the above discussion, server should return the same response code. I will change current implementation to returning 201. Thanks, Hirofumi On 2016/02/27 2:24,

Re: [openstack-dev] [api][neutron] question on putting an existing tag

2016-02-27 1:02 GMT+09:00 Sean Dague : > On 02/26/2016 10:52 AM, Chris Dent wrote: >> On Fri, 26 Feb 2016, Jay Pipes wrote: >>> On 02/26/2016 09:02 AM, Akihiro Motoki wrote: We can create a tag by PUT'ing an individual tag: What status code should be returned if a

Re: [openstack-dev] [api][neutron] question on putting an existing tag

On 02/26/2016 10:52 AM, Chris Dent wrote: > On Fri, 26 Feb 2016, Jay Pipes wrote: >> On 02/26/2016 09:02 AM, Akihiro Motoki wrote: >>> We can create a tag by PUT'ing an individual tag: >>> What status code should be returned if a requested tag already exists? >>> >>> PUT

Re: [openstack-dev] [api][neutron] question on putting an existing tag

Thanks Jay. I will send an update to api-wg repo as well. 2016-02-27 0:36 GMT+09:00 Jay Pipes : > On 02/26/2016 09:02 AM, Akihiro Motoki wrote: >> >> Hi API-WG, >> >> Neutron is implementing tag support for network resource [0]. >> The implementation follows 'Tags' guideline

Re: [openstack-dev] [api][neutron] question on putting an existing tag

Hi, Jay, an explanation would be appreciated as it seems 409 doesn't match HTTP RFC[1] [1] https://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html Cédric/ZZelle On Fri, Feb 26, 2016 at 4:36 PM, Jay Pipes wrote: > On 02/26/2016 09:02 AM, Akihiro Motoki wrote: > >> Hi

Re: [openstack-dev] [api][neutron] question on putting an existing tag

On Fri, 26 Feb 2016, Jay Pipes wrote: On 02/26/2016 09:02 AM, Akihiro Motoki wrote: We can create a tag by PUT'ing an individual tag: What status code should be returned if a requested tag already exists? PUT /servers/1234567890/tags/qux The guideline defines 201 (+ Location header) on

Re: [openstack-dev] [api][neutron] question on putting an existing tag

On 02/26/2016 09:02 AM, Akihiro Motoki wrote: Hi API-WG, Neutron is implementing tag support for network resource [0]. The implementation follows 'Tags' guideline defined by API-WG [1]. I have a questions on the guideline. We can create a tag by PUT'ing an individual tag: What status

[openstack-dev] [api][neutron] question on putting an existing tag

Hi API-WG, Neutron is implementing tag support for network resource [0]. The implementation follows 'Tags' guideline defined by API-WG [1]. I have a questions on the guideline. We can create a tag by PUT'ing an individual tag: What status code should be returned if a requested tag already