diff options
| author | Kevin_Zheng <zhengzhenyu@huawei.com> | 2018-04-23 15:41:21 +0800 |
|---|---|---|
| committer | Matt Riedemann <mriedem.os@gmail.com> | 2018-07-16 13:57:09 -0400 |
| commit | 79dac41fee178dabb547f4d7bc10609630767131 (patch) | |
| tree | 5d877e273d064d0dc845b617a8770f6fc5493b29 /requirements.txt | |
| parent | b2dafb1ee8c125cbeca92871e9478ac412084292 (diff) | |
| download | nova-79dac41fee178dabb547f4d7bc10609630767131.tar.gz | |
Use ThreadPoolExecutor for max_concurrent_live_migrations
This changes the max_concurrent_live_migrations handling
to use a ThreadPoolExecutor so that we can control a bounded
pool of Futures in order to cancel queued live migrations
later in this series.
There is a slight functional difference in the unlimited
case since starting in python 3.5, ThreadPoolExecutor will
default to ncpu * 5 concurrently running threads. However,
max_concurrent_live_migrations defaults to 1 and assuming
compute hosts run with 32 physical CPUs on average, you'd
be looking at a maximum of 160 concurrently running live
migrations, which is probably way above what anyone would
consider sane.
Co-Authored-By: Matt Riedemann <mriedem.os@gmail.com>
Part of blueprint abort-live-migration-in-queued-status
Change-Id: Ia9ea1e164fb3b4a386405538eed58d94ad115172
Diffstat (limited to 'requirements.txt')
| -rw-r--r-- | requirements.txt | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/requirements.txt b/requirements.txt index 2e1f9246a8..5b48ebb5fe 100644 --- a/requirements.txt +++ b/requirements.txt @@ -67,3 +67,4 @@ os-service-types>=1.2.0 # Apache-2.0 taskflow>=2.16.0 # Apache-2.0 python-dateutil>=2.5.3 # BSD zVMCloudConnector>=1.1.1;sys_platform!='win32' # Apache 2.0 License +futures>=3.0.0;python_version=='2.7' or python_version=='2.6' # PSF |