From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:40739) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SwBhX-00044q-FT for qemu-devel@nongnu.org; Tue, 31 Jul 2012 08:37:33 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SwBhP-0004SW-R5 for qemu-devel@nongnu.org; Tue, 31 Jul 2012 08:37:27 -0400 Received: from e28smtp02.in.ibm.com ([122.248.162.2]:47196) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SwBhP-0004Rk-53 for qemu-devel@nongnu.org; Tue, 31 Jul 2012 08:37:19 -0400 Received: from /spool/local by e28smtp02.in.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 31 Jul 2012 18:07:14 +0530 Received: from d28av02.in.ibm.com (d28av02.in.ibm.com [9.184.220.64]) by d28relay03.in.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q6VCalxS23396578 for ; Tue, 31 Jul 2012 18:06:47 +0530 Received: from d28av02.in.ibm.com (loopback [127.0.0.1]) by d28av02.in.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q6VCajkc022737 for ; Tue, 31 Jul 2012 22:36:46 +1000 Date: Tue, 31 Jul 2012 18:08:16 +0530 From: Bharata B Rao Message-ID: <20120731123816.GA19276@in.ibm.com> References: <20120725055806.GB1392@in.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PATCH v3 0/2] GlusterFS support in QEMU - v3 Reply-To: bharata@linux.vnet.ibm.com List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: Amar Tumballi , Anand Avati , qemu-devel@nongnu.org, Vijay Bellur On Tue, Jul 31, 2012 at 09:12:53AM +0100, Stefan Hajnoczi wrote: > On Wed, Jul 25, 2012 at 6:58 AM, Bharata B Rao > wrote: > > Apart from cleanups, the major change in this version is to expose all > > the gluster configuration options to QEMU user. With this, the gluster > > specification looks like this: > > > > -drive file=gluster:server:[port]:[transport]:volname:image > > > > - Here 'gluster' is the protocol. > > - 'server' specifies the server where the volume file specification for > > the given volume resides. > > Works fine for hostnames and IPv4 addresses. It seems like the ':' > separator may prevent users from giving IPv6 addresses unless there is > a way to escape ':'. I feel its better to go the URI way than to escape ':'. I will have this specification in v4: gluster://server:[port]/volname/path/to/image?transport=socket As per http://tools.ietf.org/html/rfc3986#section-3.2.2, ipv6 addresses are specified within square brackets in a URI which makes it easy to parse the port after : Regards, Bharata.