All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Peter Krempa <pkrempa@redhat.com>
Cc: Prasanna Kumar Kalever <prasanna.kalever@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 v5 1/1] block/gluster: add support for multiple gluster backup volfile servers
Date: Wed, 7 Oct 2015 11:38:30 +0200	[thread overview]
Message-ID: <20151007093830.GC4337@noname.redhat.com> (raw)
In-Reply-To: <20151007090958.GK712645@andariel.pipo.sk>

[-- Attachment #1: Type: text/plain, Size: 2207 bytes --]

Am 07.10.2015 um 11:09 hat Peter Krempa geschrieben:
> On Mon, Sep 28, 2015 at 18:06:12 +0530, Prasanna Kumar Kalever wrote:
> >    driver       => 'gluster' (protocol name)
> >    volname      => name of gluster volume where our VM image resides
> >    image-path   => is the absolute path of image in gluster volume
> > 
> >   {tuple}       => {"server":"1.2.3.4"[,"port":"24007","transport":"tcp"]}
> > 
> >    server       => server address (hostname/ipv4/ipv6 addresses)
> >    port         => port number on which glusterd is listening. (default 24007)
> >    tranport     => transport type used to connect to gluster management daemon,
> >                     it can be tcp|rdma (default 'tcp')
> > 
> > Examples:
> > 1.
> >  -drive driver=qcow2,file.driver=gluster,
> >         file.volname=testvol,file.image-path=/path/a.qcow2,
> >         file.volfile-servers.0.server=1.2.3.4,
> >         file.volfile-servers.0.port=24007,
> >         file.volfile-servers.0.transport=tcp,
> >         file.volfile-servers.1.server=5.6.7.8,
> >         file.volfile-servers.1.port=24008,
> >         file.volfile-servers.1.transport=rdma
> > 2.
> >  'json:{"driver":"qcow2","file":{"driver":"gluster","volname":"testvol",
> >          "image-path":"/path/a.qcow2","volfile-servers":
> >          [{"server":"1.2.3.4","port":"24007","transport":"tcp"},
> >           {"server":"4.5.6.7","port":"24008","transport":"rdma"}] } }'
> 
>   -drive driver=qcow2,file.driver=gluster,
>          file.volume=testvol,
>          file.path=/path/a.qcow2,
>          file.server.0.host=1.2.3.4,
>          file.server.0.port=24007,
>          file.server.0.transport=tcp,
>          file.server.1.host=5.6.7.8,
>          file.server.1.port=24008,
>          file.server.1.transport=rdma
> 
> I'm suggesting the above naming scheme.
> So:
> 'path' instead of 'image-path'
> 'volume' instead of 'volname'
> 'server' instead of 'volfile-servers'
> 'host' instead of 'server'

I agree, let's keep the names short so they are easy to read, type and
remember. I especially agree with changing 'server' into 'host' because
that makes it consistent with InetSocketAddress.

Kevin

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2015-10-07  9:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-28 12:36 [Qemu-devel] [PATCH v5 1/1] block/gluster: add support for multiple gluster backup volfile servers Prasanna Kumar Kalever
2015-10-07  9:09 ` Peter Krempa
2015-10-07  9:38   ` Kevin Wolf [this message]
2015-10-07 10:15   ` Prasanna Kalever
2015-10-07 11:07     ` Peter Krempa

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=20151007093830.GC4337@noname.redhat.com \
    --to=kwolf@redhat.com \
    --cc=bharata@linux.vnet.ibm.com \
    --cc=deepakcs@redhat.com \
    --cc=pkrempa@redhat.com \
    --cc=prasanna.kalever@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.