[ovs-dev] [PATCH ] Add tunnel key to Physical_Locator

Ben Pfaff blp at ovn.org
Wed Dec 23 06:07:09 UTC 2015


On Sun, Dec 06, 2015 at 06:04:45PM +0200, ofer.benyacov at gmail.com wrote:
> From: Ofer Ben Yacov <ofer.benyacov at gmail.com>
> 
> Currently the scenario of single logical bridge that use multiple locators
> with different tunnel key on each of the locators is not supported.
> In order to support much more flexibility in the tunnel settings, we need
> to add tunnel key column to the Physical_Locator table.
> 
> This patch is needed to support the usage of neutron L2GW as an inter-cloud
> gateway. The tunnel key that is set in the logical bridge will be used 
> 'internally' to connect the L2GW to the compute hosts and the key that 
> is set in the physical locator will be used to connect the L2GW to a 
> remote L2GW to form a tunnel between 2 clouds. In this case, the
> 'external' connection will use single 'dst_ip' on all the locators with 
> different tunnel key for each L2 domain.
> 
> Signed-off-by: Ofer Ben-Yacov<ofer.benyacov at gmail.com>

I doubt this has been tested, because the Physical_Locator table has an
index on (encapsulation_type,dst_ip), meaning that the database server
will disallow rows that have the same 'encapsulation_type' and 'dst_ip'
even if the new 'tunnel_key' column differs.



More information about the dev mailing list