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)
(if called by the same worker..)
Change-Id: I3d0a354d999f7a69b7ae5ceaf9ab2f3d59739132
(cherry picked from commit c0459dc8c6607b8f1cb742a6fad23738bc8c5118)
There wire provider port function had two definitions for the same
parameter (mac and lladdr). This patch is merging them and ensuring
it gets used on the NB DB Driver so that the PERMANENT ip nei entries
get added for the router gateway ports (cr-lrp)
Closes-Bug: #2068699
Change-Id: I9649cd185b100c9941887e3440bad8d39881f92c
(cherry picked from commit a4e307e6f53794532284f02c91c0ff7a96fb242f)
In the case of the subnet advertisement method, we do not
announce the route to the tenant subnet via BGP. While the routes
in br-ex are good, they do not fully expose the subnet.
This change exposes the router interface that connects the
tenant subnet.
Closes-Bug: 2068730
Change-Id: Id7dd902e5e2010ba41052cc9316db8518349c755
(cherry picked from commit bc1dc8ec9ea2438fe89ad0d9535dfddd05c463d9)
Even if expose_tenant_networks is not enabled, cr-lrp IPs must
be exposed
Closes-Bug: #2068028
Change-Id: Ibcffbad5204bfbc1a42c157755ac9ae9d7b67766
(cherry picked from commit d24d6fbf9fbd8dab260fd6c720d42edd052f76a9)
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)
There was a bad comparison of datapath types, we compared router
datapath is equal to loadbalancer datapaths instead of if it is included
there.
Closes-bug: #2064922
Change-Id: I4f92d75f512ca906ad884e9da21ee7048b1dc5d6
Signed-off-by: Jakub Libosvar <libosvar@redhat.com>
When options.requested-chassis is not in sync with
external_ids.neutron:host_id it would pick both hosts, causing duplicate
announcements from more than 1 host.
This has been fixed in change 910305, but was left unchanged for the
sync method, causing issues when the sync interval was re-evaluating all
lsp's on the node.
The code for determining the chassis of a port has been moved from the
base_watcher to driver_utils so the logic for the event is the same as the
logic when fetching the records from the northbound database.
Related-bug: #2049902
Change-Id: I545d6b41fd308eb56e5295657260718dc14868f7
(cherry picked from commit 1bacff1dff825d267c390752fa21592c2e6f6588)
Update the URL to the upper-constraints file to point to the redirect
rule on releases.openstack.org so that anyone working on this branch
will switch to the correct upper-constraints list automatically when
the requirements repository branches.
Until the requirements repository has as stable/2024.1 branch, tests will
continue to use the upper-constraints list on master.
Change-Id: I481fc4bce82210822f63a3f80732facccf2a7fb6
Added check in LSP events to see if the event would belong to a network
that is exposed remotely (e.g. tenant networks behind router)
Change-Id: Idcc7880fc877f0a876c65bb1877ec4f89c2af5aa
Besides changing the default driver to the NB driver, it also
adapt to the new section for the ovn configurations
Change-Id: I9a2d0bc9b80fdf0c9e92d06103c03dcf5b018f49
When deleting an OVN LB with an attached FIP, the FIP is not
withdrawn from the BGP interface where it was exposed.
This patch corrects the behavior in accordance with the events
received from the OVN NB DB, taking as main source the vips
field provided in events to detect if added/removed entries.
Closes-Bug: #2049535
Change-Id: If0bca4a39a857364582804b64140f9a36bfc422a
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
Since the requested-chassis superseeds the placement in external_ids
(which is managed by neutron), we should preferable use that instead of the
value set by neutron (which _could_ lag or be wrong in specific scenario's)
Also update logic for FIP handling to make migrations more efficient.
Closes-Bug: #2049902
Change-Id: I7f73a1ba7956f22e58fdde383775e88bf72cba14
This also requires to use redist kernel in FRR, so there is a change
here which allows to define the default redistribute options in the FRR
template.
Since now this method is now available, the separate KERNEL_LEAK template
can be removed, as the only difference was the redist kernel, instead of
redist connected.
Related-Bug: #2017886
Change-Id: I570d8c482f3d17d63d66699e402c84dc61787638
In create_interface method we trimm interface name up to 16 symbols,
however in all following methods we do not care about same trimm, which
causes calls to such interfaces fail with NetworkInterfaceNotFound
Closes-Bug: #2054599
Change-Id: I15f773afa64079eec6534c53eab0e9b7dd796d5f
tox now always recreates an env although the env is shared using envdir
options.
~~~
$ tox -e genpolicy
genpolicy: recreate env because env type changed from
{'name': 'genconfig', 'type': 'VirtualEnvRunner'} to
{'name': 'genpolicy', 'type': 'VirtualEnvRunner'}
~~~
According to the maintainer of tox, this functionality is not intended
to be supported.
https://github.com/tox-dev/tox/issues/425#issuecomment-1011944293
Change-Id: I18ad8e5de031bc6be1b8e01860585ffae5ec0aa5
OVN deprecated the datapath_group column from Load_Balancer table. Now
this column was split in two: ls_datapath_group and lr_datapath_group.
This patch changes the code to also look for the datapath group in these
new columns.
This change is backward compatible and will work with a newer or older
version of OVN.
Change-Id: Ia3a95b77fccaa056aa9169114d102258f015002f
Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
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
Ideally the _run method should not do a check to see if row is valid.
Also, add the _get_ips_info method in base to get in line with LSP events
Change-Id: I7320ba37d622cd6b7de55e994caf657fb8b70b8d
This patch adds support to the OVN LBs created when a port forwarding
(PF) is configured over a FIP for the NB driver.
Closes-Bug: #2049415
Change-Id: I95d132172d54329306f41fee2cc631e27ccfd8c4
We can use the omit option instead of adding --omit argument, so that
we can run coverage commands outside of tox easily. Also this fixes
the inconsistent omit used in some coverage commands in tox.
Change-Id: I1efa406401c2e8a6b705daef4921b2dec7d55f2e
The vrysh command also allows reading from file and when using
this option, it works perfectly.
Closes-Bug: #2049736
Change-Id: I6cbee6739d8dddb43118585d1c03ad3eda8e4cbf
The patch simplifies the function searching for used routing table or
generating a new one. Since the method is no longer massive and complex
the unittests were added.
Change-Id: I75d8c4fdaed38a99b721b9077088952aaeb1b9a6
Signed-off-by: Jakub Libosvar <libosvar@redhat.com>