ad9f37350a
The confirm resize flow in the compute manager runs on the source host. It calls RT.drop_move_claim to drop resource usage from the source host for the old flavor. The problem with drop_move_claim is it only decrements the old flavor from the reported usage if the instance is in RT.tracked_migrations, which will only be there on the source host if the update_available_resource periodic task runs before the resize is confirmed, otherwise the instance is still just tracked in RT.tracked_instances on the source host. This leaves the source compute incorrectly reporting resource usage for the old flavor until the next periodic runs, which could be a large window if resizes are configured to automatically confirm, e.g. resize_confirm_window=1, and the periodic interval is big, e.g. update_resources_interval=600. This fixes the issue by also updating usage in drop_move_claim when the instance is not in tracked_migrations but is in tracked_instances. Because of the tight coupling with the instance.migration_context we need to ensure the migration_context still exists before drop_move_claim is called during confirm_resize, so a test wrinkle is added to enforce that. test_drop_move_claim_on_revert also needed some updating for reality because of how drop_move_claim is called during revert_resize. And finally, the functional recreate test is updated to show the bug is fixed. Change-Id: Ia6d8a7909081b0b856bd7e290e234af7e42a2b38 Closes-Bug: #1818914 Related-Bug: #1641750 Related-Bug: #1498126 |
||
|---|---|---|
| api-guide/source | ||
| api-ref/source | ||
| devstack | ||
| doc | ||
| etc/nova | ||
| gate | ||
| nova | ||
| playbooks/legacy | ||
| releasenotes | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| MAINTAINERS | ||
| README.rst | ||
| babel.cfg | ||
| bindep.txt | ||
| lower-constraints.txt | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.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: