On 9/12/24 19:45, Roberto Bartzen Acosta wrote: > > - The result of this synchronization is basically: > > - SB->NB: creating/deleting/updating > Logical_Router_Static_Route > > entries for learned routes in the Routing_Information_Base > > table (using the > > key). > > Why would you see the need to push the learned routes to the northbound > database? I would see this as just creating chaos in the CMS. > I would rather keep them only in the SB and let northd do the merging. > > > This is not necessary at all! It would not be necessary to sync a new > table with NB since the learned routes can be redistributed as static > routes via OVN-IC, for example. The solution as a whole needs to be > generic enough that we can redistribute/learn static routes in addition > to directly connected routes. > So, as long as northd merges these routes, it should work perfectly > fine! Of course we need to be careful with the route policies that can > block some prefix.
While I agree that it's probably not desirable to write these dynamic routes in the NB I think it would be useful to have a way to dump both "static" and "dynamic" routing table contents from a single place. It would make debugging easier. E.g.: ovn-nbctl --all lr-route-list <router> [dumps all static routes and also learnt (received) routes] However, that means we either need ovn-nbctl to connect to the SB or we propagate the information to the NB for nbctl to read. Regards, Dumitru _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
