[Openstack-operators] [openstack-dev] [nova] can we deprecate the xvp console?
andrew at lascii.com
Thu Nov 5 18:17:29 UTC 2015
On 11/05/15 at 10:39am, Matt Riedemann wrote:
>I noticed today that nova.console.xvp hits the database directly for
>console pools. We should convert this to objects so that the console
>service does not have direct access to the database (this is the only
>console I see that hits the database directly). However, rather than
>go through the work of create an object for ConsolePools, if no one
>is using xvp consoles in nova then we could deprecate it.
>It looks like it was added back in diablo  (at least).
>Someone from Rackspace in IRC said that they weren't using it, so
>given it's for xenserver I assume that means probably no one is using
>it, but we need to ask first.
So apparently I was wrong. We are using both novnc and xvpvncproxy in
an attempt to eventually get off of xvpvnxproxy. It's possible that
nobody else is using it, but Rackspace at least is for now.
>Please respond else I'll probably move forward with deprecation at
>some point in mitaka-1.
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-operators