qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Cody <jcody@redhat.com>
To: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, eblake@redhat.com,
	pkrempa@redhat.com, bharata@linux.vnet.ibm.com,
	berrange@redhat.com, rtalur@redhat.com, deepakcs@redhat.com,
	armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH v17 0/4][WIP] block/gluster: add support for multiple gluster servers
Date: Wed, 29 Jun 2016 10:11:31 -0400	[thread overview]
Message-ID: <20160629141131.GA17242@localhost.localdomain> (raw)
In-Reply-To: <1465979147-1993-1-git-send-email-prasanna.kalever@redhat.com>

On Wed, Jun 15, 2016 at 01:55:43PM +0530, Prasanna Kumar Kalever wrote:
> This version of patches are rebased on master branch.
> 
> Prasanna Kumar Kalever (4):
>   block/gluster: rename [server, volname, image] -> [host, volume, path]
>   block/gluster: code cleanup
>   block/gluster: using new qapi schema
>   block/gluster: add support for multiple gluster servers
>

I think the main criticism with this series revolves around the interface,
and the overloading of the server hosts fields when using tcp and unix
sockets, etc.  The idea of using flat unions for the API was floated.

Eric, does this criticism still stand, from libvirt's perspective?  Or are
you comfortable enough with the current interface that I can go ahead and
take this series in through my tree?


> v1:
> multiple host addresses but common port number and transport type
> pattern: URI syntax with query (?) delimitor
> syntax:
>     file=gluster[+transport-type]://host1:24007/testvol/a.img\
>          ?server=host2&server=host3
> 
> v2:
> multiple host addresses each have their own port number, but all use
>                                                          common transport type
> pattern: URI syntax  with query (?) delimiter
> syntax:
>     file=gluster[+transport-type]://[host[:port]]/testvol/a.img\
>          [?server=host1[:port]\
>           &server=host2[:port]]
> 
> v3:
> multiple host addresses each have their own port number and transport type
> pattern: changed to json
> syntax:
>     'json:{"driver":"qcow2","file":{"driver":"gluster","volume":"testvol",
>            "path":"/path/a.qcow2","server":
>          [{"host":"1.2.3.4","port":"24007","transport":"tcp"},
>           {"host":"4.5.6.7","port":"24008","transport":"rdma"}] } }'
> 
> v4, v5:
> address comments from "Eric Blake" <eblake@redhat.com>
> renamed:
> 'backup-volfile-servers' -> 'volfile-servers'
> 
> v6:
> address comments from Peter Krempa <pkrempa@redhat.com>
> renamed:
>  'volname'    ->  'volume'
>  'image-path' ->  'path'
>  'server'     ->  'host'
> 
> v7:
> fix for v6 (initialize num_servers to 1 and other typos)
> 
> v8:
> split patch set v7 into series of 3 as per Peter Krempa <pkrempa@redhat.com>
> review comments
> 
> v9:
> reorder the series of patches addressing "Eric Blake" <eblake@redhat.com>
> review comments
> 
> v10:
> fix mem-leak as per Peter Krempa <pkrempa@redhat.com> review comments
> 
> v11:
> using qapi-types* defined structures as per "Eric Blake" <eblake@redhat.com>
> review comments.
> 
> v12:
> fix crash caused in qapi_free_BlockdevOptionsGluster
> 
> v13:
> address comments from "Jeff Cody" <jcody@redhat.com>
> 
> v14:
> address comments from "Eric Blake" <eblake@redhat.com>
> split patch 3/3 into two
> rename input option and variable from 'servers' to 'server'
> 
> v15:
> patch 1/4 changed the commit message as per Eric's comment
> patch 2/4 are unchanged
> patch 3/4 addressed Jeff's comments
> patch 4/4 concentrates on unix transport related help info,
> rename 'parse_transport_option()' to 'qapi_enum_parse()',
> address memory leaks and other comments given by Jeff and Eric
> 
> v16:
> In patch 4/4 fixed segfault on glfs_init() error case, as per Jeff's comments
> other patches in this series remain unchanged
> 
> v17:
> rebase of v16 on latest master
> 
>  block/gluster.c      | 484 ++++++++++++++++++++++++++++++++++++++-------------
>  qapi/block-core.json |  64 ++++++-
>  2 files changed, 419 insertions(+), 129 deletions(-)
> 
> -- 
> 2.5.5
> 

  parent reply	other threads:[~2016-06-29 14:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-15  8:25 [Qemu-devel] [PATCH v17 0/4][WIP] block/gluster: add support for multiple gluster servers Prasanna Kumar Kalever
2016-06-15  8:25 ` [Qemu-devel] [PATCH v17 1/4] block/gluster: rename [server, volname, image] -> [host, volume, path] Prasanna Kumar Kalever
2016-06-17 17:32   ` Jeff Cody
2016-06-15  8:25 ` [Qemu-devel] [PATCH v17 2/4] block/gluster: code cleanup Prasanna Kumar Kalever
2016-06-17 17:32   ` Jeff Cody
2016-06-15  8:25 ` [Qemu-devel] [PATCH v17 3/4] block/gluster: using new qapi schema Prasanna Kumar Kalever
2016-06-15  8:25 ` [Qemu-devel] [PATCH v17 4/4] block/gluster: add support for multiple gluster servers Prasanna Kumar Kalever
2016-06-29 14:11 ` Jeff Cody [this message]
2016-06-29 14:17   ` [Qemu-devel] [PATCH v17 0/4][WIP] " Daniel P. Berrange

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=20160629141131.GA17242@localhost.localdomain \
    --to=jcody@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=bharata@linux.vnet.ibm.com \
    --cc=deepakcs@redhat.com \
    --cc=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pkrempa@redhat.com \
    --cc=prasanna.kalever@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rtalur@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).