[openstack-dev] [Ironic] How to deal with microversions in 3rdparty tools
yuikotakada0313 at gmail.com
Wed Apr 8 04:48:32 UTC 2015
In Tempest, there is similar discussion.
> Now Nova and Ironic have implemented API microversions in Kilo.
> Nova's microversions are v2.1 - v2.3.
> Ironic's microversions are v1.1 - v1.6.
> Now Tempest is testing the lowest microversion on the gate, and
> Ironic's microversions test patch is on the gerrit.
> Before merging the patch, I'd like to propose consistent test way for
> microversions of Nova and Ironic.
> My suggestion is the test target microversions are:
> * the lowest microversion
> * the biggest microversion, but don't use the keyword "latest" on a
> header and these microversions tests are operated on different gate
> The lowest microversion is already tested on check-tempest-dsvm-full
> or something, so this proposes just to add the biggest microversion
> job like check-tempest-dsvm-full-big-microversion.
Same as Tempest, I propose to use (in other word, "test") both;
* The lowest microversion
* The biggest microversion without the keyword "latest"
How do you think?
2015-04-07 22:02 GMT+09:00 Dmitry Tantsur <dtantsur at redhat.com>:
> Hi again, hope you're not tired of this topic :D
> I'm seeking for advice on what to do with microversions in discoverd.
> Basically I have the following options:
> 1. Do nothing. Get whatever behavior I can get from installed Ironic and
> Ironic client. Though unlikely, may get broken by future changes.
> 2. Demand version = 1.6. Looks like it keeps compatibility with old
> clients and servers, not sure what downsides are here.
> What are we going to recommend now as upstream?
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev