RFE: add possibility of advertising entire tenant subnet prefixes instead of single-host routes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ovn-bgp-agent |
In Progress
|
High
|
Unassigned |
Bug Description
ovn-bgp-agent currently advertises VM addresses on tenant network in BGP as single-host routes (IPv4 /32 and IPv6 /128).
This is the case both for the BGP driver (if expose_
This is rather inefficient, as it creates a large amount of advertisements (e.g., 192.0.2.1/32, .2/32, 3/32 and so on) that could easily been aggregated into a single advertisement (192.0.2.0/24). This ought to work equally well, considering that all the traffic to the tenant networks needs to pass through the cr-lrp port (gateway chassis) anyway.
If the feature [1] is implemented, it is obviously necessary to advertise advertise single-host routes directly from the compute nodes in order to bypass the gateway chassis. That said, having the ability to advertise the subnet prefixes would still be valuable in certain situations:
One example of such as situation would be two VMs maintaining (let's say 192.0.2.10 and 192.0.2.11) maintaining a failover address using Keepalived (192.0.2.234). Since the Keepalived failover address is not known to Neutron (beyond being present in the VM port's allowed_
Changed in ovn-bgp-agent: | |
importance: | Undecided → Medium |
importance: | Medium → Wishlist |
Changed in ovn-bgp-agent: | |
status: | New → Confirmed |
Changed in ovn-bgp-agent: | |
importance: | Wishlist → High |
status: | Confirmed → In Progress |
Related fix proposed to branch: master /review. opendev. org/c/openstack /ovn-bgp- agent/+ /907057
Review: https:/