feat: Support OVN dynamic routing - #3557
Conversation
ca360bd to
11a0af2
Compare
Add two new config options to networks that can be uplink network for OVN networks: `ovn.dynamic_routing` and `ovn.dynamic_routing.vrf.id` When configured, dynamic-routing [0] will be enabled on OVN networks using this uplink network. With that, prefixes of ovn networks and load-balancers are added to the configured host routing table (`vrf.id`) of the active OVN chassis. [0] https://docs.ovn.org/en/latest/topics/dynamic-routing/architecture.html Signed-off-by: Jakob Mueller <me@jakobm.de>
11a0af2 to
0176b92
Compare
|
I also took a look on how to test this in lxc-ci, but it seems that ovn comes from |
|
Just discovered a bad caveat: |
|
We should move the daily tests to Debian 13 and using https://github.com/zabbly/ovn for the packages. That PPA is effectively dead at this point, we just haven't spent the time to update the tests yet. |
|
@ibot3 any update on this one? |
|
I am currently in the process of getting the change into OVN. But I also wanted to check if OVN has some option to allow multiple active gateway chassis for the same network, as this would give a better redundancy. |
Add two new config options to networks that can be uplink network for OVN networks:
ovn.dynamic_routingandovn.dynamic_routing.vrf.idWhen configured, dynamic-routing [0] will be enabled on OVN networks using this uplink network. With that, prefixes of ovn networks and load-balancers are added to the configured host routing table (
vrf.id) of the active OVN chassis.[0] https://docs.ovn.org/en/latest/topics/dynamic-routing/architecture.html
Why?
We have a setup where our incus nodes do not have a shared L2 connection, but all run a local routing daemon.
Currently, incus requires a shared L2 uplink network for OVN networks.
My plan was to configure an uplink bridge on each node, which is not directly connected to the fabric nor other nodes.
Instead, the local routing daemon distributes the routes coming directly from the OVN active gateway.
Using the bgp integration is no good option, as this would create a hard dependency on the incus daemon running.
(Only one host (=the active gateway) can announce the prefix)