From: Paolo Bonzini <pbonzini@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>,
Kevin Wolf <kwolf@redhat.com>
Cc: Ashish Mittal <ashmit602@gmail.com>,
qemu-devel@nongnu.org, armbru@redhat.com,
ashish.mittal@veritas.com, stefanha@gmail.com,
Ketan.Nilangekar@veritas.com, Abhijit.Dey@veritas.com
Subject: Re: [Qemu-devel] [PATCH v3 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support
Date: Wed, 17 Aug 2016 13:20:55 +0200 [thread overview]
Message-ID: <a14aba66-01a6-5fe8-2a15-070770deb94d@redhat.com> (raw)
In-Reply-To: <20160815105457.GD13261@redhat.com>
On 15/08/2016 12:54, Daniel P. Berrange wrote:
> I think the dot-separated qapi syntax is actually more user friendly as
> looking at it, it is obvious what each component does. The URI syntax is
> inherantly limited, so if you start with that syntax and then want to
> support > 1 server, you have to completely change to the qapi syntax anyway.
If I understand correctly, this already supports >1 data server, the URI
is to some kind of metadata server that is used only at startup.
Paolo
next prev parent reply other threads:[~2016-08-17 11:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-14 4:35 [Qemu-devel] [PATCH v3 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support Ashish Mittal
2016-08-14 4:41 ` no-reply
2016-08-14 4:43 ` no-reply
2016-08-15 10:20 ` Daniel P. Berrange
2016-08-15 10:47 ` Kevin Wolf
2016-08-15 10:54 ` Daniel P. Berrange
2016-08-17 11:20 ` Paolo Bonzini [this message]
2016-08-23 23:28 ` ashish mittal
2016-08-15 16:29 ` ashish mittal
2016-08-17 11:22 ` Paolo Bonzini
2016-08-17 21:58 ` ashish mittal
2016-08-20 18:42 ` ashish mittal
2016-08-23 21:58 ` Stefan Hajnoczi
2016-08-23 22:22 ` ashish mittal
2016-11-15 19:02 ` ashish mittal
2016-11-15 20:48 ` Stefan Hajnoczi
2016-11-15 20:51 ` ashish mittal
2017-02-07 23:20 ` ashish mittal
2016-08-23 22:57 ` ashish mittal
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=a14aba66-01a6-5fe8-2a15-070770deb94d@redhat.com \
--to=pbonzini@redhat.com \
--cc=Abhijit.Dey@veritas.com \
--cc=Ketan.Nilangekar@veritas.com \
--cc=armbru@redhat.com \
--cc=ashish.mittal@veritas.com \
--cc=ashmit602@gmail.com \
--cc=berrange@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).