From: Prasanna Kalever <pkalever@redhat.com>
To: Peter Krempa <pkrempa@redhat.com>
Cc: kwolf@redhat.com, stefanha@gmail.com, qemu-devel@nongnu.org,
deepakcs@redhat.com, bharata@linux.vnet.ibm.com,
rtalur@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 1/1] block/gluster: add support for multiple gluster backup volfile servers
Date: Sat, 26 Sep 2015 00:47:34 -0400 (EDT) [thread overview]
Message-ID: <1159167986.22189489.1443242854311.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20150923150455.GL324088@andariel.pipo.sk>
> On Tue, Sep 22, 2015 at 04:06:54 -0400, Prasanna Kalever wrote:
> >
> > > On 09/21/2015 05:24 AM, Prasanna Kumar Kalever wrote:
> > > > This patch adds a way to specify multiple backup volfile servers to the
> > > > gluster
> > > > block backend of QEMU with tcp|rdma transport types and their port
> > > > numbers.
> > > >
> > >
> ter
> ...
>
> >
> > > > +##
> > > > +{ 'struct': 'BlockdevOptionsGluster',
> > > > + 'data': { 'volname': 'str',
> > > > + 'image-path': 'str',
> > > > + 'backup-volfile-servers': [ 'GlusterTuplePattern' ] } }
> > >
> > > Shouldn't this be simply 'volfile-servers', as you are including the
> > > primary server in addition to the backup servers?
> > >
> >
> > Again I want to maintain naming as mount.glusterfs do for fuse.
>
> Well, I have to agree with Eric here. I think the option name doesn't
> need to be kept in sync with the gluster implementation since they don't
> share anything with qemu and since the array contains also the primary
> server to be queried the word backup doesn't make snese there.
Yes Peter, I have to agree with you and Eric.
I will rectify this changes in next patch-set, just waiting for 'gfapi' patch to get merged.
Thank you,
Best Regards,
Prasanna Kumar Kalever.
>
> Peter
>
prev parent reply other threads:[~2015-09-26 4:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 11:24 [Qemu-devel] [PATCH v3 1/1] block/gluster: add support for multiple gluster backup volfile servers Prasanna Kumar Kalever
2015-09-21 15:41 ` Eric Blake
2015-09-22 8:06 ` Prasanna Kalever
2015-09-23 15:04 ` Peter Krempa
2015-09-26 4:47 ` Prasanna Kalever [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=1159167986.22189489.1443242854311.JavaMail.zimbra@redhat.com \
--to=pkalever@redhat.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=deepakcs@redhat.com \
--cc=kwolf@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rtalur@redhat.com \
--cc=stefanha@gmail.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).