Matt Riedemann
d33a2b1cbb
The expected VIFHostUser object in this test is setting the vif_name field on the object which didn't actually exist until version 1.1 of that object which is being released in os-vif 1.4.0. The test passes against os-vif 1.3.0 and VIFHostUser 1.0 today because the obj_to_primitive() routine will not include anything that's not a field on the object, which is vif_name in this case. But when moving to os-vif 1.4.0, we're hitting a failure because the expected object has vif_name set but the actual object doesn't because though the vif_name field is defined, it's not actually used yet in the code, so it's not set in the primitive and our object comparison fails. Change-Id: I1c27726d583a41ab69d9eab23e8484e7e047942d Closes-Bug: #1656025
========================
Team and repository tags
========================
.. image:: http://governance.openstack.org/badges/nova.svg
:target: http://governance.openstack.org/reference/tags/index.html
.. Change things from this point on
OpenStack Nova
==============
OpenStack Nova provides a cloud computing fabric controller,
supporting a wide variety of compute technologies, including:
libvirt (KVM, Xen, LXC and more), Hyper-V, VMware, XenServer
and OpenStack Ironic.
OpenStack Nova is distributed under the terms of the Apache
License, Version 2.0. The full terms and conditions of this
license are detailed in the LICENSE file.
API
---
To learn how to use Nova's API, consult the documentation
available online at:
http://developer.openstack.org/api-guide/compute/
http://developer.openstack.org/api-ref/compute/
For more information on OpenStack APIs, SDKs and CLIs,
please see:
http://www.openstack.org/appdev/
http://developer.openstack.org/
Operators
---------
To learn how to deploy and configure OpenStack Nova, consult the
documentation available online at:
http://docs.openstack.org
For information about the different compute (hypervisor) drivers
supported by Nova, please read:
http://docs.openstack.org/developer/nova/feature_classification.html
In the unfortunate event that bugs are discovered, they should
be reported to the appropriate bug tracker. If you obtained
the software from a 3rd party operating system vendor, it is
often wise to use their own bug tracker for reporting problems.
In all other cases use the master OpenStack bug tracker,
available at:
http://bugs.launchpad.net/nova
Developers
----------
For information on how to contribute to Nova, please see the
contents of the CONTRIBUTING.rst.
Any new code must follow the development guidelines detailed
in the HACKING.rst file, and pass all unit tests.
Further developer focused documentation is available at:
http://docs.openstack.org/developer/nova/