Deprecate and remove libvirt.api_thread_pool option
Bug #1254811 reported by
Matt Riedemann
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
We should deprecate the libvirt.
https:/
The reasons why this should be removed are detailed here:
Changed in nova: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in nova: | |
milestone: | none → icehouse-2 |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | icehouse-2 → 2014.1 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/59941 github. com/openstack/ nova/commit/ 22cd7cc27ca8285 c1674e370e256ec 84d3f2a20a
Committed: http://
Submitter: Jenkins
Branch: master
commit 22cd7cc27ca8285 c1674e370e256ec 84d3f2a20a
Author: Michael Kerrin <email address hidden>
Date: Mon Nov 25 11:03:26 2013 +0000
Remove the api_thread_pool option from libvirt driver
This gave us the option to select if calls to libvirtd are done
in a native thread or directly. This was added because the person
who wrote the thread pool code was afraid of regressions for existing
deployments. But now we have enough features in nova that require
that this is always set to True or else users can have issues with
them. To this point the firewall overrode this option to make
sure that its call was always in a native thread no matter the
value of this option was.
The reasons behind this were discussed during this review: /review. openstack. org/#/c/ 57000/
https:/
Closes-Bug: #1254811
DocImpact: removes api_thread_pool flag from the libvirt group
Change-Id: Ifad7f1bdf2af69 e4fcd6f9a04bf2f 7ff5251afd6