Hi Daya, Anil, NeutronNorthbound is same time tomorrow [8:00-9:00pm PST/PDT, 8:30-9:30pm IST], so we can’t have same time tomorrow. Any other works fine for me. Regards, Vishal.

no worries anil! would tomorrow morning IST be ok? myself and vishal are ok with anytime except 8.30 to 9.30 am (neutron northbound), i guess andre and sam are east coast though, so if morning IST

Hi Folks, Sorry for last moment notice, but we will have to move this meeting to sometime tomorrow. I need to attend internal meeting which i can't skip. Can we do it same time tomorrow? Anil --

This email is a formal notification that FaaS depends on the following projects. No changes are required. controller mdsal odlparent openflowplugin ovsdb Thanks! Xingjun

Acknowledging the dependency. Ryan neutron-dev-bounces@... wrote on 09/03/2015 05:51:14 AM: > From: Sam Hague <shague@...> > To: sfc-dev@..., controller- > dev@..., openflowplugin- > dev@...,

Project: OVSDB Offset: 2 Release plan finalized: Yes Extra configuration or resource needed: No Project check list completed: Yes Wave from system test: No Use CI infrastructure for system

Brady, the rsp piece just as anyone using SFC will need the ability to query for the rendered service chains. So this is more of a functional dependency rather than a code or compile

Sam, Are you sure OVSDB depends on SFC? SFC already depends on OVSDB, so that would create a cyclic dependency. What does OVSDB need from SFC? Regards, Brady

This email is a formal notification that OVSDB depends on the following projects. No changes are required. controller mdsal neutron odlparent openflowplugin sfc yangtools Thanks, Sam

please let me know your e-mail id, i will add you to the hangout session. -- Thanks Anil

Hi Vishal, Thank you very much! I will try it. Best Marcelo Sent from Samsung Mobile

Dear OVSDB project, I would like to notify you that the VTN project has dependencies on your project in Beryllium. As you know, VTN project uses the old OVSDB southbound plugin and

Since we couldn’t fit it within time we had for HWVTEP meeting, Anil will be doing a Google Hangout in which he will give an overview of OVSDB Southbound. Date: 3rd September 2015

Thanks. Sent from my Android phone using Symantec TouchDown (www.symantec.com)

With the current implementation that's the case, because ovsdb is as of now is not cluster aware. But once we make it cluster aware, only one instance of ovsdb will be writing to data store. On

Hi Anil, Sorry, I meant "will each of the nodes write to the operational data store?" If ovsdb is connected to all the nodes, each will get the ovsdb notification and do a write transaction to the

Sounds good. Andre

Hi Andre, Yes. In order to make icmp type writeable, We have to modify and compile a version of ovs. The change is minimal, but I’m not sure if the OVS folks would merge that upstream. Marcelo and

I think someone said on the call yesterday that OVS doesn't support modifying the type or code in ICMP. That's confirmed here for OVS

Logically there is only one Operational/Config data store for all the nodes in the cluster. As of now persistence of operational data store is disabled, it only persist config data store. On Wednesday