Hi Everyone, I would like to shed some light on why l2gw logic in OpenStack neutron cannot be a part of the ODL ML2 mechanism driver. The core plugin (today also called ML2 plugin) is designed

Flavio, this looks like it could be very useful for CI. Thanks for the work :) Is there anyone in OVSDB land doing tests that could make use of this? If so, I'm

Soory I can’t, because it is 0:00 am next day for me

We can start some discussions around this in today (Monday) 9 am Pacific OpenFlow plugin meeting - which you should be able to attend remotely. Of course we have other topics to cover regarding

Ok, thanks, I can’t attend that in person, but we will have some representatives to attend.

Yi, Abhijit, I have created a placeholder for this topic during ODL design discussion summit - https://wiki.opendaylight.org/view/Events:Be_Dev_Forum#OF_Pipeline_Conflict_resolution We can use

Hema, good point, we need to fix the conflict before a flow is written to MDSAL data store, but this won’t impact we add this middle layer into openflowplugin, the reason to put it to openflowplugin

Thanks, Flavio, I tried it. These tools are awesome!

Hi folks, I was asked for an example dump of an openstack config on ovsdb netvirt and how one can piece mail the ovs ports to the overlay network that goes with it. For that, I ‘devstacked' 3 nodes

Hi again I'am trying to understand the relation you mentioned here: I can't figure this out in the case of a neutron port creation. The neutron port creation gets passed to the PortHandler. But

I feel that the openflow plugin may not the place to detect the flow / table conflict. When the flow / table request reaches the openflow plugin, the NSFs / application would have already configured

This sounds like a good candidate for Beryllium Developer Forum at the Summit. https://wiki.opendaylight.org/view/Events:Be_Dev_Forum

I’m very glad to hear many guys have realized this issue, Prem Sankar created this wiki pagehttps://wiki.opendaylight.org/view/OF_pipeline, this is a start point, please add other projects which

Hi Yi / Abhijit, We had proposed an idea in the ODL India forum on similar lines of Flow Conflict Prevention. Here is thelink to the presentation. We are interested in any discussion on

+ lacp-dev

Hi folks, After getting cross eyed from staring at postman outputs [1] to debug ovsdb net-virt, I decided to write a tool to dump mdsal info related to ovsdb and its netvirt (including high level

Hi Yi Yang, Agree with you, very good points and we were also thinking on similar lines about creating small framework that can detect conflicts/provide conflict resolution. Also, I had brought

Yi, This is a good topic - and OpenFlow plugin will likely be a good place for this. Are you planning to work on this? Why don't you join the next OpenFlow plugin meeting (at least for part of the

Vikram, I don't know of anything in the ovsdb or openflow protocols to assign addresses so that won't help. I have cc'ed the controller-dev alias to see if there is something else in odl that can