On Sep 28, 2012, at 11:42 AM, Daniel P. Berrange wrote: > On Fri, Sep 21, 2012 at 05:16:45PM -0400, Kyle Mestery wrote: >> This series of commits has the end goal of allowing per-port data stored >> in the Open vSwitch DB to be transported during live migration. This is >> done by first providing a generic infrastructure for transporting network >> data, adding some utility functions specific to Open vSwitch, and hooking >> the two together. >> >> The framework provided is generic in that other networking data could be >> transferred as well by simply adding in additional hooks as needed. >> >> An example of the XML being transported is shown here: >> >> <network> >> <interface index='1' vporttype='openvswitch' netdata='blah blah blah'/> >> <interface index='7' vporttype='openvswitch' netdata='blah blah blah'/> >> </network> > > Could you give an example of what goes in the netdata='blah blah blah' > part of the XML ? I'm interesting in seeing the type of data, and its > indicitive size > > > Daniel Hi Daniel: >From a hypothetical angle: As an example, an OpenFlow controller may have certain information about the port, specific to this controller, which it may want to store with the port itself on the host. This especially true if an agent exists on the host which needs to read this data, update it, and use it to perform some tasks. It's convenient to have this data stored as close to the port itself, which in this case is the OVS DB, and having it transferred as part of the migration protocol is also very handy. Thanks, Kyle -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list