Jay Pipes
9ea340eb0d
Somewhere in the past release, we started using extremely complex code paths involving sharing providers, anchor providers, and nested resource provider calculations when we absolutely don't need to do so. There was a _has_provider_trees() function in the nova/api/openstack/placement/objects/resource_provider.py file that used to be used for top-level switching between a faster, simpler approach to finding allocation candidates for a simple search of resources and traits when no sharing providers and no nesting was used. That was removed at some point and all code paths -- even for simple "get me these amounts of these resources" when no trees or sharing providers are present (which is the vast majority of OpenStack deployments) -- were going through the complex tree-search-and-match queries and algorithms. This patch changes that so that when there's a request for some resources and there's no trees or sharing providers, we do the simple code path. Hopefully this gets our performance for the simple, common cases back to where we were pre-Rocky. This change is a prerequisite for the following change which adds debugging output to help diagnose which resource classes are running out of inventory when GET /allocation_candidates returns 0 results. That code is not possible without the changes here as they only work if we can identify when a "simpler approach" is possible and call that simpler code. Related-Bug: #1786055 Partial-Bug: #1786519 Change-Id: I1fdbcdb7a1dd51e738924c8a30238237d7ac74e1
========================
Team and repository tags
========================
.. image:: https://governance.openstack.org/tc/badges/nova.svg
:target: https://governance.openstack.org/tc/reference/tags/index.html
.. Change things from this point on
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:
- `Compute API Guide <https://developer.openstack.org/api-guide/compute/>`__
- `Compute API Reference <https://developer.openstack.org/api-ref/compute/>`__
For more information on OpenStack APIs, SDKs and CLIs in general, refer to:
- `OpenStack for App Developers <https://www.openstack.org/appdev/>`__
- `Development resources for OpenStack clouds
<https://developer.openstack.org/>`__
Operators
---------
To learn how to deploy and configure OpenStack Nova, consult the documentation
available online at:
- `OpenStack Nova <https://docs.openstack.org/nova/>`__
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:
- `Bug Tracker <https://bugs.launchpad.net/nova>`__
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:
- `Official Nova Documentation <https://docs.openstack.org/nova/>`__
- `Official Client Documentation
<https://docs.openstack.org/python-novaclient/>`__
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:
- `Nova Specs <http://specs.openstack.org/openstack/nova-specs/>`__
.. _Summit: https://www.openstack.org/summit/
.. _Project Team Gathering: https://www.openstack.org/ptg/