[openstack-dev] [Neutron] Removing udp_port field from 'ml2_vxlan_endpoint' table

Mathieu Rohon mathieu.rohon at gmail.com
Mon Mar 23 13:49:05 UTC 2015

Hi romil,

I think the main purpose of this DB field is to maintain the compatibility
in dataplane between OVS and LinuxBridge which, by default, don't use the
same UDP port for VXLAN.
It might be useful for a cloud admin which wants to run some nodes with LB
and some others with OVS.

I feel like your patch proposal will enable this scenario if the
tunnel_update() RPC message gets updated with the UDP port too.


On Mon, Mar 23, 2015 at 11:40 AM, Romil Gupta <romilgupta19 at gmail.com>

> Hello everyone,
> There is regarding the following bug:
> https://bugs.launchpad.net/neutron/+bug/1373359
> May I know what is the significance of having the '*udp_port'* field in
> the  *'ml2_vxlan_endpoints*' table in Neutron DB, Do we have any plans in
> future that we could use this field for synchronization or any other
> purpose instead of simply keeping it in the DB.
> The following patchset will fix the bug mentioned above,
> https://review.openstack.org/#/c/153891/
> But the question still remains the same. Do we need to keep this field or
> we need to remove it?
> --
> *Regards,*
> *Romil *
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150323/1b7f5ced/attachment.html>

More information about the OpenStack-dev mailing list