[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [RFC PATCH 0/2] GlusterFS support in QEMU - v2

From: Kevin Wolf
Subject: Re: [Qemu-devel] [RFC PATCH 0/2] GlusterFS support in QEMU - v2
Date: Tue, 24 Jul 2012 12:24:07 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120605 Thunderbird/13.0

Am 23.07.2012 11:20, schrieb Stefan Hajnoczi:
> On Mon, Jul 23, 2012 at 9:50 AM, Bharata B Rao
> <address@hidden> wrote:
>> On Sun, Jul 22, 2012 at 03:42:28PM +0100, Stefan Hajnoczi wrote:
>>> What about the other transports supported by libgfapi: UNIX domain
>>> sockets and RDMA?  My reading of glfs.h is that there are 3 connection
>>> options:
>>> 1. 'transport': 'socket' (default), 'unix', 'rdma'
>>> 2. 'host': server hostname for 'socket', path to UNIX domain socket
>>> for 'unix', or something else for 'rdma'
>>> 3. 'port': TCP port when 'socket' is used.  Ignored otherwise.
>>> Unfortunately QEMU block drivers cannot take custom options yet.  That
>>> would make it possible to cleanly map these connection options and
>>> save you from inventing syntax which doesn't expose all options.
>>> In the meantime it would be nice if the syntax exposed all options.
>> 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.

This is the way it is without -blockdev. *shrug*


reply via email to

[Prev in Thread] Current Thread [Next in Thread]