[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[libvirt] [PATCH 0/3] Transport network port data during live migration



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>

----
- V3 of this patch series fixes issues found by Laine during review around
  making the XML more generic.
- V2 of this patch series fixes some issues found when migrating VMs on
  standard Linux bridges.

Kyle Mestery (3):
  Add the ability for the Qemu V3 migration protocol to include    
    transporting network configuration. A generic framework is proposed
        with this patch to allow for the transfer of opaque data.
  Add utility functions for Open vSwitch to both save     per-port data
    before a live migration, and restore the     per-port data after a
    live migration.
  Transport Open vSwitch per-port data during live     migration by
    using the utility functions    
    virNetDevOpenvswitchGetMigrateData() and    
    virNetDevOpenvswitchSetMigrateData().

 src/libvirt_private.syms        |   2 +
 src/qemu/qemu_migration.c       | 293 +++++++++++++++++++++++++++++++++++++++-
 src/util/virnetdevopenvswitch.c |  70 ++++++++++
 src/util/virnetdevopenvswitch.h |   6 +
 4 files changed, 369 insertions(+), 2 deletions(-)

-- 
1.7.11.4


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]