neutron/releasenotes/notes/network-routed-subnets-cf4874d97ddacd77.yaml
Ryan Tidwell c613ede9fa Floating IP for routed networks: network:routed API
This change is needed for enabling floating IP's on routed networks.
To be able to create a subnet that spans all segments of a routed network,
a special subnet service type of 'network:routed' is used to denote a
network that can span all segments of a routed network.

To create floating IP's on a routed network, the subnet must be created
with a service_type of 'network:routed'. After the subnet has been
created, floating IP's can be allocated and associated as before.
See the design spec https://review.opendev.org/#/c/486450/ for
reference.

One caveat for this approach is that it requires the underlying
infrastructure to be aware of and able to route /32 host routes
for the floating IP. This implies that in practice, use of the
'network:routed' service type should be done in conjunction with
one or both of the following:

1. Third-party SDN backend that handles this service type in its
   own way
2. neutron-dynamic-routing and the BGP service plugin for announcing
   the appropriate next-hops for floating IP's. This is compatible
   with DVR and non-DVR environments.

Depends-On: Ibde33bdacba6bd1e9c41cc69d0054bf55e1e6454
Change-Id: I9ae9d193b885364d5a4d90538880d8e9fbc8df74
Co-Author: Thomas Goirand <zigo@debian.org>
Partial-Bug: #1667329
2020-12-17 14:21:30 +01:00

12 lines
564 B
YAML

---
features:
- |
A new subnet of type ``network:routed`` has been added. If such a subnet is
used, the IPs of that subnet will be advertized with BGP over a provider
network, which itself can use segments. This basically achieves a
BGP-to-the-rack feature, where the L2 connectivity can be confined to a
rack only, and all external routing is done by the switches, using BGP.
In this mode, it is still possible to use VXLAN connectivity between the
compute nodes, and only floating IPs and router gateways are using BGP
routing.