On Tue, Oct 11, 2016 at 4:23 AM, Ken'ichi Ohmichi <ken1ohmi...@gmail.com> 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 API is used in the scenario like [2]. > So it is better to switch using v2 API on the default. > https://review.openstack.org/#/c/385050/ 2016-10-10 11:37 GMT-07:00 Matt Riedemann <mrie...@linux.vnet.ibm.com>: > > > > 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. > Yeah that could work. But I'd rather we completely remove the Cinder v1 part in Tempest, I am tired of the "if cinder_v1 is True ... elif cinder_v2 is True ...", not to mention the name vs display name thing. Anyway, that's not my call. I understand from Sean and Duncan reply that Cinder v1 is going to live on for a while, I'll see how we can react to this in Tempest. > > > > -- > > > > Thanks, > > > > Matt Riedemann > > > > > > > > ____________________________________________________________ > ______________ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: openstack-dev-requ...@lists.op > enstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > __________________________________________________________________________ > 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 > -- <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://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
