Operating System: All
Platform: All

Email on ovsdb-dev, from Daya, about how this works.

Hi pearl,
First word of caution - I am not sure if this is tested with netvirt autoconfig tunnel creation mode, or works with the same.
So, the assumption is that a transport zone is available, with a bunch of ovs nodes, which are already fully meshed.
Given this,when the l2gw create commands comes through, netivirt will build tunnels from each ovs endpt in the TZ (or other hwvtep endpts) to the new l2gw device. Netvirt will also populate all the remote TEPs in the physical locator table of the hwvtep, to enable it to build its own tunnels as and when needed.

Can you try the following –
Switch off tunnel autocreation, use REST aPI to create TZ with all OVS, and then see if u face any issues.
Use the netvirt autoconfig mode, but create the neutron network first, which will trigger creation of the TZ with OVS switches upfront, then add the l2gw API.

If we know this is the issue, (and it may be different from the exception you are seeing below), we can update the l2gw code as follows in case the netvirt auto0config mode is enabled –
It should not build tunnels as part of l2gw create operations. When l2gw conn-create comes through, it needs to look up the corresponding TZ, and add the hwvtep into this tz as an external endpt, this will enable tunnels from all ovs’s in that tz to the hwvtep, netvirt should also publish only the subset of physical locators in that tz onto the hwvtep.

Thanks,
daya