From: Jeff Cody <jcody@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, armbru@redhat.com,
eblake@redhat.com
Subject: Re: [Qemu-devel] [PATCH 4/4] block/rbd: Add blockdev-add support
Date: Mon, 27 Feb 2017 10:27:15 -0500 [thread overview]
Message-ID: <20170227152715.GF25637@localhost.localdomain> (raw)
In-Reply-To: <20170227134547.GM18219@redhat.com>
On Mon, Feb 27, 2017 at 01:45:47PM +0000, Daniel P. Berrange wrote:
> On Mon, Feb 27, 2017 at 02:30:41AM -0500, Jeff Cody wrote:
> > Signed-off-by: Jeff Cody <jcody@redhat.com>
> > ---
> > qapi/block-core.json | 47 ++++++++++++++++++++++++++++++++++++++++++++---
> > 1 file changed, 44 insertions(+), 3 deletions(-)
> >
> > diff --git a/qapi/block-core.json b/qapi/block-core.json
> > index 5f82d35..08a1419 100644
> > --- a/qapi/block-core.json
> > +++ b/qapi/block-core.json
> > @@ -2111,6 +2111,7 @@
> > # @replication: Since 2.8
> > # @ssh: Since 2.8
> > # @iscsi: Since 2.9
> > +# @rbd: Since 2.9
> > #
> > # Since: 2.0
> > ##
> > @@ -2120,7 +2121,7 @@
> > 'host_device', 'http', 'https', 'iscsi', 'luks', 'nbd', 'nfs',
> > 'null-aio', 'null-co', 'parallels', 'qcow', 'qcow2', 'qed',
> > 'quorum', 'raw', 'replication', 'ssh', 'vdi', 'vhdx', 'vmdk',
> > - 'vpc', 'vvfat' ] }
> > + 'vpc', 'vvfat', 'rbd' ] }
> >
> > ##
> > # @BlockdevOptionsFile:
> > @@ -2376,7 +2377,6 @@
> > 'path': 'str',
> > '*user': 'str' } }
> >
> > -
> > ##
> > # @BlkdebugEvent:
> > #
> > @@ -2666,6 +2666,47 @@
> > '*timeout': 'int' } }
> >
> > ##
> > +# @BlockdevOptionsRbd:
> > +#
> > +# @pool: Ceph pool name
> > +#
> > +# @image: Image name in the Ceph pool
> > +#
> > +# @conf: # optional path to Ceph configuration file. Values
> > +# in the configuration file will be overridden by
> > +# options specified via QAPI.
> > +#
> > +# @snapshot: #optional Ceph snapshot name
> > +#
> > +# @rbd-id: #optional Ceph id name
>
> BTW, I think I'd suggest 'user' or 'username' for this, since that is the more
> common terminology we seem to use for other block drivers
>
OK, I will go with 'user' instead of 'rbd-id'.
I think that fits with the usage terminology in rados_create()
documentation as well:
int rados_create(rados_t * cluster, const char *const id)
[...]
Parameters
* cluster: where to store the handle
* id: the user to connect as (i.e. admin, not client.admin)
-Jeff
prev parent reply other threads:[~2017-02-27 15:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 7:30 [Qemu-devel] [PATCH 0/4] RBD: blockdev-add Jeff Cody
2017-02-27 7:30 ` [Qemu-devel] [PATCH 1/4] block/rbd: don't copy strings in qemu_rbd_next_tok() Jeff Cody
2017-02-27 16:39 ` Markus Armbruster
2017-02-27 18:07 ` Jeff Cody
2017-02-27 7:30 ` [Qemu-devel] [PATCH 2/4] block/rbd: code movement Jeff Cody
2017-02-27 9:28 ` Daniel P. Berrange
2017-02-27 13:14 ` Jeff Cody
2017-02-27 7:30 ` [Qemu-devel] [PATCH 3/4] block/rbd: parse all options via bdrv_parse_filename Jeff Cody
2017-02-27 7:30 ` [Qemu-devel] [PATCH 4/4] block/rbd: Add blockdev-add support Jeff Cody
2017-02-27 7:36 ` Jeff Cody
2017-02-27 9:31 ` Daniel P. Berrange
2017-02-27 13:18 ` Jeff Cody
2017-02-27 13:30 ` Daniel P. Berrange
2017-02-27 13:38 ` Jeff Cody
2017-02-27 13:45 ` Daniel P. Berrange
2017-02-27 15:27 ` Jeff Cody [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=20170227152715.GF25637@localhost.localdomain \
--to=jcody@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).