[ovs-dev] [PATCH] ovn: Remove complete to-do items.

[Ben Pfaff]

On Wed, Apr 22, 2015 at 12:33:20PM -0400, Russell Bryant wrote:
> On 04/22/2015 10:52 AM, Ben Pfaff wrote:
> > Reported-by: Justin Pettit <jpettit at nicira.com>
> > Signed-off-by: Ben Pfaff <blp at nicira.com>
> 
> Acked-by: Russell Bryant <rbryant at redhat.com>

Thanks for the review.

> > @@ -120,29 +101,6 @@
> >  
> >  * ovn-northd
> >  
> > -** Monitor OVN_Northbound database, trigger Pipeline recomputation on change.
> > -
> > -** Translate each OVN_Northbound entity into Pipeline logical datapath flows.
> > -
> > -   We have to first sit down and figure out what the general
> > -   translation of each entity is.  The original OVN architecture
> > -   description at
> > -   http://openvswitch.org/pipermail/dev/2015-January/050380.html had
> > -   some sketches of these, but they need to be completed and
> > -   elaborated.
> > -
> > -   Initially, the simplest way to do this is probably to write
> > -   straight C code to do a full translation of the entire
> > -   OVN_Northbound database into the format for the Pipeline table in
> > -   the OVN Southbound database.  As scale increases, this will probably
> > -   be too inefficient since a small change in OVN_Northbound requires a
> > -   full recomputation.  At that point, we probably want to adopt a more
> > -   systematic approach, such as something akin to the "nlog" system used
> > -   in NVP (see Koponen et al. "Network Virtualization in Multi-tenant
> > -   Datacenters", NSDI 2014).
> > -
> > -** Push logical datapath flows to Pipeline table.
> > -
> >  ** Monitor OVN Southbound database Bindings table.
> >  
> >     Sync rows in the OVN Bindings table to the "up" column in the
> 
> This last one is done, too.

Thanks for pointing that out, I'll remove that too.

I'll apply this in a minute.