0a88916911
This extends the multi_cell_list module with batching support to avoid querying N*$limit total results when listing resources across cells. Instead, if our total limit is over a given threshold, we should query smaller batches in the per-cell thread until we reach the total limit or are stopped because the sort feeder has found enough across all cells to satisfy the requirements. In many cases, this can drop the total number of results we load and process from N*$limit to (best case) $limit+$batch or (usual case) $limit+(N*$batch). Since we return a generator from our scatter-gather function, this should mean we basically finish the scatter immediately after the first batch query to each cell database, keeping the threads alive until they produce all the results possible from their cell, or are terminated in the generator loop by the master loop hitting the total_limit condition. As a result, the checking over results that we do immediately after the scatter finishes will no longer do anything since we start running the query code for the first time as heapq.merge() starts hitting the generators. So, this brings a query_wrapper() specific to the multi_cell_list code which can mimic the timeout and error handling abilities of scatter_gather_cells, but inline as we're processing so that we don't interrupt the merge sort for a failure. Related-Bug: #1787977 Change-Id: Iaa4759822e70b39bd735104d03d4deec988d35a1 |
||
|---|---|---|
| api-guide/source | ||
| api-ref/source | ||
| contrib | ||
| devstack | ||
| doc | ||
| etc/nova | ||
| gate | ||
| nova | ||
| placement-api-ref | ||
| 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: