"dev" <dev-boun...@openvswitch.org> wrote on 03/24/2016 03:29:28 PM:

> From: Ben Pfaff <b...@ovn.org>
> To: Hui Kang <hkang.sun...@gmail.com>
> Cc: dev@openvswitch.org
> Date: 03/24/2016 03:29 PM
> Subject: Re: [ovs-dev] [PATCH] ovn-architecture.7.xml: Clarify the
> definition of Binding table
> Sent by: "dev" <dev-boun...@openvswitch.org>
>
> On Thu, Mar 24, 2016 at 02:50:47PM -0400, Hui Kang wrote:
> > For the sake of clarity
> >
> > Signed-off-by: Hui Kang <ka...@us.ibm.com>
> > ---
> >  ovn/ovn-architecture.7.xml | 7 ++++---
> >  1 file changed, 4 insertions(+), 3 deletions(-)
> >
> > diff --git a/ovn/ovn-architecture.7.xml b/ovn/ovn-architecture.7.xml
> > index 13acaf5..a588a0e 100644
> > --- a/ovn/ovn-architecture.7.xml
> > +++ b/ovn/ovn-architecture.7.xml
> > @@ -353,9 +353,10 @@
> >        table to reflect the new port, e.g. add a flow to recognize
> that packets
> >        destined to the new port's MAC address should be delivered to
it, and
> >        update the flow that delivers broadcast and multicast
> packets to include
> > -      the new port.  It also creates a record in the
> <code>Binding</code> table
> > -      and populates all its columns except the column that identifies
the
> > -      <code>chassis</code>.
> > +      the new port.  It also creates a record in the Datapath_Binding,
> > +      Port_Binding, and MAC_Binding tables (hereafter,
<code>Binding</code>
> > +      table) of the Southbound database and populates all its
> columns except
> > +      the column that identifies the <code>chassis</code>.
>
> Now this doesn't make any sense at all.

Hi, Ben, from my understanding, as a new VIF with MAC address and flow are
added to
to the southbound database, these tables seem need to be updated. Is there
any
misunderstanding here? Thanks. - Hui


> _______________________________________________
> dev mailing list
> dev@openvswitch.org
> http://openvswitch.org/mailman/listinfo/dev
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Reply via email to