Balazs Gibizer
2275b8545e
This rewrites the core logic of scatter-gather to use the futurist lib that provides a consistent API to use either Green or native ThreadPoolExecutor. This way the scatter-gather code can be made independent from the actual concurrency backend. In this change we also create a separate executor for the scatter-gather calls to better control it. A new config option [default]cell_worker_thread_pool_size is added to define the number of threads in this ThreadPoolExecutor. For the GreenThreadPoolExecutor case this config is ignored as only real threads are expensive, green threads doesn't. As oslo.sevice use os.fork(), and fork copies the parent process state to the children processes we need to make sure that the children processes get a proper, fresh executor state, so we destroy the executor just before the fork. The fixtures.SynchronousThreadPoolExecutorFixture is deleted. It was globally mocking futurist.GreenThreadPoolExecutor which would now mocking more than what we want. There was only one usage of it in the ComputeManager testing where it is replaced with a direct change of the manager internal executor in the test setup to get the same, but localized, result. Note that testing the threading mode is done in nova-next job in I36c68740fae3e3a9bd3286a1b66d86fd3341aff5, pool statistics reporting will be added by Id4244f5ae0fd49c99af2898789cdd510859e150d, and documentation about our threading tunables are in I003177de3a9f69c71c19eb8eaa7232785e03e669. Change-Id: Ibff6c73ad9af911a42204e53fee31ed5537c829d
============== OpenStack Nova ============== OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), VMware and OpenStack Ironic. 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://docs.openstack.org/api-guide/compute/>`__ - `Compute API Reference <https://docs.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. To understand better the processes that the team is using, please refer to the `Process document <https://docs.openstack.org/nova/latest/contributor/process.html>`__. 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/