Luis Tomas Bolivar 921e39ba02 Fixes at the documentation

This is a follow up of [1]

[1] https://review.opendev.org/c/openstack/ovn-bgp-agent/+/903407

Change-Id: Ifda13d090b1e298ae8b5393a313c2ea4df105fcb

2024-02-19 09:14:31 +01:00

10 KiB

Raw Blame History

BGP Supportability Matrix

The next sections highlight the options and features supported by each driver

BGP Driver (SB)

Exposing Method	Description	Expose with	Wired with	Expose Tenants	Expose only GUA	OVS-DPDK/HWOL Support	Supported
Underlay	Expose IPs on the default underlay network.	Adding IP to dummy NIC isolated in a VRF	Ingress: ip rules, and ip routes on the routing table associated with OVS Egress: OVS flow to change MAC	Yes (expose_tenant_networks)	Yes (expose_ipv6_gua _tenant_networks)	No	Yes

Exposing Method

Description

Expose with

Wired with

Expose Tenants

Expose only GUA

OVS-DPDK/HWOL Support

Supported

Underlay

Expose IPs on the default underlay network.

Adding IP to dummy NIC isolated in a VRF

Ingress: ip rules, and ip routes on the routing table associated with OVS Egress: OVS flow to change MAC

Yes

(expose_tenant_networks)

Yes (expose_ipv6_gua _tenant_networks)

Yes

BGP Driver (NB)

OVN version 23.09 is required to expose tenant networks and ovn Load Balancers, because Distributed Gateway port (cr-lrp) chassis information in the NB DB is only available in that version (https://bugzilla.redhat.com/show_bug.cgi?id=2107515).

The following table lists the various methods you can use to expose the networks/IPS, how they expose the IPs and the tenant networks, and whether OVS-DPDK and hardware offload (HWOL) is supported.

Exposing Method	Description	Expose with	Wired with	Expose Tenants or GUA	OVS-DPDK/HWOL Support	Supported
Underlay	Expose IPs on the default underlay network.	Adding IP to dummy NIC isolated in a VRF.	Ingress: ip rules, and ip routes on the routing table associated to OVS Egress: OVS-flow to change MAC	Yes (expose_tenant_networks)	No	Yes
L2VNI	Extends the L2 segment on a given VNI.	No need to expose it, automatic with the FRR configuration and the wiring.	Ingress: vxlan + bridge device Egress: nothing	N/A	No	No
VRF	Expose IPs on a given VRF (vni id).	Add IPs to dummy NIC associated to the VRF device (lo_VNI_ID).	Ingress: vxlan + bridge device Egress: flow to redirect to VRF device	Yes (Not implemented)	No	No
Dynamic	Mix of the previous. Depending on annotations it exposes IPs differently and on different VNIs.	Mix of the previous three.	Ingress: mix of all the above Egress: mix of all the above	Depends on the method used	No	No
OVN	Make use of an extra OVN cluster (per node) instead of kernel routing -- exposing the IPs with BGP is the same as before.	Adding IP to dummy NIC isolated in a VRF (as it only supports the underlay option).	Ingress: OVN routes, OVS flow (MAC tweak) Egress: OVN routes and policies, and OVS flow (MAC tweak)	Yes (Not implemented)	Yes	Yes. Only for ipv4 and flat provider networks

BGP Stretched Driver (SB)

Exposing Method	Description	Expose with	Wired with	Expose Tenants	Expose only GUA	OVS-DPDK/HWOL Support	Supported
Underlay	Expose IPs on the default underlay network.	Adding IP routes to default VRF table.	Ingress: ip rules, and ip routes on the routing table associated to OVS Egress: OVS-flow to change MAC	Yes	No	No	Yes

EVPN Driver (SB)

Exposing Method	Description	Expose with	Wired with	Expose Tenants	Expose only GUA	OVS-DPDK/HWOL Support	Supported
VRF	Expose IPs on a given VRF (vni id) -- requires newtorking-bgpvpn or manual NB DB inputs.	Add IPs to dummy NIC associated to the VRF device (lo_VNI_ID).	Ingress: vxlan + bridge device Egress: flow to redirect to VRF device	Yes	No	No	No

10 KiB Raw Blame History