Bug 1080992

Summary: OVIRT35 - [RFE] Allow setup of ovirt-websocket-proxy on separate machine
Product: [Retired] oVirt Reporter: Sandro Bonazzola <sbonazzo>
Component: ovirt-engine-installerAssignee: Simone Tiraboschi <stirabos>
Status: CLOSED CURRENTRELEASE QA Contact: Jiri Belka <jbelka>
Severity: low Docs Contact:
Priority: medium    
Version: 3.5CC: bugs, fromani, gklein, iheim, rbalakri, s.kieske, talayan, yeylon
Target Milestone: ---Keywords: FutureFeature, Improvement
Target Release: 3.5.0Flags: sbonazzo: ovirt_requires_release_note?
Hardware: Unspecified   
OS: Unspecified   
URL: http://www.ovirt.org/Features/WebSocketProxy_on_a_separate_host
Whiteboard: integration
Fixed In Version: ovirt-engine-3.5.0_beta Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-17 12:40:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1063236, 1114978, 1115957, 1138800    
Bug Blocks: 985945    

Description Sandro Bonazzola 2014-03-26 12:56:48 UTC 
Allow ovirt-websocket-proxy to be installed and configured by engine-setup on a separate machine, without requiring ovirt-engine to be on the same host.
Comment 1 Jiri Belka 2014-05-23 08:56:29 UTC 
I doubt the way how to do it is the right way (as written in wiki now) :/
Comment 2 Jiri Belka 2014-07-29 14:01:27 UTC 
ok but it's horrible

https://tcms.engineering.redhat.com/run/163679/
Comment 3 Sandro Bonazzola 2014-10-17 12:40:30 UTC 
oVirt 3.5 has been released and should include the fix for this issue.