On Tue, Oct 11, 2016 at 4:23 AM, Ken'ichi Ohmichi
wrote:
> Thanks for pointing this up, Jordan
>
> Before removing volume v1 API tests, it is nice to make the v2 API the
> default of Tempest scenario tests.
> Now the v1 and v2 is set as True on the default in the
> configuration[1], and the v1 AP
Thanks for pointing this up, Jordan
Before removing volume v1 API tests, it is nice to make the v2 API the
default of Tempest scenario tests.
Now the v1 and v2 is set as True on the default in the
configuration[1], and the v1 API is used in the scenario like [2].
So it is better to switch using v2
On 10/10/2016 7:47 AM, Duncan Thomas wrote:
If we can get them running on cinder patches via a different job, then
removing them from the common job afterwards seems reasonable.
There's no strong will to remove them, several libraries still use them,
and given we're now supporting /all/ other AP
On Mon, Oct 10, 2016 at 03:47:39PM +0300, Duncan Thomas wrote:
> If we can get them running on cinder patches via a different job, then
> removing them from the common job afterwards seems reasonable.
>
> There's no strong will to remove them, several libraries still use them,
> and given we're no
If we can get them running on cinder patches via a different job, then
removing them from the common job afterwards seems reasonable.
There's no strong will to remove them, several libraries still use them,
and given we're now supporting /all/ other API versions indefinitely,
keeping them around i
Hi,
I'd like to reduce the duration of a full Tempest run and I noticed that
Cinder tests take a good amount of time (cumulative time 2149sec vs 2256sec
for Nova, source code [0])
So I'd like to not run the Cinder v1 tests anymore, at least on the master
branches.
I remember that Cinder v1 is de
