| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] A migration framework for external devices
|
To: |
"Mike D. Day" <ncmike@xxxxxxxxxx> |
|
Subject: |
Re: [Xen-devel] A migration framework for external devices |
|
From: |
Daniel Veillard <veillard@xxxxxxxxxx> |
|
Date: |
Mon, 13 Feb 2006 05:18:39 -0500 |
|
Cc: |
"Cihula, Joseph" <joseph.cihula@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Stefan Berger <stefanb@xxxxxxxxxx>, "Scarlata, Vincent R" <vincent.r.scarlata@xxxxxxxxx>, Ronald Perez <ronpz@xxxxxxxxxx> |
|
Delivery-date: |
Mon, 13 Feb 2006 10:30:36 +0000 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<43EB6969.6020007@xxxxxxxxxx> |
|
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
|
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
|
List-post: |
<mailto:xen-devel@lists.xensource.com> |
|
List-subscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
|
List-unsubscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
|
References: |
<OFAF40C2ED.9A049C9A-ON8525710F.007C18EC-8525710F.007C8530@xxxxxxxxxx> <43EB36DB.7080302@xxxxxxxxxx> <20060209150127.GQ30975@xxxxxxxxxx> <43EB6969.6020007@xxxxxxxxxx> |
|
Reply-to: |
veillard@xxxxxxxxxx |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
User-agent: |
Mutt/1.4.1i |
On Thu, Feb 09, 2006 at 11:10:17AM -0500, Mike D. Day wrote:
> Daniel Veillard wrote:
> > So how do you plan to glue the XML and the other parts together ?
>
> One way is to have two channels (like ftp). Have an xml session channel
Urgh, way more complex, you start hitting synchronization problems
requiring more round trips etc ... Maybe the convenience still makes
sense though.
> and a tcp data channel. That gives the benefits of xml-rpc for
> triggering events and invoking plugins. You could use xml-rpc to
> negotiate the port for the migration data transfer, for example. Then
> use the data channel (scp/tcp) for the migration.
>
> I'm not convinced this approach is better than starting from scratch tho.
I can't tell :-) I was just raising a problem which could happen in
the proposal, I still have much to read/learn on the current state...
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
veillard@xxxxxxxxxx | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home