From: "Mike D. Day" <ncmike@us.ibm.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: "Cihula, Joseph" <joseph.cihula@intel.com>,
xen-devel@lists.xensource.com, Stefan Berger <stefanb@us.ibm.com>,
"Scarlata, Vincent R" <vincent.r.scarlata@intel.com>,
Ronald Perez <ronpz@us.ibm.com>
Subject: Re: A migration framework for external devices
Date: Thu, 09 Feb 2006 13:35:53 -0500 [thread overview]
Message-ID: <43EB8B89.80909@us.ibm.com> (raw)
In-Reply-To: <43EB766A.30701@us.ibm.com>
Anthony Liguori wrote:
> all). It also allows you to do clever things like vary the port which
> should add to the security of migration.
Allowing the target to choose the port is good practice but not added
security.
> Why do plugins have to exist? The only reason to have a plugin
> mechanism is to be able to maintain plugins outside of the Xend tree
> which would require a stable plugin interface. I don't think we're at a
> point where we can do that.
No, you are missing an important point. The plugin mechanism is
necessary to isolate specialized device migration code from
general-purpose migration code. I don't think it has anything to do with
where the plugins are maintained.
> This all sounds like it's going to add complexity. The tools are
> already far too complex.
I think the complexity is already there in the usage scenarios. So this
is not adding complexity. Rather it is dealing with complexity that
exists. Right now the tools ignore most of the complex scenarios.
Mike
next prev parent reply other threads:[~2006-02-09 18:35 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
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 [this message]
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=43EB8B89.80909@us.ibm.com \
--to=ncmike@us.ibm.com \
--cc=aliguori@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.