From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Kashyap Chamarthy <kchamart@redhat.com>, qemu-devel@nongnu.org
Cc: armbru@redhat.com, "Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: [Qemu-devel] Should the "props" be documented for QMP `object-add`?
Date: Wed, 9 Jan 2019 11:31:18 +0100 [thread overview]
Message-ID: <16805fd6-6326-4acc-ee99-ac0899a8cf1e@redhat.com> (raw)
In-Reply-To: <20190109085113.GA23677@paraplu>
Hi Kashyap,
On 1/9/19 9:51 AM, Kashyap Chamarthy wrote:
> I notice that the following QMP command:
>
> {
> "execute":"object-add",
> "arguments":{
> "qom-type":"tls-creds-x509",
> "id":"objlibvirt_migrate_tls0",
> "props":{
> "dir":"/etc/pki/qemu",
> "endpoint":"server",
> "verify-peer":true
> }
> }
> }
>
> ... is the same as its command-line equivalent:
>
> -object tls-creds-x509,id=tls0,dir=/etc/pki/qemu,endpoint=server,verify-peer=yes
>
> That said, in qapi/misc.json "@object-add" doesn't document any of the
> "props". Is it on purpose? Maybe because it is a 1:1 mapping of the
> command-line `-object` (which _is_ documented in qemu-doc.texi).
>
> Is it a good idea to send a patch to document the "props" in
> qapi/misc.json? Or would it be needless duplication?
IMHO the 1:1 mapping is only obvious for developpers who implement such
commands and for 3rd party libs using QMP.
For end-users, a command-line comment is helpful.
This remind me of this patch:
https://lists.gnu.org/archive/html/qemu-devel/2018-11/msg06623.html
+/**
+ * QAuthZSimple:
+ *
+ * This authorization driver provides a simple mechanism
+ * for granting access based on an exact matched username.
+ *
+ * To create an instance of this class via QMP:
+ *
+ * {
+ * "execute": "object-add",
+ * "arguments": {
+ * "qom-type": "authz-simple",
+ * "id": "authz0",
+ * "parameters": {
+ * "identity": "fred"
+ * }
+ * }
+ * }
+ *
+ * Or via the command line
+ *
+ * -object authz-simple,id=authz0,identity=fred
+ *
+ */
Regards,
Phil.
next prev parent reply other threads:[~2019-01-09 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 8:51 [Qemu-devel] Should the "props" be documented for QMP `object-add`? Kashyap Chamarthy
2019-01-09 10:31 ` Philippe Mathieu-Daudé [this message]
2019-01-09 10:44 ` Kashyap Chamarthy
2019-01-09 11:02 ` Daniel P. Berrangé
2019-01-09 11:21 ` Kashyap Chamarthy
2019-01-09 13:01 ` Markus Armbruster
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=16805fd6-6326-4acc-ee99-ac0899a8cf1e@redhat.com \
--to=philmd@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=kchamart@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).