2bdf51fed6
Some services (like Neutron) still pass `wait_interval` to ProcessLauncher, and it is still used in the eventlet backend to avoid CPU spin when no children exit. This patch allows the threading backend to accept it for compatibility. The value is ignored and a deprecation warning is logged. Additionally, this patch aligns the threading backend with eventlet by allowing multiple calls to launch_service() on the same ProcessLauncher instance. All services are now added to a single internal ServiceManager, avoiding runtime errors from Cotyledon and matching expected behavior. This improves compatibility and simplifies migration to the threading backend. Change-Id: I77a5f2fc7081d256be079b87aa86312d5cbfff1b
12 lines
621 B
YAML
12 lines
621 B
YAML
---
|
|
fixes:
|
|
- |
|
|
The ``threading`` backend now accepts the ``wait_interval`` argument
|
|
in ``ProcessLauncher`` for compatibility with services like Neutron.
|
|
The parameter is still used in the ``eventlet`` backend to reduce CPU usage
|
|
during child monitoring loops, but has no effect in ``threading``.
|
|
A warning is logged if it is passed.
|
|
In addition, multiple calls to ``launch_service()`` on the same
|
|
``ProcessLauncher`` instance are now supported, using a single
|
|
``ServiceManager`` internally. This makes the threading backend fully
|
|
compatible with how the ``eventlet`` backend behaves. |