There is difference in VIF list response for v2 and v2.1. 'net_id' attribute is not present in v2.1 VIF list response and it was added as new microversion - Ic8b26df8d7e69bd71d23dfbc983fa3449c16fa7d For v21 compatible mode we should have that attribute in response to make v21 comp mode behaves same as v2. Also VIF Extension "OS-EXT-VIF-NET" was removed from v2.1 ext list in - Ic99ac1179d02d907422911fe1369b64479fd5f33 As we need to add 'OS-EXT-VIF-NET:net_id' in VIF API response to make that same as v2 one. So ext list should have "OS-EXT-VIF-NET" extension also to avoid any confusion for user whether this extension is present for v21 comp mode or not. This commit adds 'OS-EXT-VIF-NET:net_id' attribute in VIF list response for v21 compatible mode. Also adds VIF extension in ext list for v21 comp mode. NOTE-There is no change in v2.1 API. Closes-Bug #1496664 Change-Id: I4df76fbf85fbb1e79528a1690692b12a65f07835
OpenStack Nova README
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of virtualization technologies, including KVM, Xen, LXC, VMware, and more. In addition to its native API, it includes compatibility with the commonly encountered Amazon EC2 and S3 APIs.
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.
Nova primarily consists of a set of Python daemons, though it requires and integrates with a number of native system components for databases, messaging and virtualization capabilities.
To keep updated with new developments in the OpenStack project follow @openstack on Twitter.
To learn how to deploy OpenStack Nova, consult the documentation available online at:
For information about the different compute (hypervisor) drivers supported by Nova, read this page on the wiki:
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:
Developers wishing to work on the OpenStack Nova project should always base their work on the latest Nova code, available from the master GIT repository at:
Developers should also join the discussion on the mailing list, at:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
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:
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst file.
-- End of broadcast