[sahara][qa][api-sig]Support for Sahara APIv2 in tempest tests, unversioned endpoints
jeremyfreudberg at gmail.com
Wed Jan 2 22:29:27 UTC 2019
I poked around in Tempest and saw these code bits:
Here's a patch which takes advantage of those bits to append the
version to the unversioned base URL:
Hope it works without regression (I'm a bit worried since Tempest does
its own URL mangling rather than nicely use keystoneauth...)
On Wed, Jan 2, 2019 at 5:19 AM Luigi Toscano <ltoscano at redhat.com> wrote:
> Hi all,
> I'm working on adding support for APIv2 to the Sahara tempest plugin.
> If I get it correctly, there are two main steps
> 1) Make sure that that tempest client works with APIv2 (and don't regress with
> This mainly mean implementing the tempest client for Sahara APIv2, which
> should not be too complicated.
> On the other hand, we hit an issue with the v1.1 client in an APIv2
> A change associated with API v2 is usage of an unversioned endpoint for the
> deployment (see https://review.openstack.org/#/c/622330/ , without the /v1,1/$
> (tenant_id) suffix) which should magically work with both API variants, but it
> seems that the current tempest client fails in this case:
> Does anyone know if this is an issue with the code of the tempest tests (which
> should maybe have some logic to build the expected endpoint when it's
> unversioned, like saharaclient does) or somewhere else?
> 2) fix the tests to support APIv2.
> Should I duplicate the tests for APIv1.1 and APIv2? Other projects which
> supports different APIs seems to do this.
> But can I freely move the existing tests under a subdirectory
> (sahara_tempest_plugins/tests/api/ -> sahara_tempest_plugins/tests/api/v1/),
> or are there any compatibility concerns? Are the test ID enough to ensure that
> everything works as before?
> And what about CLI tests currently under sahara_tempest_plugin/tests/cli/ ?
> They supports both API versions through a configuration flag. Should they be
> duplicated as well?
> (and happy new year if you have a new one in your calendar!)
More information about the openstack-discuss