Debian Codegraph @

releasenotes/notes/accepted_egress_direct-cc23873e213c6919.yaml

raw
1 ---
2 fixes:
3 - |
4 Bug https://bugs.launchpad.net/neutron/+bug/1732067 described a flooding
5 issue on the neutron-ovs-agent integration bridge. And bug
6 https://bugs.launchpad.net/neutron/+bug/1841622 proposed a solution for
7 it. The accepted egress packets will be taken care in the final egress
8 tables (61 when openflow firewall is not enabled, table 94 otherwise) with
9 direct output flows for unicast traffic with a minimum influence on the
10 existing cloud networking.
11 A new config option ``explicitly_egress_direct``, with default value False,
12 was added for the aim of distinguishing clouds which are running the
13 network node mixed with compute services, upstream neutron CI should be
14 an example. In such situation, this ``explicitly_egress_direct`` should be
15 set to False, because there are numerous cases from HA routers which can
16 not be covered, particularly when you have centralized floating IPs running
17 in such mixed hosts.
18 Otherwise, set ``explicitly_egress_direct`` to True to avoid the flooding.
19 One more note is if your network nodes are for networing services only, we
20 recommand you disable all the security_group to get a higher performance.