2021-09-15 16:29:29 +00:00
|
|
|
"""
|
|
|
|
QEMU Monitor Protocol (QMP) development library & tooling.
|
|
|
|
|
|
|
|
This package provides a fairly low-level class for communicating
|
|
|
|
asynchronously with QMP protocol servers, as implemented by QEMU, the
|
|
|
|
QEMU Guest Agent, and the QEMU Storage Daemon.
|
|
|
|
|
|
|
|
`QMPClient` provides the main functionality of this package. All errors
|
2022-01-10 23:28:44 +00:00
|
|
|
raised by this library derive from `AQMPError`, see `aqmp.error` for
|
2021-09-15 16:29:29 +00:00
|
|
|
additional detail. See `aqmp.events` for an in-depth tutorial on
|
|
|
|
managing QMP events.
|
|
|
|
"""
|
|
|
|
|
|
|
|
# Copyright (C) 2020, 2021 John Snow for Red Hat, Inc.
|
|
|
|
#
|
|
|
|
# Authors:
|
|
|
|
# John Snow <jsnow@redhat.com>
|
|
|
|
#
|
|
|
|
# Based on earlier work by Luiz Capitulino <lcapitulino@redhat.com>.
|
|
|
|
#
|
|
|
|
# This work is licensed under the terms of the GNU GPL, version 2. See
|
|
|
|
# the COPYING file in the top-level directory.
|
|
|
|
|
python/aqmp: Disable logging messages by default
AQMP is a library, and ideally it should not print error diagnostics
unless a user opts into seeing them. By default, Python will print all
WARNING, ERROR or CRITICAL messages to screen if no logging
configuration has been created by a client application.
In AQMP's case, ERROR logging statements are used to report additional
detail about runtime failures that will also eventually be reported to the
client library via an Exception, so these messages should not be
rendered by default.
(Why bother to have them at all, then? In async contexts, there may be
multiple Exceptions and we are only able to report one of them back to
the client application. It is not reasonably easy to predict ahead of
time if one or more of these Exceptions will be squelched. Therefore,
it's useful to log intermediate failures to help make sense of the
ultimate, resulting failure.)
Add a NullHandler that will suppress these messages until a client
application opts into logging via logging.basicConfig or similar. Note
that upon calling basicConfig(), this handler will *not* suppress these
messages from being displayed by the client's configuration.
Signed-off-by: John Snow <jsnow@redhat.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Message-id: 20210923004938.3999963-8-jsnow@redhat.com
Signed-off-by: John Snow <jsnow@redhat.com>
2021-09-23 00:49:28 +00:00
|
|
|
import logging
|
2021-09-15 16:29:51 +00:00
|
|
|
|
2021-09-15 16:29:30 +00:00
|
|
|
from .error import AQMPError
|
2021-09-15 16:29:43 +00:00
|
|
|
from .events import EventListener
|
2021-09-15 16:29:41 +00:00
|
|
|
from .message import Message
|
2022-01-10 23:28:48 +00:00
|
|
|
from .protocol import (
|
|
|
|
ConnectError,
|
|
|
|
Runstate,
|
|
|
|
SocketAddrT,
|
|
|
|
StateError,
|
|
|
|
)
|
2021-09-15 16:29:48 +00:00
|
|
|
from .qmp_client import ExecInterruptedError, ExecuteError, QMPClient
|
2021-09-15 16:29:30 +00:00
|
|
|
|
2021-09-15 16:29:29 +00:00
|
|
|
|
python/aqmp: Disable logging messages by default
AQMP is a library, and ideally it should not print error diagnostics
unless a user opts into seeing them. By default, Python will print all
WARNING, ERROR or CRITICAL messages to screen if no logging
configuration has been created by a client application.
In AQMP's case, ERROR logging statements are used to report additional
detail about runtime failures that will also eventually be reported to the
client library via an Exception, so these messages should not be
rendered by default.
(Why bother to have them at all, then? In async contexts, there may be
multiple Exceptions and we are only able to report one of them back to
the client application. It is not reasonably easy to predict ahead of
time if one or more of these Exceptions will be squelched. Therefore,
it's useful to log intermediate failures to help make sense of the
ultimate, resulting failure.)
Add a NullHandler that will suppress these messages until a client
application opts into logging via logging.basicConfig or similar. Note
that upon calling basicConfig(), this handler will *not* suppress these
messages from being displayed by the client's configuration.
Signed-off-by: John Snow <jsnow@redhat.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Message-id: 20210923004938.3999963-8-jsnow@redhat.com
Signed-off-by: John Snow <jsnow@redhat.com>
2021-09-23 00:49:28 +00:00
|
|
|
# Suppress logging unless an application engages it.
|
|
|
|
logging.getLogger('qemu.aqmp').addHandler(logging.NullHandler())
|
|
|
|
|
2021-09-15 16:29:51 +00:00
|
|
|
|
2021-09-15 16:29:29 +00:00
|
|
|
# The order of these fields impact the Sphinx documentation order.
|
|
|
|
__all__ = (
|
2021-09-15 16:29:41 +00:00
|
|
|
# Classes, most to least important
|
2021-09-15 16:29:45 +00:00
|
|
|
'QMPClient',
|
2021-09-15 16:29:41 +00:00
|
|
|
'Message',
|
2021-09-15 16:29:43 +00:00
|
|
|
'EventListener',
|
2021-09-15 16:29:34 +00:00
|
|
|
'Runstate',
|
|
|
|
|
2021-09-15 16:29:33 +00:00
|
|
|
# Exceptions, most generic to most explicit
|
2021-09-15 16:29:30 +00:00
|
|
|
'AQMPError',
|
2021-09-15 16:29:34 +00:00
|
|
|
'StateError',
|
2021-09-15 16:29:33 +00:00
|
|
|
'ConnectError',
|
2021-09-15 16:29:48 +00:00
|
|
|
'ExecuteError',
|
|
|
|
'ExecInterruptedError',
|
2022-01-10 23:28:48 +00:00
|
|
|
|
|
|
|
# Type aliases
|
|
|
|
'SocketAddrT',
|
2021-09-15 16:29:29 +00:00
|
|
|
)
|