WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Fwd: Examples for using xl migrate -s ?

To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Subject: Re: [Xen-devel] Fwd: Examples for using xl migrate -s ?
From: Florian Heigl <florian.heigl@xxxxxxxxx>
Date: Sat, 29 Oct 2011 21:38:36 +0200
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sat, 29 Oct 2011 12:39:34 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=MvmuWd0INOkNUt/HrjoGjcUYnWoYbojpT8cdnMEJ1ww=; b=fZuhm0kqHIDAJdKnOlAccTeuTZKvh9wpbTwsqH3xGaZB8AdMm1oDyRUJfb9B5wCSUK iFPBuAxMc8glSdRdodW9Y6D/fqn6XSF+6XFQ5fPVfveYxpZRp1MpPyUkc1BHx0yPEjSM 8lzdg1iivvgT178v53C06xz1UcbWoS0/SwJKs=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1319795729.9436.209.camel@xxxxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <CAFivhPmT1mfzaQbPDviB4jMAUBe5u-cruXtDz7U2Jh7jWrPCcQ@xxxxxxxxxxxxxx> <CAFivhPniexii22twa+Cq+WPk2GUp5i=bKJZKpo4BH=ev1A3Jfg@xxxxxxxxxxxxxx> <1319795729.9436.209.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

2011/10/28 Ian Campbell <Ian.Campbell@xxxxxxxxxx>:
>> sorry to disturb, but are there any in-depth docs about migration in xl?
>
> Not that I know of, sorry.

usage as an exercise left to the user. :>

> Perhaps an option to xl migrate-receive to have it receive a single
> connection on a specified socket from a given source instead of
> expecting things on stdin would be a useful compromise? i.e. you should
> use ssh to execute that command "securely" then pipe the data to the
> unsecure socket?

I don't write network protocols ... I don't know which way of
connection setup would be best, but using ssh to securely initiate
things definitely makes sense.
On the other hand I don't like the initiator of (the migration)
something telling the receiver where to listen. That's like the NAT
traversal stuff in SIP.

Maybe, uh, something like:
ssh into migration target, saying hi, please spin up a receiver using
(stdin|network)
server says: receiver ready at (stdin|network ip+socket)
client sends to the correct destination.

The advantage would be that the server could have the final decision
about which interface to use, it might well be different from the
SSH-facing one.

> It's the Unix way, surely ;-)

Hehe, getting me from the Unix angle, I feel trapped!

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>