d0d546ce8e
When using neutron polling mode, booting a VM will timeout because cannot receive network-vif-plugged event. After investigation we found we set vif['id'](i.e. neutron port uuid from neutron's perspective of view) to two different OVS ports. One is the Xenserver VIF, the other is tap device qvo-XXXX which neutron ovs agent will monitor and deal with. This patch is to deprecate the setting of 'nicira-iface-id' to XenServer VIF (which will result in 'iface-id' in ovsdb) and use 'neutron-port-id'. Note: There is no problem if we don't use neutron-ovs-agent polling mode Change-Id: I878602b5a84106634a211735c0002580293e3c06
Team and repository tags
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:
https://developer.openstack.org/api-guide/compute/ https://developer.openstack.org/api-ref/compute/
For more information on OpenStack APIs, SDKs and CLIs, please see:
https://www.openstack.org/appdev/ https://developer.openstack.org/
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
For information about the different compute (hypervisor) drivers supported by Nova, please read:
https://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:
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: