Tony, Robert, Anil mentioned there is a possibility to add wildcard queries to mdsal? Is that a feature that can be added for Be? The idea is to be able to search for something using a field in the

Khal, no, those exceptions are OK. In the 7.12.1 schema datapath and iface type fields were added so you have to have the matching ovs version installed which most don't. I don't recall the exact ovs

The ovsdb project formally joins the OpenDaylight Beryllium Simultaneous Release and agrees to the activities and timeline documented on the Beryllium Release Plan Page. Thanks, Sam

Hi Sam, Do you think the following two exceptions explain some of the problem I have. Thanks. 2015-07-02 13:40:13,110 | DEBUG | n-invoker-impl-0 | OpenVSwitchUpdateCommand | 251 -

Hi Sam, The ovsdb loads the config and operational topology correctly, which is good I need that. But, what is not working for me is that openflowplugin is not adding switches to

Khal, the openstack modules do not write anything to operational. It relies on the southbound to do that and openstack listens for those changes when they happen. After that the openstack netvirt

Hi Sam, I commented out the openstack bundles in odl-ovsdb-openstack (please see below) to test if odl-ovsdb-southbound-impl-ui will be able to load the inventory operational node into datastore.

Dear All, Please find attached the L2 gateway slides.

Sam, if you add this as an item to [1], then we'll get it the next meeting. Ryan [1] https://wiki.opendaylight.org/view/NeutronNorthbound:FutureReleaseWishList neutron-dev-bounces@... wrote on

Ryan, Flavio, Ed, I wanted to start the conversation for adding support for l2-gw [1]. The l2-gw is a service plugin in neutron that has been included with kilo. We would need to add some changes to

Hi Ravi/Maruthi, Flow wise it looks good to me. Need minor clarification, with the current design are we assuming that connection management and table modification on hardware vtep will be done by

Hi all, the project wiki for hardware_vtep is at [1]. Feel free to add to the wiki as more information is developed or useful. Some of the work items for the OVSDB side of hardware_vtep are included

----- Forwarded Message -----

Hi all, Please add any feature requests to the google sheet at [1]. Simply add the feature, description and requester or resource names so that we can track the feature. We will then move them over

Hi Flavio, Responses inline. Yes, this is straightforward. We could try and backport this to neutron stable/kilo, there's a slight complication but I wonder if we could make it work. Bear with me,

[dropped controller-dev since this is ovsdb related] Simhon, there were some bugs [1] and [2] related to flow removed on network deletes in helium. Basically the bugs revolve around the fact that

Hi, We are working with Devstack of integration ODL Helium and Icehouse Openstack taken from: https://wiki.opendaylight.org/view/OVSDB:Helium_and_Openstack_on_Fedora20#VMs. All works well, but when

[cc’ing odl neutron-dev ovsdb-dev] Hi Armando, Sam ran into a snag while trying to use lithium against stable kilo. The issue is 2 fold: A) there is no stable/kilo branch for networking-odl; B) the

https://git.opendaylight.org/gerrit/#/c/23438/ Presumably it also wants to be cherry-picked to stable/lithium (and maybe stable/helium). --Colin