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.
Reviewed: https:/ /review. opendev. org/c/openstack /neutron/ +/908173 /opendev. org/openstack/ neutron/ commit/ b38f72b2129ee37 7cb80132ca9c079 4b60585be6
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit b38f72b2129ee37 7cb80132ca9c079 4b60585be6
Author: Takashi Kajinami <email address hidden>
Date: Wed Feb 7 01:46:47 2024 +0900
Completely disable rpc workers when rpc_workers=0
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] 3e1e2d63b3383d2 8c9a36b00000ab8 9caffa3829
Closes-Bug: #2052484 3b145ded0ab8394 845a089696e
Change-Id: I878e50c3192ecd