Remove nova-xvpvncproxy

Registered by Stephen Finucane on 2019-10-10

XVP VNC consoles can only used by the XenServer virt driver. That same driver also supports noVNC consoles, and our XenServer experts tell us they no longer recommend using the XVP VNC consoles [1]. In addition, the nova-console service and 'os-consoles' APIs are only compatible with this server type and therefore are also unused. As a result, we can and should remove the nova-xvpvncproxy service, the nova-console service, and the 'os-consoles' API.

[1] http://lists.openstack.org/pipermail/openstack-dev/2018-October/135422.html

Blueprint information

Status:
Started
Approver:
Matt Riedemann
Priority:
Undefined
Drafter:
Stephen Finucane
Direction:
Needs approval
Assignee:
Stephen Finucane
Definition:
Approved
Series goal:
Accepted for ussuri
Implementation:
Needs Code Review
Milestone target:
None
Started by
Matt Riedemann on 2019-10-17

Related branches

Sprints

Whiteboard

[mriedem 20191017] We discussed this in the nova meeting today:

http://eavesdrop.openstack.org/meetings/nova/2019/nova.2019-10-17-14.00.log.html#l-220

And agreed to move forward with this. Note that there are changes but they weren't linking to the blueprint properly:

https://review.opendev.org/#/q/topic:bp/remove-nova-console-nova-xvpvncproxy+(status:open+OR+status:merged)

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.