b38f72b212
Currently at least 1 rpc worker is launched even when a user requests
zero workers by setting rpc_workers=0. The setting of rpc_workers=0 is
used when ml2-ovn plugin is used without any additional agent, and in
this deployment pattern the single rpc worker is not at all used.
This change ensures no rpc worker is launched when rpc_workers options
is explicitly set to 0. This may be classified as a breaking change,
but is consistent with the earlier change[1] for rpc_workers=0.
[1] 3e1e2d63b3
Closes-Bug: #2052484
Change-Id: I878e50c3192ecd3b145ded0ab8394845a089696e
17 lines
676 B
YAML
17 lines
676 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
Now setting ``[DEFAULT] rpc_workers = 0`` completely disables rpc workers.
|
|
In a deployment with additional agents, like the dhcp-agent, this option
|
|
should be set to a positive value. Note that all notifications from
|
|
neutron-server to agents were disabled when ``[DEFAULT] rpc_workers = 0``
|
|
is set in 22.0.0 release, so this was the requiremenet actually added in
|
|
that release.
|
|
|
|
fixes:
|
|
- |
|
|
[`bug 2052484 <https://bugs.launchpad.net/neutron/+bug/2002484>`_]
|
|
Now setting ``[DEFAULT] rpc_workers = 0`` completely disables rpc workers.
|
|
Previously one rpc worker was launched even though ``0`` is specifically
|
|
requested.
|