On Sun, Dec 06, 2015 at 06:04:45PM +0200, [email protected] wrote: > From: Ofer Ben Yacov <[email protected]> > > 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<[email protected]>
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. _______________________________________________ dev mailing list [email protected] http://openvswitch.org/mailman/listinfo/dev
