2e11d85d6b
Introduce calls to collect host routes for floating IP's in a DVR-aware way. When a floating IP is associated through a distributed router, the next-hop for the floating IP is announced as the floating IP agent gateway port on the corresponding host. Change-Id: I654e4d2496e19c011653eedb87c9b6026f801e9f Implements: blueprint bgp-dynamic-routing DocImpact: Neutron BGP should have docs created for the feature
24 lines
1.2 KiB
YAML
24 lines
1.2 KiB
YAML
---
|
|
prelude: >
|
|
Announcement of tenant prefixes and host routes for floating
|
|
IP's via BGP is supported
|
|
features:
|
|
- Announcement of tenant subnets via BGP using centralized Neutron
|
|
router gateway port as the next-hop
|
|
- Announcement of floating IP host routes via BGP using the centralized
|
|
Neutron router gateway port as the next-hop
|
|
- Announcement of floating IP host routes via BGP using the floating
|
|
IP agent gateway as the next-hop when the floating IP is associated
|
|
through a distributed router
|
|
issues:
|
|
- When using DVR, if a floating IP is associated to a fixed IP direct
|
|
access to the fixed IP is not possible when traffic is sent from
|
|
outside of a Neutron tenant network (north-south traffic). Traffic
|
|
sent between tenant networks (east-west traffic) is not affected.
|
|
When using a distributed router, the floating IP will mask the fixed
|
|
IP making it inaccessible, even though the tenant subnet is being
|
|
announced as accessible through the centralized SNAT router. In such
|
|
a case, traffic sent to the instance should be directed to the
|
|
floating IP. This is a limitation of the Neutron L3 agent when using
|
|
DVR and will be addressed in a future release.
|