[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 2/2] qapi/ui: introduce change-vnc-listen
|
From: |
Daniel P . Berrangé |
|
Subject: |
Re: [PATCH 2/2] qapi/ui: introduce change-vnc-listen |
|
Date: |
Thu, 13 Jan 2022 16:30:11 +0000 |
|
User-agent: |
Mutt/2.1.3 (2021-09-10) |
On Thu, Jan 13, 2022 at 05:27:08PM +0100, Markus Armbruster wrote:
> Daniel P. Berrangé <berrange@redhat.com> writes:
>
> > On Mon, Dec 20, 2021 at 04:44:18PM +0100, Vladimir Sementsov-Ogievskiy
> > wrote:
> >> Add command that can change addresses where VNC server listens for new
> >> connections. Prior to 6.0 this functionality was available through
> >> 'change' qmp command which was deleted.
> >>
> >> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> >> ---
> >> docs/about/removed-features.rst | 3 ++-
> >> qapi/ui.json | 12 ++++++++++++
> >> ui/vnc.c | 26 ++++++++++++++++++++++++++
> >> 3 files changed, 40 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/docs/about/removed-features.rst
> >> b/docs/about/removed-features.rst
> >> index d42c3341de..20e6901a82 100644
> >> --- a/docs/about/removed-features.rst
> >> +++ b/docs/about/removed-features.rst
> >> @@ -348,7 +348,8 @@ documentation of ``query-hotpluggable-cpus`` for
> >> additional details.
> >> ``change`` (removed in 6.0)
> >> '''''''''''''''''''''''''''
> >>
> >> -Use ``blockdev-change-medium`` or ``change-vnc-password`` instead.
> >> +Use ``blockdev-change-medium`` or ``change-vnc-password`` or
> >> +``change-vnc-listen`` instead.
> >>
> >> ``query-events`` (removed in 6.0)
> >> '''''''''''''''''''''''''''''''''
> >> diff --git a/qapi/ui.json b/qapi/ui.json
> >> index d7567ac866..14e6fe0b4c 100644
> >> --- a/qapi/ui.json
> >> +++ b/qapi/ui.json
> >> @@ -1304,3 +1304,15 @@
> >> { 'command': 'display-reload',
> >> 'data': 'DisplayReloadOptions',
> >> 'boxed' : true }
> >> +
> >> +##
> >> +# @change-vnc-listen:
> >> +#
> >> +# Change set of addresses to listen for connections.
> >> +#
> >> +# Since: 7.0
> >> +#
> >> +##
> >> +{ 'command': 'change-vnc-listen',
> >> + 'data': { 'id': 'str', 'addresses': ['SocketAddress'],
> >> + '*websockets': ['SocketAddress'] } }
> >
> > We already have a general purpose command above 'display-reload'
> > for doing live changes to the display backends.
> >
> > THis should instead be
> >
> > { 'struct': 'DisplayReloadOptionsVNC',
> > 'data': { '*tls-certs': 'bool',
> > '*addresses': ['SocketAddress'],
> > '*websockets': ['SocketAddress'] } }
> >
> > if 'addresses' is non-null then the listener can be updated.
>
> Good point. Gerd, what do you think?
I guess you could argue that 'display-reload' is more about reloading
state, rather than changing configuration. If we want to make such a
distinction, then we could have a very similar 'display-update' command
for configuration changes.
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 :|