[ovs-dev] [PATCH v2] ovn-controller: Fix match crieria for dynamic mac binding flows

2016-09-08 Thread Chandra S Vejendla
match struct is not initialized before adding flows for each entry in mac_bindings table. This results in incorrect match criteria. Signed-off-by: Chandra Sekhar Vejendla Signed-off-by: Ryan Moats Co-authored-by: Ryan Moats --- ovn/controller/lflow.c | 31 ++- 1 fil

[ovs-dev] [PATCH] ovn-controller: Fix match crieria for dynamic mac binding flows

2016-09-02 Thread Chandra S Vejendla
match struct is not initialized before adding flows for each entry in mac_bindings table. This results in incorrect match criteria. Signed-off-by: Chandra Sekhar Vejendla Signed-off-by: Ryan Moats Co-authored-by: Ryan Moats --- ovn/controller/lflow.c | 4 ++-- 1 file changed, 2 insertions(+),

[ovs-dev] [PATCH v2] ovn: Delete stale MAC_Bindings that result in Referential Integrity Violation

2016-08-25 Thread Chandra S Vejendla
The MAC_Bindings have a strong reference to the Datapath_Binding. However the MAC_Bindings are never deleted anywhere, and when the Datapath (associated with a MAC_Binding) is deleted, the ovsdb-server returns Referential Integrity Violation. This prevents newer operations initiated from the CMS fr

[ovs-dev] [PATCH] ovn: Delete stale MAC_Bindings that result in Referential Integrity Violation

2016-08-24 Thread Chandra S Vejendla
The MAC_Bindings have a strong reference to the Datapath_Binding. However the MAC_Bindings are never deleted anywhere, and when the Datapath (associated with a MAC_Binding) is deleted, the ovsdb-server returns Referential Integrity Violation. This prevents newer operations initiated from the CMS fr

[ovs-dev] [PATCH v2] ovn: Delete stale MAC_Binding records

2016-08-16 Thread Chandra S Vejendla
Entries in MAC_Binding table are not deleted when the logical_ports referred to in MAC_Bindings are deleted. The patch fixes this by deleting the MAC_Binding entry when the logical_port is not found. Signed-off-by: Chandra Sekhar Vejendla --- ovn/controller/lflow.c | 25 +

[ovs-dev] [PATCH v6] ovn: Support for GARP for NAT IPs via localnet

2016-08-16 Thread Chandra S Vejendla
In cases where a DNAT IP is moved to a new router or the SNAT IP is reused with a new mac address, the NAT IPs become unreachable because the external switches/routers have stale ARP entries. This commit aims to fix the problem by sending GARPs for NAT IPs via locanet. There are two parts to this p

[ovs-dev] [PATCH] ovn: Delete stale MAC_Binding records

2016-08-16 Thread Chandra S Vejendla
Entries in MAC_Binding table are not deleted when the logical_ports referred to in MAC_Bindings are deleted. The patch fixes this by deleting the MAC_Binding entry when the logical_port is not found. Signed-off-by: Chandra Sekhar Vejendla --- ovn/controller/lflow.c | 24

[ovs-dev] [PATCH] ovn: Fix ARP request flow for unknown IP in lrouter

2016-08-16 Thread Chandra S Vejendla
TPA in arp requests generated for unknown MAC-to-IP bindings is currently set to DST_IP of the original packet. These arps will not be resolved when the DST_IP is rechable via the default gateway. This patch fixes the issue by setting the TPA to reg0. In routing stage reg0 is set to IP of the defau

[ovs-dev] [PATCH v5] ovn: Support for GARP for NAT IPs via localnet

2016-08-15 Thread Chandra S Vejendla
In cases where a DNAT IP is moved to a new router or the SNAT IP is reused with a new mac address, the NAT IPs become unreachable because the external switches/routers have stale ARP entries. This commit aims to fix the problem by sending GARPs for NAT IPs via locanet A new options key "nat-addres

[ovs-dev] [PATCH v4] ovn: Support for GARP for NAT IPs via localnet

2016-08-12 Thread Chandra S Vejendla
In cases where a DNAT IP is moved to a new router or the SNAT IP is reused with a new mac address, the NAT IPs become unreachable because the external switches/routers have stale ARP entries. This commit aims to fix the problem by sending GARPs for NAT IPs via locanet A new options key "nat-addres

[ovs-dev] [PATCH v3] ovn: Support for GARP for NAT IPs via localnet

2016-07-29 Thread Chandra S Vejendla
In cases where a DNAT IP is moved to a new router or the SNAT IP is reused with a new mac address, the NAT IPs become unreachable because the external switches/routers have stale ARP entries. This commit aims to fix the problem by sending GARPs for NAT IPs via locanet A new options key "nat-addres

[ovs-dev] [PATCH v2] ovn: Support for GARP for NAT IPs via localnet

2016-07-27 Thread Chandra S Vejendla
In cases where a DNAT IP is moved to a new router or the SNAT IP is reused with a new mac address, the NAT IPs become unreachable because the external switches/routers have stale ARP entries. This commit aims to fix the problem by sending GARPs for NAT IPs via locanet A new options key "nat-addres

[ovs-dev] [PATCH] ovn: Support for GARP for NAT IPs via localnet

2016-07-26 Thread Chandra S Vejendla
In cases where a DNAT IP is moved to a new router or the SNAT IP is reused with a new mac address, the NAT IPs become unreachable because the external switches/routers have stale ARP entries. This commit aims to fix the problem by sending GARPs for NAT IPs via locanet A new options key "nat-addres

[ovs-dev] [PATCH v3] ovn: Allow SNAT traffic destined to router ip

2016-07-18 Thread Chandra S Vejendla
When router ip is used as SNAT IP, traffic destined to router ip should not be dropped Fixes: 4685e523695c ("ovn: Support multiple addresses on a single logical router port.") Signed-off-by: Chandra Sekhar Vejendla --- ovn/northd/ovn-northd.c | 7 ++- 1 file changed, 6 insertions(+), 1 delet

[ovs-dev] [PATCH] ovn: Add datapth of gateway port to local_datapaths

2016-07-18 Thread Chandra S Vejendla
When a l3 gateway port is created on a chassis, the corresponding datapath is not added to local datapths. This results in patch ports not getting created between local network and br-int Signed-off-by: Chandra Sekhar Vejendla --- ovn/controller/binding.c | 8 1 file changed, 8 insertio

[ovs-dev] [PATCH, v2] ovn: Allow SNAT traffic destined to router ip

2016-07-18 Thread Chandra S Vejendla
When router ip is used as SNAT IP, traffic destined to router ip should not be dropped --- ovn/northd/ovn-northd.c | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/ovn/northd/ovn-northd.c b/ovn/northd/ovn-northd.c index 7ce509d..78c3a7d 100644 --- a/ovn/northd/ovn-northd.c

[ovs-dev] [PATCH] ovn: Allow SNAT traffic destined to router ip when router

2016-07-18 Thread Chandra S Vejendla
Signed-off-by: Chandra Sekhar Vejendla --- ovn/northd/ovn-northd.c | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/ovn/northd/ovn-northd.c b/ovn/northd/ovn-northd.c index 7ce509d..78c3a7d 100644 --- a/ovn/northd/ovn-northd.c +++ b/ovn/northd/ovn-northd.c @@ -2399,11 +239

[ovs-dev] [PATCH v3] OVN: Fix ARP request flow in router ingress table

2016-07-07 Thread Chandra S Vejendla
TPA in arp requests generated for unknown MAC-to-IP bindings is currently set to DST_IP of the original packet. These arps will not be resolved when the DST_IP is rechable via the default gateway. This patch fixes the issue by setting the TPA to reg0. In routing stage reg0 is set to IP of the defau

[ovs-dev] [PATCH v2] OVN: Fix ARP request flow in router ingress table

2016-07-07 Thread Chandra S Vejendla
TPA in arp requests generated for unknown MAC-to-IP bindings is currently set to DST_IP of the original packet. These arps will not be resolved when the DST_IP is rechable via the default gateway. This patch fixes the issue by setting the TPA to reg0. In routing stage reg0 is set to IP of the defau

[ovs-dev] [PATCH] OVN: Fix ARP request flow in router ingress table

2016-07-04 Thread Chandra S Vejendla
TPA in arp requests generated for unknown MAC-to-IP bindings is currently set to DST_IP of the original packet. These arps will not be resolved when the DST_IP is rechable via the default gateway. This patch fixes the issue by setting the TPA to reg0. In routing stage reg0 is set to IP of the defau

[ovs-dev] [PATCH] ovn: Allow IP packets destined to router ip for SNAT

2016-06-21 Thread Chandra S Vejendla
By default all the ip traffic destined to router ip is dropped in lr_in_ip_input stage. When the router ip is used as snat ip, allow reverse snat traffic destined to the router ip. Signed-off-by: Chandra Sekhar Vejendla --- ovn/northd/ovn-northd.c | 33 - 1 file c

[ovs-dev] [PATCH RFC] OVN: Openstack floating ip support

2016-03-22 Thread Chandra S Vejendla
This patch adds distributed floating ip support for ovn. The assumption made here is that the external network is a single L2 broadcast domain and all the chassis have connectivity to the external network. 2 new tables are added in the LROUTER pipeline IN_IP_DNAT & IP_IN_SNAT. IN_IP_DNAT will modi