Re: [openstack-dev] Version Discovery Standardization

2014-02-16 Thread Jamie Lennox
On Mon, 2014-02-17 at 16:09 +1000, Jamie Lennox wrote: > On Thu, 2014-02-13 at 08:37 -0500, Sean Dague wrote: > > On 02/13/2014 07:50 AM, Jamie Lennox wrote: > > > Hi all, > > > > > > I am one of i think a number of efforts trying to make clients be > > > interoperable between different versions

Re: [openstack-dev] Version Discovery Standardization

2014-02-16 Thread Jamie Lennox
On Thu, 2014-02-13 at 08:37 -0500, Sean Dague wrote: > On 02/13/2014 07:50 AM, Jamie Lennox wrote: > > Hi all, > > > > I am one of i think a number of efforts trying to make clients be > > interoperable between different versions of an API. > > > > What i would like to talk about specifically he

Re: [openstack-dev] Version Discovery Standardization

2014-02-16 Thread Jamie Lennox
On Thu, 2014-02-13 at 08:45 -0600, Dean Troyer wrote: > FWIW, an early proposal to address this, as well as capability > discovery, still lives > at https://etherpad.openstack.org/p/api-version-discovery-proposal. > I've lost track of where this went, and even which design summit this > is from, b

Re: [openstack-dev] Version Discovery Standardization

2014-02-16 Thread Jamie Lennox
On Thu, 2014-02-13 at 19:35 -0700, Christopher Yeoh wrote: > On Thu, 13 Feb 2014 21:10:01 -0500 > Sean Dague wrote: > > On 02/13/2014 08:28 PM, Christopher Yeoh wrote: > > > On Thu, 13 Feb 2014 15:54:23 -0500 > > > Sean Dague wrote: > > > > > > > So one question I have around a global version i

Re: [openstack-dev] Version Discovery Standardization

2014-02-13 Thread Christopher Yeoh
On Thu, 13 Feb 2014 21:10:01 -0500 Sean Dague wrote: > On 02/13/2014 08:28 PM, Christopher Yeoh wrote: > > On Thu, 13 Feb 2014 15:54:23 -0500 > > Sean Dague wrote: > > > > So one question I have around a global version is what happens when > > we have the following situation: > > > > - Extensi

Re: [openstack-dev] Version Discovery Standardization

2014-02-13 Thread Sean Dague
On 02/13/2014 08:28 PM, Christopher Yeoh wrote: > On Thu, 13 Feb 2014 15:54:23 -0500 > Sean Dague wrote: > >> On 02/13/2014 09:45 AM, Dean Troyer wrote: >>> FWIW, an early proposal to address this, as well as capability >>> discovery, still lives >>> at https://etherpad.openstack.org/p/api-versio

Re: [openstack-dev] Version Discovery Standardization

2014-02-13 Thread Christopher Yeoh
On Thu, 13 Feb 2014 15:54:23 -0500 Sean Dague wrote: > On 02/13/2014 09:45 AM, Dean Troyer wrote: > > FWIW, an early proposal to address this, as well as capability > > discovery, still lives > > at https://etherpad.openstack.org/p/api-version-discovery-proposal. > > I've lost track of where thi

Re: [openstack-dev] Version Discovery Standardization

2014-02-13 Thread Sean Dague
On 02/13/2014 09:45 AM, Dean Troyer wrote: > FWIW, an early proposal to address this, as well as capability > discovery, still lives > at https://etherpad.openstack.org/p/api-version-discovery-proposal. > I've lost track of where this went, and even which design summit this > is from, but I've bee

Re: [openstack-dev] Version Discovery Standardization

2014-02-13 Thread Dean Troyer
FWIW, an early proposal to address this, as well as capability discovery, still lives at https://etherpad.openstack.org/p/api-version-discovery-proposal. I've lost track of where this went, and even which design summit this is from, but I've been using it as a sanity check for the discovery bits i

Re: [openstack-dev] Version Discovery Standardization

2014-02-13 Thread Sean Dague
On 02/13/2014 07:50 AM, Jamie Lennox wrote: > Hi all, > > I am one of i think a number of efforts trying to make clients be > interoperable between different versions of an API. > > What i would like to talk about specifically here are the inconsistencies in > the version listing of the differe

[openstack-dev] Version Discovery Standardization

2014-02-13 Thread Jamie Lennox
Hi all, I am one of i think a number of efforts trying to make clients be interoperable between different versions of an API. What i would like to talk about specifically here are the inconsistencies in the version listing of the different servers when you query the root GET '/' and GET '/vX'