File: ovs_agent_explicitly_egress_direct-a5989bd33844c0f4.yaml

package info (click to toggle)
puppet-module-neutron 25.0.0-6
  • links: PTS, VCS
  • area: main
  • in suites: sid, trixie
  • size: 3,708 kB
  • sloc: ruby: 12,680; python: 38; sh: 15; makefile: 10
file content (9 lines) | stat: -rw-r--r-- 483 bytes parent folder | download | duplicates (3) 
1
2
3
4
5
6
7
8
9
 
---
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.