Re: [openstack-dev] [Glance][TC] Glance Functional API and Cross-project API Consistency

2014-06-24 Thread Jay Pipes
*To:* OpenStack Development Mailing List (not for usage questions) *Subject:* Re: [openstack-dev] [Glance][TC] Glance Functional API and Cross-project API Consistency On Wed, Jun 4, 2014 at 11:54 AM, Sean Dague s...@dague.net mailto:s...@dague.net wrote: On 05/30/2014 02:22 PM, Hemanth Makkapati wrote

Re: [openstack-dev] [Glance][TC] Glance Functional API and Cross-project API Consistency

2014-06-24 Thread Jay Pipes
On 06/11/2014 02:34 AM, Mark Washenberger wrote: I think the tasks stuff is something different, though. A task is a (potentially) long-running operation. So it would be possible for an action to result in the creation of a task. As the proposal stands today, the actions we've been looking at

Re: [openstack-dev] [Glance][TC] Glance Functional API and Cross-project API Consistency

2014-06-11 Thread Mark Washenberger
I think the tasks stuff is something different, though. A task is a (potentially) long-running operation. So it would be possible for an action to result in the creation of a task. As the proposal stands today, the actions we've been looking at are an alternative to the document-oriented PATCH

Re: [openstack-dev] [Glance][TC] Glance Functional API and Cross-project API Consistency

2014-06-10 Thread Jay Pipes
On Wed, Jun 4, 2014 at 11:54 AM, Sean Dague s...@dague.net wrote: On 05/30/2014 02:22 PM, Hemanth Makkapati wrote: Hello All, I'm writing to notify you of the approach the Glance community has decided to take for doing functional API. Also, I'm writing to solicit your feedback on this

Re: [openstack-dev] [Glance][TC] Glance Functional API and Cross-project API Consistency

2014-06-10 Thread Christopher Yeoh
On Wed, Jun 11, 2014 at 8:45 AM, Jay Pipes jaypi...@gmail.com wrote: On Wed, Jun 4, 2014 at 11:54 AM, Sean Dague s...@dague.net wrote: On 05/30/2014 02:22 PM, Hemanth Makkapati wrote: Hello All, I'm writing to notify you of the approach the Glance community has decided to take for doing

Re: [openstack-dev] [Glance][TC] Glance Functional API and Cross-project API Consistency

2014-06-10 Thread Brian Rosmaita
From: Jay Pipes [jaypi...@gmail.com] Sent: Tuesday, June 10, 2014 7:15 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Glance][TC] Glance Functional API and Cross-project API Consistency On Wed, Jun 4, 2014 at 11:54 AM

Re: [openstack-dev] [Glance][TC] Glance Functional API and Cross-project API Consistency

2014-06-06 Thread Mark McLoughlin
On Fri, 2014-05-30 at 18:22 +, Hemanth Makkapati wrote: Hello All, I'm writing to notify you of the approach the Glance community has decided to take for doing functional API. Also, I'm writing to solicit your feedback on this approach in the light of cross-project API consistency. At

Re: [openstack-dev] [Glance][TC] Glance Functional API and Cross-project API Consistency

2014-06-04 Thread Mark Washenberger
I will provide a little more context for the TC audience. I asked Hemanth to tag this message [TC] because at the Juno summit in the cross-project track there was discussion of cross-project api consistency [1]. The main outcome of that meeting was that TC should recommend API conventions via

[openstack-dev] [Glance][TC] Glance Functional API and Cross-project API Consistency

2014-05-30 Thread Hemanth Makkapati
Hello All, I'm writing to notify you of the approach the Glance community has decided to take for doing functional API. Also, I'm writing to solicit your feedback on this approach in the light of cross-project API consistency. At the Atlanta Summit, the Glance team has discussed introducing

Re: [openstack-dev] [Glance][TC] Glance Functional API and Cross-project API Consistency

2014-05-30 Thread Zhi Yan Liu
Hello Hemanth, Thanks for your summary, and raise it up in ML. All of them are sensible to me, there is only one concern from implementation perspective for me like to get folks notice. If we follow 'POST /images/{image_id}/actions/{action_type}' approach, I think we will hard to write common