Re: [openstack-dev] [nova][api] Allow passing body for more API methods

2015-05-12 Thread Rosa, Andrea (HP Cloud Services)
-dev@lists.openstack.org Subject: Re: [openstack-dev] [nova][api] Allow passing body for more API methods On 05/11/2015 11:53 AM, Sean Dague wrote: Why is DELETE /volumes/ID?force=true not an option? Yes, this is what I would recommend as well. Best, -jay

Re: [openstack-dev] [nova][api] Allow passing body for more API methods

2015-05-11 Thread Kevin L. Mitchell
(Added [api] to subject to bring in the attention of the API team.) On Mon, 2015-05-11 at 14:48 +, Rosa, Andrea (HP Cloud Services) wrote: I noticed that in the nova API we allow to specify body just for the PUT and POST requests [0], for all the other methods, if a body is specified, it

Re: [openstack-dev] [nova][api] Allow passing body for more API methods

2015-05-11 Thread Monty Taylor
On 05/11/2015 02:05 PM, Dean Troyer wrote: On Mon, May 11, 2015 at 11:44 AM, Rosa, Andrea (HP Cloud Services) andrea.r...@hp.com wrote: Agreed. Violating the HTTP spec is something that should be avoided. Actually it is not violating the HTTP spec, from RFC: A payload within a DELETE

Re: [openstack-dev] [nova][api] Allow passing body for more API methods

2015-05-11 Thread Dean Troyer
On Mon, May 11, 2015 at 11:44 AM, Rosa, Andrea (HP Cloud Services) andrea.r...@hp.com wrote: Agreed. Violating the HTTP spec is something that should be avoided. Actually it is not violating the HTTP spec, from RFC: A payload within a DELETE request message has no defined semantics;

Re: [openstack-dev] [nova][api] Allow passing body for more API methods

2015-05-11 Thread Everett Toews
On May 11, 2015, at 1:05 PM, Dean Troyer dtro...@gmail.commailto:dtro...@gmail.com wrote: On Mon, May 11, 2015 at 11:44 AM, Rosa, Andrea (HP Cloud Services) andrea.r...@hp.commailto:andrea.r...@hp.com wrote: Agreed. Violating the HTTP spec is something that should be avoided. Actually it is

Re: [openstack-dev] [nova][api] Allow passing body for more API methods

2015-05-11 Thread Jay Pipes
On 05/11/2015 11:53 AM, Sean Dague wrote: Why is DELETE /volumes/ID?force=true not an option? Yes, this is what I would recommend as well. Best, -jay __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [nova][api] Allow passing body for more API methods

2015-05-11 Thread Ed Leafe
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 05/11/2015 01:49 PM, Everett Toews wrote: I’m agreed that this is not a good idea. I’d also invoke the principle of least astonishment here. Because it’s a de facto standard (so much so that some proxy in the middle may alter or reject such

Re: [openstack-dev] [nova][api] Allow passing body for more API methods

2015-05-11 Thread Sean Dague
On 05/11/2015 11:39 AM, Kevin L. Mitchell wrote: (Added [api] to subject to bring in the attention of the API team.) On Mon, 2015-05-11 at 14:48 +, Rosa, Andrea (HP Cloud Services) wrote: I noticed that in the nova API we allow to specify body just for the PUT and POST requests [0], for

Re: [openstack-dev] [nova][api] Allow passing body for more API methods

2015-05-11 Thread Duncan Thomas
On 11 May 2015 at 18:53, Sean Dague s...@dague.net wrote: I have worked with client frameworks which raise exceptions if you attempt to pass a body using the DELETE method, and would presumably also prohibit a body with GET and HEAD, so I'm -1 on this: we should actively discourage

Re: [openstack-dev] [nova][api] Allow passing body for more API methods

2015-05-11 Thread Rosa, Andrea (HP Cloud Services)
Why is DELETE /volumes/ID?force=true not an option? I believe it's valid for DELETE method to take parameters. Just not a body. I am not 100% sure that it would be considered RESTful as it could violates some REST principlebut I think we do not want to open this discussion. So yes it