Re: [ovs-discuss] [OVN] Aging mechanism for MAC_Binding table

2019-08-22 Thread Dumitru Ceara
On Wed, Aug 21, 2019 at 6:47 PM Ben Pfaff wrote: > > On Tue, Aug 20, 2019 at 06:11:12PM -0700, Han Zhou wrote: > > On Tue, Aug 20, 2019 at 4:57 PM Ben Pfaff wrote: > > > > > > Let me see if I'm following this correctly. This is what currently > > > happens: > > > > > > - HV1 needs a MAC address

Re: [ovs-discuss] [OVN] Aging mechanism for MAC_Binding table

2019-08-21 Thread Ben Pfaff
On Tue, Aug 20, 2019 at 06:11:12PM -0700, Han Zhou wrote: > On Tue, Aug 20, 2019 at 4:57 PM Ben Pfaff wrote: > > > > Let me see if I'm following this correctly. This is what currently > > happens: > > > > - HV1 needs a MAC address for an IP so it broadcasts an ARP request. > > > > - The port

Re: [ovs-discuss] [OVN] Aging mechanism for MAC_Binding table

2019-08-21 Thread Daniel Alvarez Sanchez
On Wed, Aug 21, 2019 at 3:11 AM Han Zhou wrote: > > > > On Tue, Aug 20, 2019 at 4:57 PM Ben Pfaff wrote: > > > > Let me see if I'm following this correctly. This is what currently > > happens: > > > > - HV1 needs a MAC address for an IP so it broadcasts an ARP request. > > > > - The port with

Re: [ovs-discuss] [OVN] Aging mechanism for MAC_Binding table

2019-08-20 Thread Han Zhou
On Tue, Aug 20, 2019 at 4:57 PM Ben Pfaff wrote: > > Let me see if I'm following this correctly. This is what currently > happens: > > - HV1 needs a MAC address for an IP so it broadcasts an ARP request. > > - The port with the IP address, on HV2, causes the MAC_Binding to be > inserted. > > -

Re: [ovs-discuss] [OVN] Aging mechanism for MAC_Binding table

2019-08-20 Thread Ben Pfaff
Let me see if I'm following this correctly. This is what currently happens: - HV1 needs a MAC address for an IP so it broadcasts an ARP request. - The port with the IP address, on HV2, causes the MAC_Binding to be inserted. - Every ovn-controller inserts an OF flow for the binding. HV1 and

Re: [ovs-discuss] [OVN] Aging mechanism for MAC_Binding table

2019-08-20 Thread Daniel Alvarez Sanchez
Hi folks, Reviving this thread as we're seeing this more and more problematic. Combining the ideas mentioned up thread, Dumitru, Numan, Lucas and I had some internal discussion where we came up with a possible approach and we'd love to get feedback from you: - Local ovn-controller will always

Re: [ovs-discuss] [OVN] Aging mechanism for MAC_Binding table

2019-07-08 Thread Ben Pfaff
On Mon, Jul 08, 2019 at 06:19:23PM -0700, Han Zhou wrote: > On Thu, Jun 27, 2019 at 6:44 AM Ben Pfaff wrote: > > > > On Tue, Jun 25, 2019 at 01:05:21PM +0200, Daniel Alvarez Sanchez wrote: > > > Lately we've been trying to solve certain issues related to stale > > > entries in the MAC_Binding

Re: [ovs-discuss] [OVN] Aging mechanism for MAC_Binding table

2019-07-08 Thread Han Zhou
On Thu, Jun 27, 2019 at 6:44 AM Ben Pfaff wrote: > > On Tue, Jun 25, 2019 at 01:05:21PM +0200, Daniel Alvarez Sanchez wrote: > > Lately we've been trying to solve certain issues related to stale > > entries in the MAC_Binding table (e.g. [0]). On the other hand, for > > the OpenStack + Octavia

Re: [ovs-discuss] [OVN] Aging mechanism for MAC_Binding table

2019-06-27 Thread Ben Pfaff
On Tue, Jun 25, 2019 at 01:05:21PM +0200, Daniel Alvarez Sanchez wrote: > Lately we've been trying to solve certain issues related to stale > entries in the MAC_Binding table (e.g. [0]). On the other hand, for > the OpenStack + Octavia (Load Balancing service) use case, we see that > a reused VIP

[ovs-discuss] [OVN] Aging mechanism for MAC_Binding table

2019-06-25 Thread Daniel Alvarez Sanchez
Hi folks, Lately we've been trying to solve certain issues related to stale entries in the MAC_Binding table (e.g. [0]). On the other hand, for the OpenStack + Octavia (Load Balancing service) use case, we see that a reused VIP can be as well affected by stale entries in this table due to the