[openstack-dev] [Nova][Tempest] Tempest will deny extra properties on Nova v2/v2.1 API

GHANSHYAM MANN ghanshyammann at gmail.com
Tue Feb 24 11:28:49 UTC 2015

On Tue, Feb 24, 2015 at 6:48 PM, Ken'ichi Ohmichi <ken1ohmichi at gmail.com>

> Hi
> Nova team is developing Nova v2.1 API + microversions in this cycle,
> and the status of Nova v2.1 API has been changed to CURRENT from
> That said new API properties should be added via microversions, and
> v2/v2.1 API(*without* microversions) should return the same response
> without any new properties.
> Now Tempest allows extra properties of a Nova API response because we
> thought Tempest should not block Nova API development.
> However, I think Tempest needs to deny extra properties in
> non-microversions test cases because we need to block accidental
> changes of v2/v2.1 API and encourage to use microversions for API
> changes.
> https://review.openstack.org/#/c/156130/ is trying to do that, but I'd
> like to get opinions before that.
> If the above change is merged, we can not use Tempest on OpenStack
> environments which provide the original properties.

I think that will be nice to block additional properties.

Do you mean OpenStack environment with micro-versions enabled?
In those cases too tempest should run successfully as it requests on V2 or
V2.1 endpoint not on microversion.

Is it acceptable for the scope of Tempest?
> Any comments are welcome.
> Thanks
> Ken Ohmichi
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Thanks & Regards
Ghanshyam Mann
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150224/1a0a9949/attachment.html>

More information about the OpenStack-dev mailing list