Bug 1375217

Summary:	[RFE] HTML5 consoles via reverse proxy
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Jiri Belka <jbelka>
Component:	RFEs	Assignee:	Scott Herold <sherold>
Status:	CLOSED WONTFIX	QA Contact:	Gil Klein <gklein>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.0.3	CC:	gklein, lsurette, michal.skrivanek, rbalakri, srevivo, ykaul
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-13 07:34:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jiri Belka 2016-09-12 13:39:30 UTC

Description of problem:

We support accessing engine via reverse proxy under different name, so it is accessible both from LAN via its real FQDN and from other networks via different FQDN. See https://bugzilla.redhat.com/show_bug.cgi?id=1353093#c8

This should cover also HTML5 consoles, it's seems little bit tricky, we need reverse proxy app (eg. apache httpd 2.x with mod_proxy* modules) which needs to talk via websockets to engine's ovirt-engine-websocket-proxy.

It's nice to have (documented).

Version-Release number of selected component (if applicable):
4.x

How reproducible:
100%

Steps to Reproduce:
1. access html5 consoles via reverse proxy which offers access to rhvm via different fqdn as engine's real fqdn
2.
3.

Actual results:
unclear how to configure this

Expected results:
should work

Additional info:

Comment 2 Michal Skrivanek 2016-09-13 07:34:16 UTC

WebSocketProxy engine config option is supposed to be set to a resolvable IP/FQDN for the clients connecting to the proxy. We will not introduce yet another mechanism officially. Of course this is doable with the appropriate proxy or dns configuration to resolve correctly even when using the internal FQDN of engine, but that's beyond the scope of oVirt/RHEV docs