[openstack-dev] [nova][xenapi] can we deprecate the xenapi-specific 'nova-console' service?

Bob Ball bob.ball at citrix.com
Thu Oct 4 12:03:41 UTC 2018

Hi Melanie,

We recommend using novncproxy_base_url with vncserver_proxyclient_address set to the dom0's management IP address.

We don't currently use nova-console, so deprecation would be the best approach.



-----Original Message-----
From: melanie witt [mailto:melwittt at gmail.com] 
Sent: 03 October 2018 23:08
To: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org>; openstack-operators at lists.openstack.org
Subject: [openstack-dev] [nova][xenapi] can we deprecate the xenapi-specific 'nova-console' service?

Greetings Devs and Ops,

Today I noticed that our code does not handle the 'nova-console' service properly in a multi-cell deployment and given that no one has complained or reported bugs about it, we're wondering if anyone still uses the nova-console service. The documentation [1] says that the nova-console service is a "XenAPI-specific service that most recent VNC proxy architectures do not use."

Can anyone from xenapi land shed some light on whether the nova-console service is still useful in deployments using the xenapi driver, or is it an old relic that we should deprecate and remove?

Thanks for your help,

[1] https://docs.openstack.org/nova/latest/admin/remote-console-access.html	
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe

More information about the OpenStack-dev mailing list