650fe118d1
Change I7b8622b178d5043ed1556d7bdceaf60f47e5ac80 started deleting the compute node resource provider associated with a compute node when deleting a nova-compute service. However, it would only delete the first compute node associated with the service which means for an ironic compute service that is managing multiple nodes, the resource providers were not cleaned up in placement. This fixes the issue by iterating all the compute nodes and cleaning up their providers. Note this could be potentially a lot of nodes, but we don't really have many good options here but to iterate them and clean them up one at a time. Note that this is best-effort but because of how the SchedulerReportClient.delete_resource_provider method ignores ResourceProviderInUse errors, and we could have stale allocations on the host for which delete_resource_provider is not accounting, namely allocations from evacuated instances (or incomplete migrations though you can't migrate baremetal instances today), we could still delete the compute service and orphan those in-use providers. That, however, is no worse than before this change where we did not try to cleanup all providers. The issue described above is being tracked with bug 1829479 and will be dealt with separately. Change-Id: I9e852e25ea89f32bf19cdaeb1f5dac8f749f5dbc Closes-Bug: #1811726 |
||
|---|---|---|
| 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: