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

[libvirt] [PATCHv4 0/3] Transport Open vSwitch per-port data during live migration



This is an update of Kyle Mestery's patch series v3 by the same name:

  https://www.redhat.com/archives/libvir-list/2012-October/msg00014.html

I've updated it according to the comments in the review of patch 1/3
of that series:

  https://www.redhat.com/archives/libvir-list/2012-October/msg01224.html

It now needs a counter-review from Kyle, along with verification that
it actually works (since I don't have the proper setup to test it
handy).

******************************************
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.

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().


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