From: Stefan Hajnoczi <stefanha@gmail.com>
To: ashish mittal <ashmit602@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
qemu-devel@nongnu.org, kwolf@redhat.com, armbru@redhat.com,
Ashish Mittal <ashish.mittal@veritas.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: Tue, 23 Aug 2016 17:58:03 -0400 [thread overview]
Message-ID: <20160823215803.GA24259@stefanha-x1.localdomain> (raw)
In-Reply-To: <CAAo6VWNYwRO5BO-qmQdzsp0R981CcXEQOBdHGYzQaVGzBZaZMw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
On Sat, Aug 20, 2016 at 11:42:22AM -0700, ashish mittal wrote:
> I'm trying to understand how I can parse a json command line having
> multiple server list (InetSocketAddressList) without the QemuOpts ->
> QDict -> QAPI conversion that I am currently doing.
>
> block/nbd.c has been suggested, but it only parses a single host
> entry, which is pretty straightforward, but not very helpful.
>
> Could somebody please suggest a sample implementation (other than
> gluster.c) that parses a list of server like options in the json
> format?
Another block driver that takes an array of objects is block/quorum.c.
See quorum_open() and how it picks out "children." objects.
I haven't read the full discussion in this thread but maybe that's what
you're looking for.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-08-23 21:59 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
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 [this message]
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=20160823215803.GA24259@stefanha-x1.localdomain \
--to=stefanha@gmail.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=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).