From: Zhigang Wang <zhigang.x.wang@oracle.com>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: Suggestion for merging xl save/restore/migrate/migrate-receive
Date: Mon, 16 Sep 2013 13:21:13 -0400 [thread overview]
Message-ID: <52373E09.1090404@oracle.com> (raw)
In-Reply-To: <5237346A.3020106@eu.citrix.com>
On 09/16/2013 12:40 PM, George Dunlap wrote:
> On 16/09/13 17:20, Ian Jackson wrote:
>> Zhigang Wang writes ("Re: [Xen-devel] Suggestion for merging xl save/restore/migrate/migrate-receive"):
>>> ---- xl-migrate.rst ----
>> ...
>>> * Current xl migrate command is not intuitive, especially the `-s` option::
>>>
>>> # xl migrate
>>> Usage: xl [-v] migrate [options] <Domain> <host>
>>>
>>> Save a domain state to restore later.
>>>
>>> Options:
>>>
>>> -h Print this help.
>>> -C <config> Send <config> instead of config file from creation.
>>> -s <sshcommand> Use <sshcommand> instead of ssh. String will be passed
>>> to sh. If empty, run <host> instead of ssh <host> xl
>>> migrate-receive [-d -e]
>>> -e Do not wait in the background (on <host>) for the death
>>> of the domain.
>>>
>>> It's a little hard to adapt other tools as transport.
>> Perhaps the documentation needs to be improved. But you can just say
>> xl migrate -s '' 42 'nc remotehost 1234'
>
> Actually, that's a pretty bizarre interface -- I don't think I would
> have gotten that from the help.
>
> If we had a new "transport" option that could take format strings, we
> could even set the default transport in xl.conf, like so:
>
> migrate.default.transport="myssh %h %r"
>
> migrate.default.transport="nc %h 1234"
>
> migrate.default.transport="socat - OPENSSL:%h:8005,verify=0"
>
> (Where %h would be the remote host, and %r the remote command to execute
> -- i.e., xl recieve.)
>
> Or of course:
>
> xl migrate -t "nc %h 1234" 42 remotehost
>
> Zhigang, would that work better for you guys?
Yes. I think it's a improvement to the -s option anyways.
I was thinking the same thing when I work on the example. With this, the
example doesn't need the customized command any more
(xl-migrate-command/xl-ssl-migrate-command).
(But haven't decided how to do the migration yet; the socat just a
example)
Thanks,
Zhigang
next prev parent reply other threads:[~2013-09-16 17:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 16:04 Suggestion for merging xl save/restore/migrate/migrate-receive Zhigang Wang
2013-09-16 10:04 ` George Dunlap
2013-09-16 15:51 ` Zhigang Wang
2013-09-16 16:05 ` George Dunlap
2013-09-16 16:07 ` George Dunlap
2013-09-16 16:20 ` Ian Jackson
2013-09-16 16:40 ` George Dunlap
2013-09-16 17:06 ` Ian Jackson
2013-09-16 17:21 ` Zhigang Wang [this message]
2013-09-16 17:41 ` Zhigang Wang
2013-09-16 20:42 ` Ian Campbell
2013-09-16 20:51 ` Zhigang Wang
2013-09-17 8:25 ` George Dunlap
2013-09-17 9:26 ` Ian Jackson
2013-09-17 10:07 ` George Dunlap
2013-09-17 13:44 ` Zhigang Wang
2013-09-24 16:46 ` Konrad Rzeszutek Wilk
2013-09-25 10:06 ` George Dunlap
2013-10-03 2:19 ` Matt Wilson
2013-10-03 13:34 ` Zhigang Wang
2013-09-17 10:28 ` George Dunlap
2013-09-17 10:45 ` Processed: " xen
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=52373E09.1090404@oracle.com \
--to=zhigang.x.wang@oracle.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).