On 3/31/26 8:07 AM, Ales Musil wrote:
> On Fri, Mar 27, 2026 at 5:17 PM Dumitru Ceara via dev <
> [email protected]> wrote:
> 
>> Add a new Documentation/topics/dynamic-routing/ section covering:
>> - OVN's integration model with external routing daemons
>> - Architecture diagrams for IP route exchange and EVPN
>> - Deployment scenario diagrams for both IP routing and EVPN
>> - IP route advertisement and learning mechanisms
>> - VRF management
>> - EVPN remote VTEP discovery, FDB/neighbor learning, and
>>   Advertised MAC Binding
>>
>> Reported-at: https://redhat.atlassian.net/browse/FDP-3118
>> Assisted-by: Claude, with model: claude-opus-4-6
>> Signed-off-by: Dumitru Ceara <[email protected]>
>> ---
>>
> 
> Hi Dumitru,
> 

Hi Ales,

> thank you for the patch, this is nice addition, I have just two small
> comments down below.
> 

Thanks for the review!

> 

>> +Advertised MAC Binding
>> +~~~~~~~~~~~~~~~~~~~~~~
>> +
>> +The ``Advertised_MAC_Binding`` table in the Southbound database is
>> +populated by ``ovn-northd`` for EVPN-enabled logical switches.  It
>> +contains the IP and MAC address pairs that should be announced to the
>> +external network fabric.  Each record includes:
>> +
>> +- ``datapath`` --- The logical switch this binding belongs to.
>> +- ``logical_port`` --- The port binding this entry is associated with.
>> +- ``ip`` --- The IP address to announce.
>> +- ``mac`` --- The MAC address to announce.
>>
> 
> This is slightly incosistent, the  "Advertised_Route" explanation is lacking
> the column explanation. Maybe we should add that too WDYT?
>

Good point, I'll add that in v2.


> +
>> +``ovn-controller`` reads these records and installs the corresponding
>> +static FDB and neighbor entries on the appropriate kernel interfaces,
>> +making them available to the routing daemon for EVPN advertisement.
>> +
>> +EVPN Source IP Configuration
>> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> +
>> +The ``ovn-evpn-local-ip`` option in the ``Open_vSwitch`` table
>> +``external_ids`` configures the source IP addresses used for EVPN VXLAN
>> +tunnels.  The format supports per-VNI IP assignment::
>>
> 
> nit: Double colon.
> 

Ack.

Regards,
Dumitru

_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to