All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mike D. Day" <ncmike@us.ibm.com>
To: Stefan Berger <stefanb@us.ibm.com>
Cc: "Cihula, Joseph" <joseph.cihula@intel.com>,
	xen-devel@lists.xensource.com, Ronald Perez <ronpz@us.ibm.com>,
	"Scarlata, Vincent R" <vincent.r.scarlata@intel.com>
Subject: Re: A migration framework for external devices
Date: Wed, 08 Feb 2006 17:32:07 -0500	[thread overview]
Message-ID: <43EA7167.7000208@us.ibm.com> (raw)
In-Reply-To: <OFC42F5114.F06CB1CD-ON8525710F.00760BD4-8525710F.0076294D@us.ibm.com>

Stefan Berger wrote:
>>>  To be a bit clearer on the idea of the framework: It would consist of 
> a 
>>> deamon running on the target machine whose different plug-ins know how 
> to 
>>> handle the migration of different pieces of state information and know 
> how 
>>> to de-serialize them (which mere 'scp' would not do).
>> So an underlying assumption would be that the local and remove real or
>> virtual devices support serialize/deserialize of state, correct?
> 
> Yes, that's correct.

Would also  be very cool if the framework had pre-migration hooks. For 
example, allow someone to write a plugin to verify that the target host 
is qualified and in a good state to accept a migration  before it 
actually starts.

Also, some physical devices may need to be configured/re-configured on 
the target prior to a migration (infiniband, fiber channel, iscsi) and 
it would be good to have plugins for that as well.

Mike

  reply	other threads:[~2006-02-08 22:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-08 20:16 A migration framework for external devices Stefan Berger
2006-02-08 21:28 ` Muli Ben-Yehuda
2006-02-08 21:30   ` Stefan Berger
2006-02-08 22:32     ` Mike D. Day [this message]
2006-02-08 22:40       ` Stefan Berger
2006-02-09 12:34         ` Mike D. Day
2006-02-09 15:01           ` Daniel Veillard
2006-02-09 16:10             ` Mike D. Day
2006-02-13 10:18               ` Daniel Veillard
2006-02-09 16:20           ` Stefan Berger
2006-02-09 16:37             ` Mike D. Day
2006-02-09 15:05 ` Anthony Liguori
2006-02-09 16:52   ` Stefan Berger
2006-02-09 17:05     ` Anthony Liguori
2006-02-09 17:51       ` Stefan Berger
2006-02-09 18:35       ` Mike D. Day
2006-02-09 18:45         ` Anthony Liguori
2006-02-09 18:58           ` Mike D. Day

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43EA7167.7000208@us.ibm.com \
    --to=ncmike@us.ibm.com \
    --cc=joseph.cihula@intel.com \
    --cc=ronpz@us.ibm.com \
    --cc=stefanb@us.ibm.com \
    --cc=vincent.r.scarlata@intel.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.