ovn-controller can be configured with a system-id override file or
-n option to use any suffix for OVSDB options. Currently ovn-bgp-agent
just uses a constant "bgp" for this and there is no way to change it.
48db2a7a35
Let's allow this suffix to be set via a config option instead.
Change-Id: Ida30b46e16ddcdc2d82af980546876f72a845c1d
(cherry picked from commit e3cb1b4a472e0c2743690af62768a96a1c2b8c00)
Creates VRF/VXLAN per VNI, exposed through FRR with kernel routes
Vlan interfaces are added to the appropriate VNI, configured per bgpvpn
config options on the logical switch.
Related-bug: #2051105
Change-Id: I097c4629922d787827aba7761164f4004ed1305a
(cherry picked from commit b3ca890f471fc2694342edc1f22670913cece934)
If SNAT on the router is enabled, then the subnet is reachable
from the outside, but all new sessions created from within the subnet
will be SNAT-ed. So those sessions will use the external IP of the router.
For example whitelisting specific tenant ips would not be possible.
With SNAT disabled, the neutron router will act as a normal gateway, and
sessions created from within a tenant vm will be sent from the real ip.
Closes-Bug: #2052292
Change-Id: Ib97065fb2fcca069195278fea804256370d21816
This includes the option to use the OVN-Cluster for routing
instead of the kernel.
It also updates the supportability matrix to better reflect the
current status, and makes a little reorg on the organization
structure
Change-Id: If8fb9a42f74511e9f70a25d7c08dce99c20c3f10
With the move to be included in the Neutron governance we have to update
the references from x/ to openstack/
Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
Change-Id: I9bdd16d1feacefa0a9937bcf322ad7c242b506d4
This patch adds the option to filter the tenant subnets to
be exposed depending on them belonging or not to an
address_scope (i.e., to a subnet pool associated to an
address_scope).
Change-Id: Iacbcc2ef094858f82166273d5b23c81f10324726
Docs should be published at https://ovn-bgp-agent.readthedocs.io/
Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
Change-Id: I4e59fabd66aa9e67d59937762ff9eadca8fe33fd
This driver allows to announce tenant networks with
an address scope via the virtual router IP.
For this to work, all routers in the respective L2
network must be reachable to each other and the
ovn-bgp-agent/frr needs an IP in this network to
talk to its BGP peer.
The following changes have been made:
- To filter which networks are announced via which
agent/BGP session, we added a filter on the
OpenStack address scope
- Networks are announced instead of VM IPs
- Add SubnetRouterUpdateEvent to handle updates of
lrp ports
Depends-on: https://review.opendev.org/c/openstack/neutron/+/861719
Change-Id: I6e48c7e056ba2101ad670ab54c96e072459c5e65
A new flag is added so that we can either expose all the
tenant network IPs (expose_tenant_networks) or just the
IPv6 GUA ones (expose_ipv6_gua_tenant_networks).
If the expose_ipv6_gua_tenant_network flag is enabled, before
exposing the tenant IPs it is checked if they are IPv6 and
of global type, and only in that case they will be advertized.
Story 2010374
Task 46609
Change-Id: Ifa1e25aabb3f6a3fc5f1e5ba5a32bfedadf6765a
Allow the user to configure the VRF settings to e.g. run
multiple agents per host.
The constants OVN_BGP_NIC, OVN_BGP_VRF and OVN_BGP_VRF_TABLE
have been replaced by configurable config options:
- OVN_BGP_NIC renamed to bgp_nic (default: "bgp-nic")
- OVN_BGP_VRF renamed to bgp_vrf (default: "bgp-vrf")
- OVN_BGP_VRF_TABLE renamed to bgp_vrf_table_id (default: 10)
Change-Id: I863e7bb140cd85a4ecefe6ccaad8adc5eae0cbd9