From: Eric Blake <eblake@redhat.com>
To: Jules Wang <junqing.wang@cs2c.com.cn>
Cc: pbonzini@redhat.com, quintela@redhat.com, qemu-devel@nongnu.org,
owasserm@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 2/4] Curling: cmdline interface.
Date: Mon, 30 Sep 2013 16:16:34 -0600 [thread overview]
Message-ID: <5249F842.8050405@redhat.com> (raw)
In-Reply-To: <1380485683-4626-3-git-send-email-junqing.wang@cs2c.com.cn>
[-- Attachment #1: Type: text/plain, Size: 2401 bytes --]
On 09/29/2013 02:14 PM, Jules Wang wrote:
> Add an option '-f' to migration cmdline.
> Indicating whether to enable fault tolerant or not.
>
> Signed-off-by: Jules Wang <junqing.wang@cs2c.com.cn>
> ---
> .help = "migrate to URI (using -d to not wait for completion)"
> "\n\t\t\t -b for migration without shared storage with"
> " full copy of disk\n\t\t\t -i for migration without "
> "shared storage with incremental copy of disk "
> - "(base image shared between src and destination)",
> + "(base image shared between src and destination)"
> + "\n\t\t\t -f for fault tolerant, this is another "
> + "feature rather than migrate",
That sounds awkward, and overly long. Maybe go with just:
-f for fault tolerance mode
and let the user then read the full documentation for what it entails.
> -@item migrate [-d] [-b] [-i] @var{uri}
> +@item migrate [-d] [-b] [-i] [-f] @var{uri}
> @findex migrate
> Migrate to @var{uri} (using -d to not wait for completion).
> -b for migration with full copy of disk
> -i for migration with incremental copy of disk (base image is shared)
> + -f for fault tolerant
Can -d and -f be used at the same time, or are they exclusive?
> +++ b/hmp.c
> @@ -1213,10 +1213,11 @@ void hmp_migrate(Monitor *mon, const QDict *qdict)
> int detach = qdict_get_try_bool(qdict, "detach", 0);
> int blk = qdict_get_try_bool(qdict, "blk", 0);
> int inc = qdict_get_try_bool(qdict, "inc", 0);
> + int ft = qdict_get_try_bool(qdict, "ft", 0);
Why two spaces?
> +++ b/qapi-schema.json
> @@ -2420,7 +2420,8 @@
> # Since: 0.14.0
> ##
> { 'command': 'migrate',
> - 'data': {'uri': 'str', '*blk': 'bool', '*inc': 'bool', '*detach': 'bool' } }
> + 'data': {'uri': 'str', '*blk': 'bool', '*inc': 'bool', '*detach': 'bool',
> + '*ft': 'bool' } }
Missing documentation, including mention that the new option was only
made available in 1.7. We still don't have introspection; is there some
other means by which libvirt and other management apps can tell whether
this feature is available? Furthermore, 'ft' is an awfully short name;
for QMP, we prefer to use full words where possible, such as
'fault-tolerant'.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-09-30 22:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-29 20:14 [Qemu-devel] [PATCH v2 0/4] Curling: KVM Fault Tolerance Jules Wang
2013-09-29 20:14 ` [Qemu-devel] [PATCH v2 1/4] Curling: add doc Jules Wang
2013-09-29 20:14 ` [Qemu-devel] [PATCH v2 2/4] Curling: cmdline interface Jules Wang
2013-09-30 22:16 ` Eric Blake [this message]
2013-10-09 6:49 ` junqing.wang
2013-10-09 12:02 ` Eric Blake
2013-10-10 2:52 ` Jules
2013-09-29 20:14 ` [Qemu-devel] [PATCH v2 3/4] Curling: the sender Jules Wang
2013-09-29 20:14 ` [Qemu-devel] [PATCH v2 4/4] Curling: the receiver Jules Wang
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=5249F842.8050405@redhat.com \
--to=eblake@redhat.com \
--cc=junqing.wang@cs2c.com.cn \
--cc=owasserm@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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 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).