On 2/18/26 12:08 PM, Ales Musil wrote:
> On Wed, Feb 18, 2026 at 10:49 AM Dumitru Ceara via dev <
> [email protected]> wrote:
>
>> The default values didn't allow dual-stack deployments. Moreover, they
>> made very specific assumptions and would likely be overridden by the CMS
>> in all deployments.
>>
>> Instead make them mandatory if dynamic-routing-vni is configured for an
>> EVPN enabled logical switch.
>>
>> Also:
>> - made sure dynamic-routing-*-ifname are ignored if VNI not set (this is
>> what our docs said)
>> - moved the man page description of the options in the right place, in a
>> group listing all EVPN options
>>
>> Reported-at: https://issues.redhat.com/browse/FDP-3136
>> Signed-off-by: Dumitru Ceara <[email protected]>
>> ---
>> NOTE: As discussed on-list [0] this patch targets 26.03 (main branch
>> before hard freeze).
>>
>> [0]
>> https://mail.openvswitch.org/pipermail/ovs-dev/2026-February/430230.html
>> ---
[...]
>> diff --git a/ovn-nb.xml b/ovn-nb.xml
>> index ae37d03d15..d4cef12e04 100644
>> --- a/ovn-nb.xml
>> +++ b/ovn-nb.xml
>> @@ -795,27 +795,6 @@
>> <column name="external_ids" key="neutron:network_name">
>> Another name for the logical switch.
>> </column>
>> -
>> - <column name="other_config" key="dynamic-routing-bridge-ifname">
>> - Set the interface name for the bridge used for EVPN integration.
>> - The default name is <code>br-$vni</code>.
>> - Only relevant if <ref column="other_config"
>> key="dynamic-routing-vni"
>> - table="Logical_switch"/> is set to valid VNI.
>> - </column>
>> -
>> - <column name="other_config" key="dynamic-routing-vxlan-ifname">
>> - List of interface names used for the vxlan devices used for EVPN
>> - integration. The default name is <code>vxlan-$vni</code>.
>> - Only relevant if <ref column="other_config"
>> key="dynamic-routing-vni"
>> - table="Logical_switch"/> is set to valid VNI.
>> - </column>
>> -
>> - <column name="other_config" key="dynamic-routing-advertise-ifname">
>> - Set the interface name for the advertise device used for EVPN
>> - integration. The default name is <code>lo-$vni</code>.
>> - Only relevant if <ref column="other_config"
>> key="dynamic-routing-vni"
>> - table="Logical_switch"/> is set to valid VNI.
>> - </column>
>> </group>
>>
>> <group title="IP Address Assignment">
>> @@ -919,6 +898,16 @@
>> dropped, even if use_ct_inv_match is set to true.
>> Default: <code>false</code>.
>> </column>
>> + </group>
>> +
>> + <group title="EVPN Options">
>> + <p>
>> + These options control the EVPN configuration of the logical
>> switch.
>> + To enable EVPN integration set
>> + <ref column="other_config" key="dynamic-routing-vni"/> to a valid
>> + VNI number to represent the EVPN L2 domain extended by the
>> + logical switch.
>> + </p>
>>
>> <column name="other_config" key="dynamic-routing-vni"
>> type='{"type": "integer", "minInteger": 0,
>> @@ -929,9 +918,14 @@
>> </p>
>>
>> <p>
>> - The ovn-controller expects three interfaces to exist within the
>> - BGP vrf: <code>br-$vni</code>, <code>lo-$vni</code> and
>> - <code>vxlan-$vni</code>.
>> + All of the following configuration options must also be provided
>> + in order for the configuration to be valid:
>> + <ref column="other_config" key="dynamic-routing-bridge-ifname"
>> + table="Logical_switch"/>,
>> + <ref column="other_config" key="dynamic-routing-vxlan-ifname"
>> + table="Logical_switch"/>,
>> + <ref column="other_config"
>> key="dynamic-routing-advertise-ifname"
>> + table="Logical_switch"/>,
This last one should've been a dot instead of a comma.
[...]
>>
> Looks good to me, thanks.
> Acked-by: Ales Musil <[email protected]>
>
Hi Ales,
Thanks for the review!
I fixed up the small typo in the documentation and applied the patch to
main.
Regards,
Dumitru
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
