Debian Codegraph @

releasenotes/notes/bgp-support-ef361825ca63f28b.yaml

raw
1 ---
2 prelude: >
3 Announcement of tenant prefixes and host routes for floating
4 IP's via BGP is supported
5 features:
6 - Announcement of tenant subnets via BGP using centralized Neutron
7 router gateway port as the next-hop
8 - Announcement of floating IP host routes via BGP using the centralized
9 Neutron router gateway port as the next-hop
10 - Announcement of floating IP host routes via BGP using the floating
11 IP agent gateway as the next-hop when the floating IP is associated
12 through a distributed router
13 issues:
14 - When using DVR, if a floating IP is associated to a fixed IP direct
15 access to the fixed IP is not possible when traffic is sent from
16 outside of a Neutron tenant network (north-south traffic). Traffic
17 sent between tenant networks (east-west traffic) is not affected.
18 When using a distributed router, the floating IP will mask the fixed
19 IP making it inaccessible, even though the tenant subnet is being
20 announced as accessible through the centralized SNAT router. In such
21 a case, traffic sent to the instance should be directed to the
22 floating IP. This is a limitation of the Neutron L3 agent when using
23 DVR and will be addressed in a future release.