From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
kvm-devel <kvm@vger.kernel.org>,
Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>,
John Snow <jsnow@redhat.com>
Subject: Re: KVM call for agenda for 2020-10-06
Date: Wed, 7 Oct 2020 19:04:29 +0100 [thread overview]
Message-ID: <20201007180429.GI2505881@redhat.com> (raw)
In-Reply-To: <8fce8f99-56bd-6a87-9789-325d6ffff54d@redhat.com>
On Wed, Oct 07, 2020 at 07:50:20PM +0200, Paolo Bonzini wrote:
> On 06/10/20 20:21, Stefan Hajnoczi wrote:
> > * Does command-line order matter?
> > * Two options: allow any order OR left-to-right ordering
> > * Andrea Bolognani: Most users expect left-to-right ordering,
> > why allow any order?
> > * Eduardo Habkost: Can we enforce left-to-right ordering or do
> > we need to follow the deprecation process?
> > * Daniel Berrange: Solve compability by introducing new
> > binaries without the burden of backwards compability
>
> I think "new binaries" shouldn't even have a command line; all
> configuration should happen through QMP commands. Those are naturally
> time-ordered, which is equivalent to left-to-right, and therefore the
> question is sidestepped. Perhaps even having a command line in
> qemu-storage-daemon was a mistake.
Non-interactive configuration is a nice property for simpler integration
use cases. eg launching from the shell is tedious with QMP compared to
CLI args.
This could be addressed though by having a configuration file to load
config from, where the config entries can be mapped 1-1 onto QMP commands,
essentially making the config file a non-interactive QMP.
> The big question to me is whether the configuration should be
> QAPI-based, that is based on QAPI structs, or QMP-based. If the latter,
> "object-add" (and to a lesser extent "device-add") are fine mechanisms
> for configuration. There is still need for better QOM introspection,
> but it would be much simpler than doing QOM object creation via QAPI
> struct, if at all possible.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2020-10-07 18:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 9:09 KVM call for agenda for 2020-10-06 Juan Quintela
2020-10-02 15:16 ` John Snow
2020-10-05 14:46 ` Stefan Hajnoczi
2020-10-06 18:21 ` Stefan Hajnoczi
2020-10-07 17:50 ` Paolo Bonzini
2020-10-07 18:04 ` Daniel P. Berrangé [this message]
2020-10-08 11:25 ` Markus Armbruster
2020-10-08 14:15 ` Paolo Bonzini
2020-10-08 8:03 ` Kevin Wolf
2020-10-09 16:45 ` Eduardo Habkost
2020-10-10 4:41 ` 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=20201007180429.GI2505881@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jsnow@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 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).