On 02/19/15 at 02:36pm, Ben Pfaff wrote: > On Thu, Feb 19, 2015 at 10:20:13PM +0100, Thomas Graf wrote: > > Is this piece CMS specific as well or can we leverage libvirt to > > create some abstraction here and write the vif-id into OVSDB? > > I believe that libvirt already does this; see > virNetDevOpenvswitchAddPort() in src/util/virnetdevopenvswitch.c. > (I'm looking at libvirt-0.9.12.3 with Debian patches applied, though I > doubt it matters.)
Perfect ;-) > 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. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
