On 05/19/2014 11:49 PM, Christopher Yeoh wrote:
On Mon, May 19, 2014 at 11:58 PM, David Kranz dkr...@redhat.com
mailto:dkr...@redhat.com wrote:
Removing [nova]
On 05/19/2014 02:55 PM, Sean Dague wrote:
My suggestion is that we stop merging new Nova v3 tests from here
On Tue, May 20, 2014 at 8:58 PM, Sean Dague s...@dague.net wrote:
On 05/19/2014 11:49 PM, Christopher Yeoh wrote:
- if/else inlined in tests based on the microversion mode that is
being tested at the moment (perhaps least amount of code but cost is
readability)
- class inheritance
On 05/20/2014 03:19 PM, Christopher Yeoh wrote:
On Tue, May 20, 2014 at 8:58 PM, Sean Dague s...@dague.net
mailto:s...@dague.net wrote:
On 05/19/2014 11:49 PM, Christopher Yeoh wrote:
- if/else inlined in tests based on the microversion mode that is
being tested at the
I also agree that instead of removing the old test, we keep changing those
as microversion gets changed.
One suggestion (may be same as what Chris is thinking)-
-Tempest can keep the common test directory containing tests which are
going to be same as microversion bump up. Initially all test can
I agree to continue work on bp/ nova-api-test-inheritance. As its reduce
the duplication code and later will help to remove the V2 tests easily.
V2.1 tests can be written on same design of inheritance.
--
Thanks
Ghanshyam Mann
On Mon, May 19, 2014 at 9:32 PM, Kenichi Oomichi
Thanks for bringing this up.
We won't be testing v3 in Juno, but we'll need coverage for v2.1.
In my understanding will be a v2 compatible API - so including proxy to
glance cinder and neutron - but with micro-versions to bring in v3 features
such as CamelCase and Tasks.
So we should be able to
On 05/19/2014 01:24 PM, Frittoli, Andrea (HP Cloud) wrote:
Thanks for bringing this up.
We won't be testing v3 in Juno, but we'll need coverage for v2.1.
In my understanding will be a v2 compatible API - so including proxy to
glance cinder and neutron - but with micro-versions to bring in v3
My suggestion is that we stop merging new Nova v3 tests from here
forward. However I think until we see the fruits of the v2.1 effort I
don't want to start ripping stuff out.
The path to removing is going to be disable Nova v3 in devstack-gate,
when the Nova team decides it's right to do that.
Hi David,
-Original Message-
From: David Kranz [mailto:dkr...@redhat.com]
Sent: Monday, May 19, 2014 6:49 PM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [qa][nova] Status of v3 tests in tempest
It seems the nova team decided in Atlanta that v3 as currently
On Mon, May 19, 2014 at 9:12 PM, David Kranz dkr...@redhat.com wrote:
On 05/19/2014 01:24 PM, Frittoli, Andrea (HP Cloud) wrote:
Thanks for bringing this up.
We won't be testing v3 in Juno, but we'll need coverage for v2.1.
In my understanding will be a v2 compatible API - so including
Removing [nova]
On 05/19/2014 02:55 PM, Sean Dague wrote:
My suggestion is that we stop merging new Nova v3 tests from here
forward. However I think until we see the fruits of the v2.1 effort I
don't want to start ripping stuff out.
Fair enough but we need to revert, or at least stop taking
On Mon, May 19, 2014 at 11:58 PM, David Kranz dkr...@redhat.com wrote:
Removing [nova]
On 05/19/2014 02:55 PM, Sean Dague wrote:
My suggestion is that we stop merging new Nova v3 tests from here
forward. However I think until we see the fruits of the v2.1 effort I
don't want to start
12 matches
Mail list logo
