aaf37a26d6
In change Ib0cf5d55750f13d0499a570f14024dca551ed4d4, we stopped waiting for vif plug events during hard reboot and start, because the behavior of neutron plug events depended on the vif type and we couldn't rely on the stale network info cache. This refines the logic not to wait for vif plug events only for the bridge vif type, instead of for all types. We also add a flag to _create_domain_and_network to indicate that we're in the middle of a reboot and to expect to wait for plug events for all vif types except the bridge vif type, regardless of the vif's 'active' status. We only query network_info from neutron at the beginning of a reboot, before we've unplugged anything, so the majority of the time, the vifs will be active=True. The current logic in get_neutron_events will only expect events for vifs with 'active' status False. This adds a way to override that if we know we've already unplugged vifs as part of a reboot. Related-Bug: #1744361 Change-Id: Ib08afad3822f2ca95cfeea18d7f4fc4cb407b4d6 |
||
|---|---|---|
| api-guide/source | ||
| api-ref/source | ||
| contrib | ||
| devstack | ||
| doc | ||
| etc/nova | ||
| gate | ||
| nova | ||
| placement-api-ref/source | ||
| playbooks/legacy | ||
| releasenotes | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| MAINTAINERS | ||
| README.rst | ||
| babel.cfg | ||
| bindep.txt | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tests-py3.txt | ||
| tox.ini | ||
README.rst
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, OpenStack Ironic and PowerVM.
Use the following resources to learn more.
API
To learn how to use Nova's API, consult the documentation available online at:
For more information on OpenStack APIs, SDKs and CLIs in general, refer to:
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
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:
Other Information
During each Summit and Project Team Gathering, we agree on what the whole community wants to focus on for the upcoming release. The plans for nova can be found at: