Re: [openstack-dev] [Nova] v3 API in Icehouse

2014-02-21 Thread Christopher Yeoh
On Fri, 21 Feb 2014 06:53:11 + Kenichi Oomichi oomi...@mxs.nes.nec.co.jp wrote: -Original Message- From: Christopher Yeoh [mailto:cbky...@gmail.com] Sent: Thursday, February 20, 2014 11:44 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Nova] v3 API

Re: [openstack-dev] [Nova] v3 API in Icehouse

2014-02-21 Thread Joe Gordon
On Thu, Feb 20, 2014 at 7:10 AM, Sean Dague s...@dague.net wrote: On 02/20/2014 09:55 AM, Christopher Yeoh wrote: On Thu, 20 Feb 2014 08:22:57 -0500 Sean Dague s...@dague.net wrote: We're also duplicating a lot of test and review energy in having 2 API stacks. Even before v3 has come out of

Re: [openstack-dev] [Nova] v3 API in Icehouse

2014-02-21 Thread Joe Gordon
On Wed, Feb 19, 2014 at 9:36 AM, Russell Bryant rbry...@redhat.com wrote: Greetings, The v3 API effort has been going for a few release cycles now. As we approach the Icehouse release, we are faced with the following question: Is it time to mark v3 stable? My opinion is that I think we

Re: [openstack-dev] [Nova] v3 API in Icehouse

2014-02-21 Thread Christopher Yeoh
On Fri, 21 Feb 2014 13:03:31 -0800 Joe Gordon joe.gord...@gmail.com wrote: 1) Discussions about the v2 and v3 APIs at the in-person Nova meetup last week made me come to the realization that v2 won't be going away *any* time soon. In some cases, users have long term API support

Re: [openstack-dev] [Nova] v3 API in Icehouse

2014-02-21 Thread Matt Riedemann
Subject: Re: [openstack-dev] [Nova] v3 API in Icehouse On Wed, 19 Feb 2014 12:36:46 -0500 Russell Bryant rbry...@redhat.com wrote: Greetings, The v3 API effort has been going for a few release cycles now. As we approach the Icehouse release, we are faced with the following question: Is it time

Re: [openstack-dev] [Nova] v3 API in Icehouse

2014-02-21 Thread Christopher Yeoh
] Sent: Thursday, February 20, 2014 11:44 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Nova] v3 API in Icehouse On Wed, 19 Feb 2014 12:36:46 -0500 Russell Bryant rbry...@redhat.com wrote: Greetings, The v3 API effort has been going for a few release cycles now

Re: [openstack-dev] [Nova] v3 API in Icehouse

2014-02-20 Thread Sean Dague
I agree that we shouldn't be rushing something that's not ready, but I guess it raises kind of a meta issue. When we started this journey this was because v2 has a ton of warts, is completely wonky on the code internals, which leads to plenty of bugs. v3 was both a surface clean up, but it was

Re: [openstack-dev] [Nova] v3 API in Icehouse

2014-02-20 Thread Alex Xu
On 2014年02月20日 10:44, Christopher Yeoh wrote: On Wed, 19 Feb 2014 12:36:46 -0500 Russell Bryant rbry...@redhat.com wrote: Greetings, The v3 API effort has been going for a few release cycles now. As we approach the Icehouse release, we are faced with the following question: Is it time to

Re: [openstack-dev] [Nova] v3 API in Icehouse

2014-02-20 Thread Matt Riedemann
On 2/19/2014 12:26 PM, Chris Behrens wrote: +1. I'd like to leave it experimental as well. I think the task work is important to the future of nova-api and I'd like to make sure we're not rushing anything. We're going to need to live with old API versions for a long time, so it's important

Re: [openstack-dev] [Nova] v3 API in Icehouse

2014-02-20 Thread Christopher Yeoh
On Thu, 20 Feb 2014 08:22:57 -0500 Sean Dague s...@dague.net wrote: We're also duplicating a lot of test and review energy in having 2 API stacks. Even before v3 has come out of experimental it's consumed a huge amount of review resource on both the Nova and Tempest sides to get it to it's

Re: [openstack-dev] [Nova] v3 API in Icehouse

2014-02-20 Thread Sean Dague
On 02/20/2014 09:55 AM, Christopher Yeoh wrote: On Thu, 20 Feb 2014 08:22:57 -0500 Sean Dague s...@dague.net wrote: We're also duplicating a lot of test and review energy in having 2 API stacks. Even before v3 has come out of experimental it's consumed a huge amount of review resource on

Re: [openstack-dev] [Nova] v3 API in Icehouse

2014-02-20 Thread John Garbutt
On 20 February 2014 14:55, Christopher Yeoh cbky...@gmail.com wrote: On Thu, 20 Feb 2014 08:22:57 -0500 Sean Dague s...@dague.net wrote: We're also duplicating a lot of test and review energy in having 2 API stacks. Even before v3 has come out of experimental it's consumed a huge amount of

Re: [openstack-dev] [Nova] v3 API in Icehouse

2014-02-20 Thread Christopher Yeoh
On Thu, 20 Feb 2014 15:24:22 + John Garbutt j...@johngarbutt.com wrote: Also micro and extension versioning is not the magic bullet which will get us out of trouble in the future. Especially with the core changes. Because even though versioning allows us to make changes, for similar

Re: [openstack-dev] [Nova] v3 API in Icehouse

2014-02-20 Thread Jay Pipes
On Thu, 2014-02-20 at 08:22 -0500, Sean Dague wrote: I agree that we shouldn't be rushing something that's not ready, but I guess it raises kind of a meta issue. When we started this journey this was because v2 has a ton of warts, is completely wonky on the code internals, which leads to

Re: [openstack-dev] [Nova] v3 API in Icehouse

2014-02-20 Thread Kenichi Oomichi
-Original Message- From: Christopher Yeoh [mailto:cbky...@gmail.com] Sent: Thursday, February 20, 2014 11:44 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Nova] v3 API in Icehouse On Wed, 19 Feb 2014 12:36:46 -0500 Russell Bryant rbry...@redhat.com wrote

Re: [openstack-dev] [Nova] v3 API in Icehouse

2014-02-19 Thread Chris Behrens
+1. I'd like to leave it experimental as well. I think the task work is important to the future of nova-api and I'd like to make sure we're not rushing anything. We're going to need to live with old API versions for a long time, so it's important that we get it right. I'm also not convinced

Re: [openstack-dev] [Nova] v3 API in Icehouse

2014-02-19 Thread Christopher Yeoh
On Wed, 19 Feb 2014 12:36:46 -0500 Russell Bryant rbry...@redhat.com wrote: Greetings, The v3 API effort has been going for a few release cycles now. As we approach the Icehouse release, we are faced with the following question: Is it time to mark v3 stable? My opinion is that I think