90d5b388e1
On OVS agent, trunk extension is always loaded. If trunk plugin is not enabled server side, we don't want to enable extension on agent side. It will avoid declaration of RPCServer for Trunk and SubPort objects. To effectively disable the trunk extension, let's introduce a new parameter under [OVS] group so that an operator turn that setting off. The default value will stay True for now to keep backward compatibility with previous deployments. Closes-bug: #2058712 Change-Id: I94602d5f3159d9a2d5b988c9ab6cdd20dfd4af5b Signed-off-by: Arnaud Morin <arnaud.morin@ovhcloud.com>
12 lines
621 B
YAML
12 lines
621 B
YAML
---
|
|
features:
|
|
- |
|
|
An new option name ``trunk_enabled`` has been added to
|
|
``neutron-openvswitch-agent`` under ``OVS`` group. This new option can be
|
|
set to ``False`` in order to disable loading the ``trunk`` extension on
|
|
agent side. The default value for this option is ``True`` to keep backward
|
|
compatibility with previous deployments. The recommendation is to set this
|
|
option to ``False`` if you do not use the ``trunk`` extension, so that
|
|
the number of queues created by the RPCServer will reduce. This can have
|
|
a very good impact on large-scale scenario using RabbitMQ message broker.
|