Re: [Openstack] [keystone] v3 API draft (update and questions to the community)

2012-06-14 Thread Nguyen, Liem Manh
: [Openstack] [keystone] v3 API draft (update and questions to the community) On 13/06/2012, at 1:24 PM, Gabriel Hurley wrote: Totally agree with all of Jay's points, and I also couldn't agree more with Mark on the importance of being crystal clear, and not operating on just a common understanding

Re: [Openstack] [keystone] v3 API draft (update and questions to the community)

2012-06-13 Thread Christopher B Ferris
bounces+chrisfer=us.ibm@lists.launchpad.netDate: 06/12/2012 11:28PMSubject: Re: [Openstack] [keystone] v3 API draft (update and questions to the community)Totally agree with all of Jay's points, and I also couldn't agree more with Mark on the importance of being crystal clear, and not operating o

Re: [Openstack] [keystone] v3 API draft (update and questions to the community)

2012-06-13 Thread Gabriel Hurley
-Original Message- From: Mark Nottingham [mailto:m...@mnot.net] Sent: Tuesday, June 12, 2012 8:43 PM To: Gabriel Hurley Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] [keystone] v3 API draft (update and questions to the community) On 13/06/2012, at 1:24 PM, Gabriel Hurley

Re: [Openstack] [keystone] v3 API draft (update and questions to the community)

2012-06-12 Thread Gabriel Hurley
Of Mark Nottingham Sent: Monday, June 11, 2012 10:27 PM To: Joseph Heck Cc: openstack@lists.launchpad.net (openstack@lists.launchpad.net) Subject: Re: [Openstack] [keystone] v3 API draft (update and questions to the community) On 11/06/2012, at 6:58 AM, Joseph Heck wrote: First - what's

Re: [Openstack] [keystone] v3 API draft (update and questions to the community)

2012-06-12 Thread Mark Nottingham
: Monday, June 11, 2012 10:27 PM To: Joseph Heck Cc: openstack@lists.launchpad.net (openstack@lists.launchpad.net) Subject: Re: [Openstack] [keystone] v3 API draft (update and questions to the community) On 11/06/2012, at 6:58 AM, Joseph Heck wrote: First - what's the current thought

Re: [Openstack] [keystone] v3 API draft (update and questions to the community)

2012-06-12 Thread Joseph Heck
P.S. the X-Subject-Token stuff is breaking HTTP; you need to either put the token (or a facsimile for it) in the URL, or put Vary: Subject-Token in EVERY response those resources generate. The former is preferred; this is over TLS, right? Sorry I didn't see that earlier. P.P.S If it's

Re: [Openstack] [keystone] v3 API draft (update and questions to the community)

2012-06-12 Thread Adam Young
, 2012 10:27 PM To: Joseph Heck Cc: openstack@lists.launchpad.net (openstack@lists.launchpad.net) Subject: Re: [Openstack] [keystone] v3 API draft (update and questions to the community) On 11/06/2012, at 6:58 AM, Joseph Heck wrote: First - what's the current thought of support for PATCH vs PUT

Re: [Openstack] [keystone] v3 API draft (update and questions to the community)

2012-06-12 Thread Jay Pipes
On 06/12/2012 04:24 AM, Gabriel Hurley wrote: Mark, Apparently you must have missed my lightning talk at the Essex summit... ;-) (http://gabrielhurley.github.com/slides/openstack/apis_like_orms/index.html) Filtering, pagination, and many other API features are *critical* for a rich dashboard

Re: [Openstack] [keystone] v3 API draft (update and questions to the community)

2012-06-12 Thread Jay Pipes
On 06/12/2012 12:21 PM, Adam Young wrote: On 06/12/2012 04:24 AM, Gabriel Hurley wrote: That said, we have also considered the case you propose where you effectively request everything and handle it on the client-side... however, I see that as a tremendously lazy solution. On the

Re: [Openstack] [keystone] v3 API draft (update and questions to the community)

2012-06-12 Thread Dolph Mathews
The X-Subject-Token solution is definitely not valid HTTP, in that it implies that two otherwise identical requests for GET /tokens would return two completely different results (hence the need for a Vary header, as we include for X-Auth-Token). I have a slightly more proper (and complicated)

Re: [Openstack] [keystone] v3 API draft (update and questions to the community)

2012-06-12 Thread Michael Barton
On Tue, Jun 12, 2012 at 3:24 AM, Gabriel Hurley gabriel.hur...@nebula.com wrote: To speak on the specific feature of pagination, the problem of 'corruption' by simultaneous writers is no excuse for not implementing it. You think Google, Facebook, Flickr, etc. etc. etc. don't have this

Re: [Openstack] [keystone] v3 API draft (update and questions to the community)

2012-06-12 Thread Mark Nottingham
On 13/06/2012, at 3:31 AM, Jay Pipes wrote: This isn't necessarily true. Nova's compute layer goes through a number of steps to ensure a semi-transactional nature to certain operations like resizing. Certain times a query needs to indicate that it intends to make a reservation of

Re: [Openstack] [keystone] v3 API draft (update and questions to the community)

2012-06-12 Thread Gabriel Hurley
@lists.launchpad.net] On Behalf Of Mark Nottingham Sent: Tuesday, June 12, 2012 7:20 PM To: Jay Pipes Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] [keystone] v3 API draft (update and questions to the community) On 13/06/2012, at 3:31 AM, Jay Pipes wrote: This isn't

Re: [Openstack] [keystone] v3 API draft (update and questions to the community)

2012-06-12 Thread Mark Nottingham
@lists.launchpad.net [mailto:openstack- bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of Mark Nottingham Sent: Tuesday, June 12, 2012 7:20 PM To: Jay Pipes Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] [keystone] v3 API draft (update and questions to the community) On 13

[Openstack] [keystone] v3 API draft (update and questions to the community)

2012-06-10 Thread Joseph Heck
First a thank you to everyone who's swung by to read (and some comment) on the V3 draft at https://docs.google.com/document/d/1s9C4EMxIZ55kZr62CKEC9ip7He_Q4_g1KRfSk9hY-Sg/edit?pli=1. It's been immensely useful. To clear up a bit of confusion I caused (sorry Jay!) - there were *no* example