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 [1] (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.
[1]
https://github.com/openstack/nova/commit/b437a98738c7a564205d1b27e36b844cd54445d1
--
Thanks,
Matt Riedemann
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
