From: Ian Campbell <Ian.Campbell@citrix.com>
To: Florian Heigl <florian.heigl@gmail.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Fwd: Examples for using xl migrate -s ?
Date: Mon, 31 Oct 2011 09:30:41 +0000 [thread overview]
Message-ID: <1320053441.23193.14.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <CAFivhP=niHCDz_xsgdwTJxCd=8CU4sKA_v_TAh53WQPHSGF3gA@mail.gmail.com>
On Sat, 2011-10-29 at 20:38 +0100, Florian Heigl wrote:
> Hi,
>
> 2011/10/28 Ian Campbell <Ian.Campbell@citrix.com>:
> >> 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. :>
As part of the documentation day last week Stefano Stabellini posted a
manpage for xl which no doubt contains a few words on this subject.
Please could you have a look in the archives and see if what is written
there would have helped.
> > 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.
I think that could work, yes.
> 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!
:-)
Ian.
prev parent reply other threads:[~2011-10-31 9:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFivhPmT1mfzaQbPDviB4jMAUBe5u-cruXtDz7U2Jh7jWrPCcQ@mail.gmail.com>
2011-10-27 20:47 ` Fwd: Examples for using xl migrate -s ? Florian Heigl
2011-10-28 9:55 ` Ian Campbell
2011-10-29 19:38 ` Florian Heigl
2011-10-31 9:30 ` Ian Campbell [this message]
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=1320053441.23193.14.camel@zakaz.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=florian.heigl@gmail.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.