From: Fiona Ebner <f.ebner@proxmox.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, armbru@redhat.com, eblake@redhat.com,
hreitz@redhat.com, kwolf@redhat.com, pl@dlhnet.de,
idryomov@gmail.com
Subject: Re: [PATCH 0/2] block/rbd: support selected key-value-pairs via QAPI
Date: Thu, 5 Jun 2025 15:36:29 +0200 [thread overview]
Message-ID: <b6d271b2-00e0-4475-b96c-f96e3e2f12fd@proxmox.com> (raw)
In-Reply-To: <20250515112908.383693-1-f.ebner@proxmox.com>
Am 15.05.25 um 13:29 schrieb Fiona Ebner:
> Currently, most Ceph configuration options are not exposed via QAPI.
> While it is possible to specify a dedicated Ceph configuration file,
> specialized options are often only required for a selection of images
> on the RBD storage, not all of them. To avoid the need to generate a
> dedicated Ceph configuration file for each image (or for each required
> combination of options), support a selection of key-value pairs via
> QAPI.
>
> Fiona Ebner (2):
> block/rbd: support selected key-value-pairs via QAPI
> block/rbd: support keyring option via QAPI
>
> block/rbd.c | 81 ++++++++++++++++++++++++++++++++++++++++++++
> qapi/block-core.json | 40 ++++++++++++++++++++++
> 2 files changed, 121 insertions(+)
Ping
prev parent reply other threads:[~2025-06-05 13:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 11:29 [PATCH 0/2] block/rbd: support selected key-value-pairs via QAPI Fiona Ebner
2025-05-15 11:29 ` [PATCH 1/2] " Fiona Ebner
2025-06-16 9:25 ` Ilya Dryomov
2025-06-16 9:52 ` Daniel P. Berrangé
2025-06-16 10:28 ` Ilya Dryomov
2025-06-16 12:38 ` Fiona Ebner
2025-06-19 18:38 ` Ilya Dryomov
2025-06-19 21:20 ` Ilya Dryomov
2025-06-20 8:18 ` Fiona Ebner
2025-06-16 12:29 ` Fiona Ebner
2025-06-16 12:34 ` Daniel P. Berrangé
2025-06-16 9:41 ` Daniel P. Berrangé
2025-05-15 11:29 ` [PATCH 2/2] block/rbd: support keyring option " Fiona Ebner
2025-06-16 9:34 ` Ilya Dryomov
2025-06-16 12:51 ` Fiona Ebner
2025-06-19 18:56 ` Ilya Dryomov
2025-06-05 13:36 ` Fiona Ebner [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=b6d271b2-00e0-4475-b96c-f96e3e2f12fd@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=hreitz@redhat.com \
--cc=idryomov@gmail.com \
--cc=kwolf@redhat.com \
--cc=pl@dlhnet.de \
--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).