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 API versions indefinitely,
keeping them around isn't that much of a burden.
On 10 October 2016 at 15:32, Jordan Pittier <jordan.pitt...@scality.com
<mailto:jordan.pitt...@scality.com>> wrote:
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 deprecated (it has been for what, 2
years ?) Is the removal scheduled ? I don't see/feel a lot of
efforts toward that removal but I may be missing something. Any way,
that's not really my business but it's not really fair to all the
projects that run the "common jobs" that Cinder "slows" everyone down.
What do you think ?
[0]
:
https://github.com/JordanP/openstack-snippets/blob/master/tempest-timing/tempest_timing.py
<https://github.com/JordanP/openstack-snippets/blob/master/tempest-timing/tempest_timing.py>
<https://www.scality.com/backup/?utm_source=signatures&utm_medium=email&utm_campaign=backup2016>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
--
--
Duncan Thomas
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
So make it conditional in Tempest via a config option, disable volume v1
tests by default for the integrated gate, and then add a new job that
runs only on cinder changes (and maybe only in the experimental queue)
that enables volume v1 tests. You could run it on cinder in the
check/gate and skip the job from running unless something in the v1 API
path is changed, there are examples of that in project-config.
Nova used to have the v2 API in tree and this was kind of the eventual
path to phasing out the Tempest testing on that code and got us to the
point of removing the v2 *code*. The compute v2 API itself is still
honored via the v2.1 base microversion.
--
Thanks,
Matt Riedemann
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
