qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: mprivozn@redhat.com
Subject: Re: [Qemu-devel] [PATCH 4/5] pr-manager: add query-pr-managers QMP command
Date: Wed, 27 Jun 2018 17:34:18 +0200	[thread overview]
Message-ID: <9260cec8-fd27-3ccb-a133-a2814b684e4d@redhat.com> (raw)
In-Reply-To: <64ad9493-8e84-51c0-f492-8424be8647df@redhat.com>

On 26/06/2018 22:51, Eric Blake wrote:
> On 06/26/2018 10:40 AM, Paolo Bonzini wrote:
>> This command lets you query the connection status of each
>> pr-manager-helper
>> object.
>>
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> ---
> 
>> +++ b/qapi/block.json
>> @@ -77,6 +77,33 @@
>>   { 'struct': 'BlockdevSnapshotInternal',
>>     'data': { 'device': 'str', 'name': 'str' } }
>>   +##
>> +# @PRManagerInfo:
>> +#
>> +# Information about a persistent reservation manager
>> +#
>> +# @id: the identifier of the persistent reservation manager
>> +#
>> +# @is-connected: whether the persistent reservation manager is
>> connected to
>> +#                the underlying storage or helper
>> +#
>> +# Since: 3.0
>> +##
>> +{ 'struct': 'PRManagerInfo',
>> +  'data': {'id': 'str', 'is-connected': 'bool'} }
> 
> Bike-shedding: I think 'connected' is a reasonable (and shorter) name
> for this member

Sounds good.

>> +
>> +##
>> +# @query-pr-managers:
>> +#
>> +# Returns a list of information about each persistent reservation
>> manager.
>> +#
>> +# Returns: a list of @PRManagerInfo for each persistent reservation
>> manager
>> +#
>> +# Since: 3.0
>> +##
>> +{ 'command': 'query-pr-managers', 'returns': ['PRManagerInfo'] }
>> +
> 
> As a query command, does it make sense to consider whether this command
> could be provided during preconfig?

Yes, definitely.

Paolo

  reply	other threads:[~2018-06-27 15:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-26 15:40 [Qemu-devel] [PATCH 0/5] pr-manager/qemu-pr-helper patches for QEMU 3.0 Paolo Bonzini
2018-06-26 15:40 ` [Qemu-devel] [PATCH 1/5] pr-helper: fix --socket-path default in help Paolo Bonzini
2018-06-26 16:13   ` Philippe Mathieu-Daudé
2018-06-26 16:24   ` Michal Privoznik
2018-06-26 15:40 ` [Qemu-devel] [PATCH 2/5] pr-helper: fix assertion failure on failed multipath PERSISTENT RESERVE IN Paolo Bonzini
2018-06-26 16:16   ` Philippe Mathieu-Daudé
2018-06-26 16:25   ` Michal Privoznik
2018-06-26 15:40 ` [Qemu-devel] [PATCH 3/5] pr-manager-helper: avoid SIGSEGV when writing to the socket fail Paolo Bonzini
2018-06-26 16:24   ` Michal Privoznik
2018-06-26 15:40 ` [Qemu-devel] [PATCH 4/5] pr-manager: add query-pr-managers QMP command Paolo Bonzini
2018-06-26 16:31   ` Michal Privoznik
2018-06-27 15:44     ` Paolo Bonzini
2018-06-28  7:05       ` Michal Prívozník
2018-06-28  7:08         ` Paolo Bonzini
2018-06-26 20:51   ` Eric Blake
2018-06-27 15:34     ` Paolo Bonzini [this message]
2018-06-26 15:40 ` [Qemu-devel] [PATCH 5/5] pr-manager-helper: report event on connection/disconnection Paolo Bonzini
2018-06-26 16:23   ` Philippe Mathieu-Daudé
2018-06-27  8:04   ` Michal Privoznik
2018-06-27 10:16   ` Michal Privoznik
2018-06-27 15:35     ` Paolo Bonzini

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=9260cec8-fd27-3ccb-a133-a2814b684e4d@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=eblake@redhat.com \
    --cc=mprivozn@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 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).