[ovs-dev] [PATCH] vtep: Update vtep schema with tunnel table

Bruce Davie bdavie at vmware.com
Wed May 7 18:24:43 UTC 2014


Ben,
 Thanks for the review. We have not yet tested any implementations of BFD on VTEPs, so I’m not too worried about backward compatibility. We discovered the need for this change to BFD in the schema when looking at how we would configure BFD tunnels terminating on several VTEPs managed  by a single HSC. I’ve reviewed Ashwin’s patch and believe it is a good design to address that issue.

Summary - I’m fine with this patch being applied.

Bruce

On May 7, 2014, at 11:17 AM, Ben Pfaff <blp at nicira.com> wrote:

> On Tue, May 06, 2014 at 02:54:52PM -0700, Ashwin Swaminathan wrote:
>> Added a Tunnel table to the VTEP schema that allows
>> per-tunnel BFD configuration and status to be specified.
>> Removed the BFD configuration/status from the
>> Physical_Locator table.
>> 
>> Signed-off-by: Ashwin Swaminathan <ashwinds at arista.com>
> 
> This is a non backward compatible change, so it could cause problems
> for vendors who implemented the previous schema.  I don't have
> information on how many vendors that affects, in practice (none, I
> hope).
> 
> Adding Bruce, who might better know the implications.  Bruce, can you
> tell us anything?
> 
> Thanks,
> 
> Ben.




More information about the dev mailing list