Thanks, applied to master.
On Sun, Feb 07, 2016 at 06:29:32AM +, Ofer Ben-Yacov wrote:
> It does.
>
> Thanks,
> Ofer.
>
> בתאריך יום ו׳, 5 בפבר׳ 2016 ב-22:57 מאת Ben Pfaff <b...@ovn.org>:
>
> > On Thu, Feb 04, 2016 at 09:49:35AM +, Ofer Ben-Yacov wrote:
> > > The tunnel key in d
It does.
Thanks,
Ofer.
בתאריך יום ו׳, 5 בפבר׳ 2016 ב-22:57 מאת Ben Pfaff <b...@ovn.org>:
> On Thu, Feb 04, 2016 at 09:49:35AM +, Ofer Ben-Yacov wrote:
> > The tunnel key in decoupled from the actual implementation of the tunnel.
> > The only tunnel protocol that is currently supporte
On Thu, Feb 04, 2016 at 09:49:35AM +, Ofer Ben-Yacov wrote:
> The tunnel key in decoupled from the actual implementation of the tunnel.
> The only tunnel protocol that is currently supported in this schema is
> VxLAN. (the encapsulation is set by enum with single value:
> vxlan_over_ipv4 ). Th
The tunnel key in decoupled from the actual implementation of the tunnel.
The only tunnel protocol that is currently supported in this schema is
VxLAN. (the encapsulation is set by enum with single value:
vxlan_over_ipv4 ). This is fine and the new key field can be used to set
the VIN of the VxLAN
On Tue, Dec 29, 2015 at 02:36:56PM +0200, Ofer Ben Yacov wrote:
> Add tunnel key to Physical_Locator to support different
> tunnel ID on different locators on the same logical switch.
This doesn't define any encapsulation that makes use of the new feature.
This needs to also update the schema v
Add tunnel key to Physical_Locator to support different
tunnel ID on different locators on the same logical switch.
---
vtep/vtep.ovsschema | 7 ---
vtep/vtep.xml | 22 --
2 files changed, 16 insertions(+), 13 deletions(-)
diff --git a/vtep/vtep.ovsschema b/vtep
