create !
title it xl improve support for migration over non-sshlike tunnels
thanks
On Wed, 2013-09-04 at 16:43 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [Xen-devel] xend deprecation"):
> > > On Wed, Sep 4, 2013 at 3:04 PM, Konrad Rzeszutek Wilk
> > > <konrad.wilk@oracle.com> wrote:
> > > > - xl uses SSH for migration. We need SSL daemon or socat like xend has.
> >
> > You can provide any tool you like to run instead of ssh, including an
> > ssl daemon/client or socat. See the manpage.
>
> If there is some migration mode that you'd like to see natively
> supported in xl, besides "fork this program which looks a bit like
> ssh", we'd be very happy to take patches or even write them.
Indeed.
Konrad, what is the exact requirement here? You mention socat which just
takes an IP address and connects to it and pipes stuff back and forth
(crypto optional). I suspect the sending side of that can be done with a
thin wrapper which provides the 'ssh like' command line interface, so
what is needed is a daemon listening on a known port which can fork +
exec xl migrate-receive for each connection?
Is socat actually what you want or was that just an example?
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Ian Campbell writes ("Re: [Xen-devel] xend deprecation"):
> create !
> title it xl improve support for migration over non-sshlike tunnels
> thanks
...
> Konrad, what is the exact requirement here? You mention socat which just
> takes an IP address and connects to it and pipes stuff back and forth
> (crypto optional). I suspect the sending side of that can be done with a
> thin wrapper which provides the 'ssh like' command line interface,
I think it can be done with the existing xl interface, TBH, but it's
probably ugly. I would have no problem with an option which made xl
make the network connection itself.
> so
> what is needed is a daemon listening on a known port which can fork +
> exec xl migrate-receive for each connection?
I think this should be doable by running xl migrate-receive out of
inetd, or some kind of socket-activation-based feature of an
init-replacement (eg upstart).
If not this should be fixed.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel