From: Josh Durgin <josh.durgin@dreamhost.com>
To: qemu-devel@nongnu.org
Cc: ceph-devel@vger.kernel.org, kwolf@redhat.com
Subject: [RFC 0/2] rbd authentication
Date: Wed, 9 Nov 2011 16:20:54 -0800 [thread overview]
Message-ID: <cover.1320884065.git.josh.durgin@dreamhost.com> (raw)
These patches allow keys to be passed to rbd devices for
authentication via the same interface that qcow uses for encryption -
the monitor block_passwd command.
Since rbd cannot read anything from the cluster before authenticating,
the size of the device is unknown until the key is set. At this point,
the size can be refreshed as if the device were resized. This works
fine with the virtio driver, but other drivers, like ide, don't
implement the resize callback. What do you think is the best way to
solve this?
Josh Durgin (2):
block: let bdrv_set_key be used for authentication
rbd: implement bdrv_set_key
block.c | 27 +++++++---
block.h | 2 +-
block/rbd.c | 160 ++++++++++++++++++++++++++++++++++++++----------------
block_int.h | 3 +-
blockdev.c | 3 +-
hmp-commands.hx | 6 +-
monitor.c | 13 +++--
qapi-schema.json | 7 ++-
qemu-img.c | 4 +-
qerror.c | 16 +++---
qerror.h | 12 ++--
qmp-commands.hx | 6 ++-
12 files changed, 172 insertions(+), 87 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Josh Durgin <josh.durgin@dreamhost.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, ceph-devel@vger.kernel.org
Subject: [Qemu-devel] [RFC 0/2] rbd authentication
Date: Wed, 9 Nov 2011 16:20:54 -0800 [thread overview]
Message-ID: <cover.1320884065.git.josh.durgin@dreamhost.com> (raw)
These patches allow keys to be passed to rbd devices for
authentication via the same interface that qcow uses for encryption -
the monitor block_passwd command.
Since rbd cannot read anything from the cluster before authenticating,
the size of the device is unknown until the key is set. At this point,
the size can be refreshed as if the device were resized. This works
fine with the virtio driver, but other drivers, like ide, don't
implement the resize callback. What do you think is the best way to
solve this?
Josh Durgin (2):
block: let bdrv_set_key be used for authentication
rbd: implement bdrv_set_key
block.c | 27 +++++++---
block.h | 2 +-
block/rbd.c | 160 ++++++++++++++++++++++++++++++++++++++----------------
block_int.h | 3 +-
blockdev.c | 3 +-
hmp-commands.hx | 6 +-
monitor.c | 13 +++--
qapi-schema.json | 7 ++-
qemu-img.c | 4 +-
qerror.c | 16 +++---
qerror.h | 12 ++--
qmp-commands.hx | 6 ++-
12 files changed, 172 insertions(+), 87 deletions(-)
next reply other threads:[~2011-11-10 0:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 0:20 Josh Durgin [this message]
2011-11-10 0:20 ` [Qemu-devel] [RFC 0/2] rbd authentication Josh Durgin
2011-11-10 0:20 ` [RFC 1/2] block: let bdrv_set_key be used for authentication Josh Durgin
2011-11-10 0:20 ` [Qemu-devel] " Josh Durgin
2011-11-10 0:20 ` [RFC 2/2] rbd: implement bdrv_set_key Josh Durgin
2011-11-10 0:20 ` [Qemu-devel] " Josh Durgin
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=cover.1320884065.git.josh.durgin@dreamhost.com \
--to=josh.durgin@dreamhost.com \
--cc=ceph-devel@vger.kernel.org \
--cc=kwolf@redhat.com \
--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 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.