[openstack-dev] [api][qa][tc][nova][cinder] Testing of a microversioned world
mtreinish at kortar.org
Fri Mar 10 21:32:34 UTC 2017
On Fri, Mar 10, 2017 at 12:34:31PM -0800, Ken'ichi Ohmichi wrote:
> Hi John,
> Now Tempest is testing microversions only for Nova and contains some
> testing framework for re-using for another projects.
> On this framework, we can implement necessary microversions tests as
> we want and actually many microversions of Nova are not tested by
> We can see the tested microversion of Nova on
> Before implementing microversion testing for Cinder, we will implement
> JSON-Schema validation for API responses for Cinder.
> The validation will be helpful for testing base microversion of Cinder
> API and we will be able to implement the microversion tests based on
> This implementation is marked as 7th priority in this Pike cycle as
> In addition, now Cinder V3 API is not tested. So we are going to
> enable v3 tests with some restructure of Tempest in this cycle.
> The detail is described on the part of "Volume API" of
Umm, I don't know what you're basing that on, but there have been cinder v3
tests and cinder microversion support in Tempest since Newton. It was initially
added in this patch: https://review.openstack.org/#/c/300639/
> 2017-03-10 11:37 GMT-08:00 John Griffith <john.griffith8 at gmail.com>:
> > Hey Everyone,
> > So along the lines of an earlier thread that went out regarding testing of
> > deprecated API's and Tempest etc .
> > Now that micro-versions are *the API versioning scheme to rule them all* one
> > question I've not been able to find an answer for is what we're going to
> > promise here for support and testing. My understanding thus far is that the
> > "community" approach here is "nothing is ever deprecated, and everything is
> > supported forever".
> > That's sort of a tall order IMO, but ok. I've already had some questions
> > from folks about implementing an explicit Tempest test for every
> > micro-versioned implementation of an API call also. My response has been
> > "nahh, just always test latest available". This kinda means that we're not
> > testing/supporting the previous versions as promised though.
> > Anyway; I'm certain that between Nova and the API-WG this has come up and is
> > probably addressed, just wondering if somebody can point me to some
> > documentation or policies in this respect.
> > Thanks,
> > John
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: not available
More information about the OpenStack-dev