From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Anand Avati <aavati@redhat.com>,
Vijay Bellur <vbellur@redhat.com>,
Amar Tumballi <amarts@redhat.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
bharata@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [RFC PATCH 0/2] GlusterFS support in QEMU - v2
Date: Mon, 23 Jul 2012 08:34:30 -0600 [thread overview]
Message-ID: <500D60F6.6020903@redhat.com> (raw)
In-Reply-To: <CAJSP0QXdLCV8FDAMLesZS4Y2tYZYLADUFj3-=5AyzviKjRAV3A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
On 07/23/2012 03:20 AM, Stefan Hajnoczi wrote:
>>
>> So without the capability to pass custom options to block drivers, am I forced
>> to keep extending the file= with more and more options ?
>>
>> file=gluster:transport:server:port:volname:image ?
>>
>> Looks ugly and not easy to make any particular option optional. If needed I can
>> support this from GlusterFS backend.
>
> Kevin, Markus: Any thoughts on passing options to block drivers?
> Encoding GlusterFS options into a "filename" string is pretty
> cumbersome.
On 07/23/2012 03:28 AM, ronnie sahlberg wrote:> Why not use
>
> -drive file=gluster://server[:port]/volname/image
At which point, options can fit into this URI scheme:
-drive file=gluster://server:port/volname/image?option1=foo&option2=bar
where anything after the ? of the URI can introduce whichever options
you need.
--
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: 620 bytes --]
next prev parent reply other threads:[~2012-07-23 14:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-21 8:29 [Qemu-devel] [RFC PATCH 0/2] GlusterFS support in QEMU - v2 Bharata B Rao
2012-07-21 8:30 ` [Qemu-devel] [RFC PATCH 1/2] qemu: Add a config option for GlusterFS as block backend Bharata B Rao
2012-07-21 8:31 ` [Qemu-devel] [RFC PATCH 2/2] block: gluster " Bharata B Rao
2012-07-22 15:38 ` Stefan Hajnoczi
2012-07-23 8:32 ` Bharata B Rao
2012-07-23 9:06 ` Stefan Hajnoczi
2012-07-21 12:22 ` [Qemu-devel] [RFC PATCH 0/2] GlusterFS support in QEMU - v2 Vijay Bellur
2012-07-21 13:04 ` Bharata B Rao
2012-07-22 14:42 ` Stefan Hajnoczi
2012-07-23 8:50 ` Bharata B Rao
2012-07-23 9:20 ` Stefan Hajnoczi
2012-07-23 9:34 ` ronnie sahlberg
2012-07-23 9:35 ` Stefan Hajnoczi
2012-07-23 14:34 ` Eric Blake [this message]
2012-07-24 3:34 ` Bharata B Rao
2012-07-24 10:24 ` Kevin Wolf
2012-07-24 11:30 ` Markus Armbruster
2012-07-23 9:36 ` Vijay Bellur
2012-07-23 9:16 ` Daniel P. Berrange
2012-07-23 9:28 ` ronnie sahlberg
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=500D60F6.6020903@redhat.com \
--to=eblake@redhat.com \
--cc=aavati@redhat.com \
--cc=amarts@redhat.com \
--cc=armbru@redhat.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=vbellur@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).