Re: [Openstack] Multiple Versions in Openstack API

2011-03-04 Thread Sandy Walsh
I agree that, while it's a pain, supporting old versions of the API is the best way to grow adoption. For many shops, simply supporting OpenStack API is a large engineering effort ... having to revisit it every version update might bust the camels back. Easy to see why Amazon goes back so far.

Re: [Openstack] Multiple Versions in Openstack API

2011-03-04 Thread Jay Pipes
On Thu, Mar 3, 2011 at 12:20 PM, Eric Day e...@oddments.org wrote: We should support old versions. The API layers should be a very thin layer over what the Nova internal API provides, so even if we have v1.0, v1.1, etc. subdirectories in the API and do full code copying, it should be a fairly

Re: [Openstack] Multiple Versions in Openstack API

2011-03-04 Thread Jay Pipes
On Fri, Mar 4, 2011 at 12:28 PM, Brian Lamar brian.la...@rackspace.com wrote: Unfortunately v1.0 - v1.1 is not a minor version increase (despite the names). Ah, ok. then if the v1.1 servers/ endpoint only *extends* the 1.0 version /servers endpoint and doesn't break it, then you could have:

Re: [Openstack] Multiple Versions in Openstack API

2011-03-04 Thread Brian Waldon
: Re: [Openstack] Multiple Versions in Openstack API On Fri, Mar 4, 2011 at 12:28 PM, Brian Lamar brian.la...@rackspace.com wrote: Unfortunately v1.0 - v1.1 is not a minor version increase (despite the names). Ah, ok. then if the v1.1 servers/ endpoint only *extends* the 1.0 version

Re: [Openstack] Multiple Versions in Openstack API

2011-03-04 Thread Jay Pipes
Lamar brian.la...@rackspace.com Cc: openstack@lists.launchpad.net openstack@lists.launchpad.net Subject: Re: [Openstack] Multiple Versions in Openstack API On Fri, Mar 4, 2011 at 12:28 PM, Brian Lamar brian.la...@rackspace.com wrote: Unfortunately v1.0 - v1.1 is not a minor version increase

Re: [Openstack] Multiple Versions in Openstack API

2011-03-04 Thread Brian Waldon
Message- From: Jay Pipes jaypi...@gmail.com Sent: Friday, March 4, 2011 2:08pm To: Brian Waldon brian.wal...@rackspace.com Cc: Brian Lamar brian.la...@rackspace.com, openstack@lists.launchpad.net openstack@lists.launchpad.net Subject: Re: [Openstack] Multiple Versions in Openstack API On Fri

Re: [Openstack] Multiple Versions in Openstack API

2011-03-04 Thread Jay Pipes
, openstack@lists.launchpad.net openstack@lists.launchpad.net Subject: Re: [Openstack] Multiple Versions in Openstack API On Fri, Mar 4, 2011 at 1:33 PM, Brian Waldon brian.wal...@rackspace.com wrote: As Brian is temporarily out of the office, I'll answer for him. Here are a few (major-version

Re: [Openstack] Multiple Versions in Openstack API

2011-03-03 Thread Thierry Carrez
Brian Waldon wrote: Currently, the Openstack API includes a Versions WSGI application. The intended purpose is to detail all versions of the API that are reachable by a client. Currently, it only supports v1.0. As we move towards the Cactus release, we need to add support for the new v1.1

Re: [Openstack] Multiple Versions in Openstack API

2011-03-03 Thread Trey Morris
maybe I'm missing something, but if you don't want to run a recent API why should you expect to be able to run it with a recent release of nova? I think trying to support older and new versions at the same time would clip our wings, or at the very least add some nastiness to the code. If someone

Re: [Openstack] Multiple Versions in Openstack API

2011-03-03 Thread Brian Waldon
To: openstack@lists.launchpad.net Subject: Re: [Openstack] Multiple Versions in Openstack API Brian Waldon wrote: Currently, the Openstack API includes a Versions WSGI application. The intended purpose is to detail all versions of the API that are reachable by a client. Currently, it only supports

Re: [Openstack] Multiple Versions in Openstack API

2011-03-03 Thread Thierry Carrez
Trey Morris wrote: maybe I'm missing something, but if you don't want to run a recent API why should you expect to be able to run it with a recent release of nova? I think trying to support older and new versions at the same time would clip our wings, or at the very least add some nastiness to

Re: [Openstack] Multiple Versions in Openstack API

2011-03-03 Thread Eric Day
We should support old versions. The API layers should be a very thin layer over what the Nova internal API provides, so even if we have v1.0, v1.1, etc. subdirectories in the API and do full code copying, it should be a fairly minimal mapping. We can of course share as much common code (like

Re: [Openstack] Multiple Versions in Openstack API

2011-03-03 Thread Ewan Mellor
: openstack@lists.launchpad.net Subject: Re: [Openstack] Multiple Versions in Openstack API We should support old versions. The API layers should be a very thin layer over what the Nova internal API provides, so even if we have v1.0, v1.1, etc. subdirectories in the API and do full code copying

Re: [Openstack] Multiple Versions in Openstack API

2011-03-03 Thread Eric Day
Message- From: openstack-bounces+ewan.mellor=citrix@lists.launchpad.net [mailto:openstack-bounces+ewan.mellor=citrix@lists.launchpad.net] On Behalf Of Eric Day Sent: 03 March 2011 17:21 To: Brian Waldon Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Multiple Versions

Re: [Openstack] Multiple Versions in Openstack API

2011-03-03 Thread Eric Day
Mellor ewan.mel...@eu.citrix.com Sent: Thursday, March 3, 2011 4:29pm To: Eric Day e...@oddments.org Cc: Brian Waldon brian.wal...@rackspace.com, openstack@lists.launchpad.net openstack@lists.launchpad.net Subject: RE: [Openstack] Multiple Versions in Openstack API That's fine