Re: [PATCH 11/11] Deprecate stable non-JSON -device and -object
Am 27.09.2021 um 11:00 hat Peter Maydell geschrieben:
On Fri, 24 Sept 2021 at 10:14, Kevin Wolf <kwolf(a)redhat.com>
wrote:
>
> We want to switch both from QemuOpts to the keyval parser in the future,
> which results in some incompatibilities, mainly around list handling.
> Mark the non-JSON version of both as unstable syntax so that management
> tools switch to JSON and we can later make the change without breaking
> things.
>
> Signed-off-by: Kevin Wolf <kwolf(a)redhat.com>
> +Stable non-JSON ``-device`` and ``-object`` syntax (since 6.2)
>
+''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
> +
> +If you rely on a stable interface for ``-device`` and ``-object`` that doesn't
> +change incompatibly between QEMU versions (e.g. because you are using the QEMU
> +command line as a machine interface in scripts rather than interactively), use
> +JSON syntax for these options instead.
> +
> +There is no intention to remove support for non-JSON syntax entirely, but
> +future versions may change the way to spell some options.
As it stands, this is basically saying "pretty much anybody
using the command line, your stuff may break in future, instead
use some other interface you've never heard of, which doesn't
appear to be documented in the manual and which none of the
documentation's examples use".
The documentation is a valid criticism. We need to document the JSON
interfaces properly (which will really mostly be a pointer to the
existing QMP documentation at least for -object, but it's important to
tell people where to look for the details).
Is there some more limited deprecation we can do rather than
"the
entire commandline for almost all users" ?
I don't think "almost all" users is true. I see three groups of users:
1. Using a management tool that is probably using libvirt. This is
likely the vast majority of users. They won't notice a difference
because libvirt abstracts it away. libvirt developers are actively
asking us for JSON (and QAPI) based interfaces because using the same
representation to describe configurations in QMP and on the CLI makes
their life easier.
2. People starting QEMU on the command line manually. This is
essentially the same situation as HMP: If something changes, you get
an error message, you look up the new syntax, done. Small
inconvenience, but that's it. This includes simple scripts that just
start QEMU and are only used to store a long command line somewhere.
3. People writing more complex scripts or applications that invoke QEMU
manually instead of using libvirt. They may actually be hurt by such
changes. They should probably be using a proper machine interface,
i.e. JSON mode, so the deprecation notice is for them to change
their code. This is probably a small minority and not "almost all
users".
Yes, we could in theory do a more limited deprecation. The planned
change from my side is just going from QemuOpts to the keyval parser,
which doesn't change anything in the vast majority of cases.
But we have the separation in the monitor between QMP and HMP for a good
reason: Requirements for a good machine interface are different from a
good human interface. The same is true for the command line.
So it seems to make a lot of sense to me to have both a machine
interface (JSON based) and a human interface (non-JSON) on the command
line, too, and take the same liberties for evolving the human interface
as we already do in HMP - which means that it's technically an unstable
interface where compatibility doesn't prevent improvements, but not that
it looks completely different in every QEMU version.
Kevin