Bug 838468
| Summary: | PRD33 - [RFE] Add NoVNC web console | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Andrew Cathrow <acathrow> | |
| Component: | RFEs | Assignee: | Frantisek Kobzik <fkobzik> | |
| Status: | CLOSED ERRATA | QA Contact: | Jiri Belka <jbelka> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | high | |||
| Version: | 3.1.0 | CC: | acathrow, adahms, alonbl, byount, cdevine, chenders, fkobzik, iheim, lpeer, lyarwood, michal.skrivanek, pstehlik, rbalakri, thildred, tvvcox | |
| Target Milestone: | --- | Keywords: | FutureFeature | |
| Target Release: | 3.3.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| URL: | http://www.ovirt.org/Features/noVNC_console | |||
| Whiteboard: | virt | |||
| Fixed In Version: | is6 | Doc Type: | Enhancement | |
| Doc Text: |
This features introduces the noVNC console client to Red Hat Enterprise Virtualization Manager. With this feature, users can connect to VNC consoles from within their browser using the noVNC client. For this feature to work, the websocket proxy must be set up and running in the virtualization environment, and the Red Hat Enterprise Virtualization Manager must be aware of the websocket proxy by correctly configuring the WebSocketProxy configuration key using engine-config. Moreover, the client machine must have a browser that supports websockets and postMessage, and the Certificate Authority of the Red Hat Enterprise Virtualization Manager must be imported into the client browser is SSL is enabled.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 976172 (view as bug list) | Environment: | ||
| Last Closed: | 2014-01-21 17:28:00 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: | 950425, 950433, 976555 | |||
| Bug Blocks: | 976172, 1019470 | |||
|
Description
Andrew Cathrow
2012-07-09 08:08:58 UTC
target 3.3 for now. Planning per-VM/user option in UP/WebAdmin to select the preferred client/means of connect Merged U/S: b8d36b573fb10e56cb2ce7324aa506cce025bea3 Please ensure there's logging working correctly for websocket proxy on RHEL, thanks! (In reply to Jiri Belka from comment #23) > Two issues: > > - typo Thanks! merged to master: http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=045d1e7a9e42c8a91756e64ee5d314d9842a21d6 http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=b8d36b573fb10e56cb2ce7324aa506cce025bea3 http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=73e767e1c41dd03fac8ee6b279490ecbad778a0a http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=321817be02f8cd5ff5d2475772001f7c0e312f45 or trust the engine's certificate authority and use engine's certs ok, is6. This bug is currently attached to errata RHEA-2013:15231. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2014-0038.html making the bug public |