Bug 1041416

Summary:	[RFE][nova]: Spice HTTP proxy
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	marcandre.lureau, markmc, mburns, sgordon, yeylon
Target Milestone:	---	Keywords:	FutureFeature, Reopened
Target Release:	13.0 (Queens)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/nova/+spec/spice-http-proxy
Whiteboard:	upstream_milestone_none upstream_status_needs-code-review upstream_definition_new
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-07-21 20:08:32 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description RHOS Integration 2013-12-12 16:03:11 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/spice-http-proxy.

Description:

Provide a custom HTTP proxy to check console token and tunnel traffic from Spice client to Spice server, without using websocket.

Unlike websocket, HTTP proxy tunnels traffic without any transformation. It doesn't handle SSL or stream multiplexing. While websockets are necessary for html client browser integration, they are aliens to native clients, and require non-trivial amount of additional HTTP/websocket support, which provides redundant features (ssl/messaging/multiplexing) over the existing protocols.

HTTP proxy:
- is one of the most common form of tunneling, and some native clients support it for some time
- do not require complex implementation of websockets in client
- do not require transformations of stream on server side, simplifying code, and lowering CPU if handling thousands of sessions

Specification URL (additional information):

None