d0bc82d842
This configuration parameter for the ML2/OVS agent was added in I14fefe289a19b718b247bf0740ca9bc47f8903f4 and backported up to stable/queens, preventing flooding on integration bridge in some cases. It needs to be enabled on specific node types, so add option to configure it. Related-Bug: #1732067 Change-Id: Iff50d2d086c687ef9ec1ba878e24c06dfc8a7d99
10 lines
483 B
YAML
10 lines
483 B
YAML
---
|
|
features:
|
|
- |
|
|
Add new configuration parameter explicitly_egress_direct for ML2 OVS agent
|
|
When set to True, the accepted egress unicast traffic will not use action
|
|
NORMAL. The accepted egress packets will be taken care of in the final
|
|
egress tables direct output flows for unicast traffic so that operators can
|
|
set customized integration bridge name in l3 agent configuration.
|
|
This can be enabled on some nodes to prevent flooding on integration bridge.
|