qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org, armbru@redhat.com,
	eblake@redhat.com, hreitz@redhat.com, kwolf@redhat.com,
	pl@dlhnet.de
Subject: Re: [PATCH 2/2] block/rbd: support keyring option via QAPI
Date: Mon, 16 Jun 2025 14:51:07 +0200	[thread overview]
Message-ID: <b0f1ebc4-c7fd-45f9-aa99-a9507c1df55f@proxmox.com> (raw)
In-Reply-To: <CAOi1vP_kEY31-brzTfG6K9y0Wbv06e=9vH=rqD9ouwq32VaYAA@mail.gmail.com>

Am 16.06.25 um 11:34 schrieb Ilya Dryomov:
> On Thu, May 15, 2025 at 1:29 PM Fiona Ebner <f.ebner@proxmox.com> wrote:
>>
>> In Proxmox VE, it is not always required to have a dedicated Ceph
>> configuration file, and using the 'key-secret' QAPI option would
>> require obtaining a key from the keyring first. The keyring location
>> is readily available however, so having support for the 'keyring'
>> configuration option is most convenient.
> 
> Would such a setup have a ceph.conf file that is shared between
> multiple users (or no ceph.conf file at all if the monitors are
> specified via QAPI option) but individual keyring files for each
> user?

There is only a single Ceph user and we could create a ceph.conf file
with the 'keyring' option set. It was just not required in the past,
because we specified 'keyring' via '-drive' directly, so having this
option would be more convenient for us.

In short: we can still make it work on our side if there is no interest
in adding this option in the QAPI.

Best Regards,
Fiona



  reply	other threads:[~2025-06-16 12:51 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 [this message]
2025-06-19 18:56       ` Ilya Dryomov
2025-06-05 13:36 ` [PATCH 0/2] block/rbd: support selected key-value-pairs " Fiona Ebner

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=b0f1ebc4-c7fd-45f9-aa99-a9507c1df55f@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).