b214dfc419
Previously in the SchedulerReportClient, _get_provider_aggregates and _get_provider_traits would log a warning and return None on placement API errors. The callers were ignoring these errors, resulting in the internal ProviderTree representation potentially being out of sync with reality. With this change set, these two methods raise exceptions on API errors. As currently implemented, these errors will bubble up into the resource tracker and compute manager in the same way as other unhandled exceptions. That is, they land in the trap in update_available_resource_for_node, where they are logged and otherwise ignored. Why is this an improvement? Because at least the routine that encountered the error doesn't continue on as if nothing went wrong. (We could have dealt with this by having the callers check for None explicitly, but this approach was deemed more rigorous and robust.) Change-Id: I20fe0d895f61ec83759cf880a87238ecc43c08f5 blueprint: nested-resource-providers
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: