From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:34586) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1StcHu-0005xb-DJ for qemu-devel@nongnu.org; Tue, 24 Jul 2012 06:24:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1StcHk-0002IS-Tk for qemu-devel@nongnu.org; Tue, 24 Jul 2012 06:24:22 -0400 Received: from mx1.redhat.com ([209.132.183.28]:55500) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1StcHk-0002IG-Kd for qemu-devel@nongnu.org; Tue, 24 Jul 2012 06:24:12 -0400 Message-ID: <500E77C7.9010402@redhat.com> Date: Tue, 24 Jul 2012 12:24:07 +0200 From: Kevin Wolf MIME-Version: 1.0 References: <20120721082917.GC1046@in.ibm.com> <20120723085031.GN1046@in.ibm.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC PATCH 0/2] GlusterFS support in QEMU - v2 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: Anand Avati , Vijay Bellur , Amar Tumballi , Markus Armbruster , qemu-devel@nongnu.org, bharata@linux.vnet.ibm.com Am 23.07.2012 11:20, schrieb Stefan Hajnoczi: > On Mon, Jul 23, 2012 at 9:50 AM, Bharata B Rao > 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* Kevin