[ovs-dev] [PATCH v2 2/2] [RFC] ovn: Start work on design documentation.

Ben Pfaff blp at nicira.com
Fri Feb 20 01:06:55 UTC 2015


On Thu, Feb 19, 2015 at 11:52:51PM +0100, Thomas Graf wrote:
> On 02/19/15 at 02:36pm, Ben Pfaff wrote:
> > I thought about this a bit when I was working on the OVN database
> > schema, but I didn't bother to write it up.  Here's an incremental
> > diff against the OVN schema.  The first hunk is for the Chassis table,
> > the second for the Bindings table.  The Pipeline table doesn't need
> > special handling because ovs-nbd is fully in charge of it:
> 
> Looks great. Eventually this cleanup process could also take care
> of removing stale OVSDB ports after a reboot.

I tend to prefer the model where OVSDB is reconstructed essentially
from an empty DB at boot.  That's what happens on e.g. XenServer.  Is
the more long-term model used widely?



More information about the dev mailing list