Re: [openstack-dev] [api] [glance] conclusion needed on functional API

2015-02-24 Thread michael mccune
On 02/24/2015 03:09 AM, Flavio Percoco wrote: On 22/02/15 22:43 -0500, Jay Pipes wrote: On 02/18/2015 06:37 PM, Brian Rosmaita wrote: Thanks for your comment, Miguel. Your suggestion is indeed very close to the RESTful ideal. However, I have a question for the entire API-WG. Our (proposed) m

Re: [openstack-dev] [api] [glance] conclusion needed on functional API

2015-02-22 Thread Jay Pipes
On 02/18/2015 06:37 PM, Brian Rosmaita wrote: Thanks for your comment, Miguel. Your suggestion is indeed very close to the RESTful ideal. However, I have a question for the entire API-WG. Our (proposed) mission is "To improve the developer experience of API users by converging the OpenStack AP

Re: [openstack-dev] [api] [glance] conclusion needed on functional API

2015-02-18 Thread Brian Rosmaita
Thanks for your comment, Miguel. Your suggestion is indeed very close to the RESTful ideal. However, I have a question for the entire API-WG. Our (proposed) mission is "To improve the developer experience of API users by converging the OpenStack API to a consistent and pragmatic RESTful desig

Re: [openstack-dev] [api] [glance] conclusion needed on functional API

2015-02-18 Thread Miguel Grinberg
Out of all the proposals mentioned in this thread, I think Jay's (d) option is what is closer to the REST ideal: d) POST /images/{image_id}/tasks with payload: { "action": "deactivate|activate" } Even though I don't think this is the perfect solution, I can recognize that at least it tries to

Re: [openstack-dev] [api] [glance] conclusion needed on functional API

2015-02-18 Thread Brian Rosmaita
On 2/15/15, 2:35 PM, "Jay Pipes" wrote: >On 02/15/2015 01:13 PM, Brian Rosmaita wrote: >> On 2/15/15, 10:10 AM, "Jay Pipes" wrote: >> >>> On 02/15/2015 01:31 AM, Brian Rosmaita wrote: This is a follow-up to the discussion at the 12 February API-WG meeting [1] concerning "functional" API

Re: [openstack-dev] [api] [glance] conclusion needed on functional API

2015-02-15 Thread Jay Pipes
On 02/15/2015 01:13 PM, Brian Rosmaita wrote: On 2/15/15, 10:10 AM, "Jay Pipes" wrote: On 02/15/2015 01:31 AM, Brian Rosmaita wrote: This is a follow-up to the discussion at the 12 February API-WG meeting [1] concerning "functional" API in Glance [2]. We made some progress, but need to close

Re: [openstack-dev] [api] [glance] conclusion needed on functional API

2015-02-15 Thread Brian Rosmaita
On 2/15/15, 10:10 AM, "Jay Pipes" wrote: >On 02/15/2015 01:31 AM, Brian Rosmaita wrote: >> This is a follow-up to the discussion at the 12 February API-WG meeting >> [1] concerning "functional" API in Glance [2]. We made some progress, >>but >> need to close this off so the spec can be implement

Re: [openstack-dev] [api] [glance] conclusion needed on functional API

2015-02-15 Thread Jay Pipes
On 02/15/2015 01:31 AM, Brian Rosmaita wrote: This is a follow-up to the discussion at the 12 February API-WG meeting [1] concerning "functional" API in Glance [2]. We made some progress, but need to close this off so the spec can be implemented in Kilo. I believe this is where we left off: 1.

Re: [openstack-dev] [api] [glance] conclusion needed on functional API

2015-02-15 Thread Flavio Percoco
On 15/02/15 06:31 +, Brian Rosmaita wrote: This is a follow-up to the discussion at the 12 February API-WG meeting [1] concerning "functional" API in Glance [2]. We made some progress, but need to close this off so the spec can be implemented in Kilo. I believe this is where we left off: 1.

[openstack-dev] [api] [glance] conclusion needed on functional API

2015-02-14 Thread Brian Rosmaita
This is a follow-up to the discussion at the 12 February API-WG meeting [1] concerning "functional" API in Glance [2]. We made some progress, but need to close this off so the spec can be implemented in Kilo. I believe this is where we left off: 1. The general consensus was that POST is the corre