From: Eric Blake <eblake@redhat.com>
To: Vaibhav Bhembre <vaibhav@digitalocean.com>, qemu-devel@nongnu.org
Cc: Josh Durgin <jdurgin@redhat.com>, Jeff Cody <jcody@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] rbd: reload ceph config for block device
Date: Mon, 20 Jun 2016 10:34:01 -0600 [thread overview]
Message-ID: <57681AF9.10505@redhat.com> (raw)
In-Reply-To: <1466216924-22172-1-git-send-email-vaibhav@digitalocean.com>
[-- Attachment #1: Type: text/plain, Size: 1161 bytes --]
On 06/17/2016 08:28 PM, Vaibhav Bhembre wrote:
> This patch adds ability to reload ceph configuration for an attached RBD
> block device. This is necessary for the cases where rebooting a VM and/or
> detaching-reattaching a RBD drive is not an easy option.
>
> The reload mechanism relies on the bdrv_reopen_* calls to provide a transactional
> +++ b/qapi-schema.json
> @@ -4308,3 +4308,16 @@
> # Since: 2.7
> ##
> { 'command': 'query-hotpluggable-cpus', 'returns': ['HotpluggableCPU'] }
> +
> +##
> +# @reload-rbd-config
> +#
> +# Reload the ceph config for a given RBD block device attached to the VM.
> +#
> +# @device: Name of the device.
> +#
> +# Returns: nothing on success.
> +#
> +# Since: 2.5
You've missed 2.5 by a long shot. This should be 2.7.
> +##
> +{'command': 'reload-rbd-config', 'data': { 'device': 'str' } }
Would 'node' be a better name than 'device'? Isn't this really reloading
the state of an arbitrary BDS node, regardless of whether (or even if)
there is a BB device using that BDS?
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2016-06-20 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-18 2:28 [Qemu-devel] [PATCH] rbd: reload ceph config for block device Vaibhav Bhembre
2016-06-20 16:34 ` Eric Blake [this message]
2016-06-20 17:10 ` Vaibhav Bhembre
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=57681AF9.10505@redhat.com \
--to=eblake@redhat.com \
--cc=jcody@redhat.com \
--cc=jdurgin@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vaibhav@digitalocean.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.