From: "Daniel P. Berrange" <berrange@redhat.com>
To: Jeff Cody <jcody@redhat.com>
Cc: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>,
qemu-devel@nongnu.org, kwolf@redhat.com, eblake@redhat.com,
pkrempa@redhat.com, bharata@linux.vnet.ibm.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 15:17:01 +0100 [thread overview]
Message-ID: <20160629141701.GR4221@redhat.com> (raw)
In-Reply-To: <20160629141131.GA17242@localhost.localdomain>
On Wed, Jun 29, 2016 at 10:11:31AM -0400, Jeff Cody wrote:
> 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?
Just from a general QAPI design POV I think this overloading is undesirable.
We cared enough about not doing this overloading in the past that we
created SocketAddress which is a union of InetSocketAddress and
UnixSocketAddress. Given this historical best practice, I don't think
we should be overloading "host" for unix socket path.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
prev parent reply other threads:[~2016-06-29 14:17 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 ` [Qemu-devel] [PATCH v17 0/4][WIP] " Jeff Cody
2016-06-29 14:17 ` Daniel P. Berrange [this message]
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=20160629141701.GR4221@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=deepakcs@redhat.com \
--cc=eblake@redhat.com \
--cc=jcody@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).