Balazs Gibizer
eda6792632
When running in eventlet mode we keep the original eventlet.tpool usage but when running in threading mode we call the functions directly on the thread of the caller. The patch_tpool_proxy() logic is removed from the libvirt driver as it was only needed for python old style classes which is not in use any more in python3 and the issue is not reproducible any more with virConnect even without the patching. ❯ python3 Python 3.12.10 (main, Apr 9 2025, 04:44:59) [GCC 14.2.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import eventlet >>> eventlet.monkey_patch() >>> from nova.virt.libvirt import host >>> h = host.Host(uri="qemu:///system") >>> h.get_connection() libvirt: error : internal error: could not initialize domain event timer URI qemu:///system does not support events: internal error: could not initialize domain event timer <libvirt.virConnect object at 0x7f829e94c170> >>> c = h.get_connection() >>> str(c) '<libvirt.virConnect object at 0x7f829e94c170>' >>> Signed-off-by: Balazs Gibizer <gibi@redhat.com> Change-Id: Ic60ab78cec2a9f9ba177568b69e738425e56cae1
============== 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/