As far as i know, No, but if somebody want to contribution, i think project should be fine with that. Anil -- Thanks Anil

Hi Daya/Sam, I have the few queries on the document. 1. There are 3 ways VXLAN can be established, i. VXLAN between OVS switches controlled by openstack and ODL. a.

Has any investigation been done to support sFlow collection from OVSDB?

tl;dr If you want OVSDB netvirt to be a stable feature in Beryllium, it will have to spin out as it's own project (proposed on or before 10/1/2015) and move to mature. Long version: Hey guys. I wanted

hi, here's a first draft of how the control flow to incorporate hwvtep into netvirt. sam, unfortunately, out of force of habit i started in ppt, and when i copied it to google, it got pasted as a

thanks ravi and alex! ravi, alex has also confirmed that the pkts are vxlan encapsulated, outer IP would have to be the TEP IP, and inner IP is immaterial since the slow path at the receiver would

Hi Daya, BFD operates on top of any data protocol (network layer, link layer, tunnels(vxlan tunnel), etc.) being forwarded between two systems. BFD provides failure detection on

hi sumit, you are right about not being able to determine the subnet, so we are stuck with your idea of picking a tunnel, or approach 2 or 3 i mentioned below, or some hybrid. if the IP is on a

Please see inline below: -- Sumit Garg Extreme Networks sumit@... +1 (919) 595-4971 From: daya kamath <daya_k@...> Reply-To: daya kamath <daya_k@...> Date: Monday, August 24, 2015 at 10:06 AM To:

You need to create a vlxan tunnel between the two host first, and then enable bfd on the tunnel ports on both end, yes, bfd pkt will be delivered as single hop, UDP port, please check the function

Yes everything is now in releng silo as Flavio pointed out, so it is fine to remove ovsdb silo. Thanks, Alexis

Yeah, we have moved out of the old silo [1] completely. All jobs for ovsdb are jjb based and use the releng [2] silo now. — flavio [1]: https://jenkins.opendaylight.org/ovsdb/ [2]:

Just that links in old Gerrits on the OpenStack side of things will fail. But that's sort of expected with really old submissions anyway. Even with our system logs don't stick around for more than 40

Andrew, what does this mean going forward? Flavio, Alexis, Marcus, everything has been moved over to jjb right? So we should be OK? Thanks, Sam

Greetings folks, We have finally surpassed the 6 month log retention window that OpenStack requires of their 3rd party CI systems. I figured I should send out to the list that I plan on finally

hi , i would like some clarification on the BFD implementation in OVS. http://openvswitch.org/pipermail/discuss/2015-February/016515.html indicates the BFD is not multi-hop but sent through the

Hi all, we moved the [OVSDB] meetings from 12:00p PST to 10:00a PST. This will start with tomorrow's meeting. Thanks, Sam [OVSDB]

my understanding is partly similar to that of sumit. creation of the VTEPs themselves is mgmt action, and should be out of scope for this activity. this value can be published in tunnel_ips field in

Hi Vishal, For question (1), as SAM mentioned hw-vtep netvirt provider should make sure that a barematel mac (ucast_mac_local) learnt on one device (running hardware_vtep) is added to

Hi, Added inline comments Regards, Ravi