Bug 1020406 - Configure default VNC client console mode
Summary: Configure default VNC client console mode
Keywords:
Status: CLOSED DUPLICATE of bug 1035719
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: 3.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Frantisek Kobzik
QA Contact:
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-17 15:31 UTC by Frantisek Kobzik
Modified: 2013-12-02 12:58 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Feature: The feature allows engine-wide configuration of default VNC client mode. Reason: Until now we hadn't any other client console modes for VNC than 'Native'. Now when noVNC has been added, it makes sense to provide this configuration (for SPICE and RDP we already have this configuration).
Clone Of:
Environment:
Last Closed: 2013-12-02 12:58:11 UTC
oVirt Team: ---
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 20222 0 None None None Never

Description Frantisek Kobzik 2013-10-17 15:31:23 UTC 
Feature description:
Add a engine-wide configuration option to set default VNC client console mode (Native, NoVnc). 

Similar configuration has been already present for SPICE and RDP and now, after integrating NoVNC client, it makes sense for VNC as well.
Comment 1 Frantisek Kobzik 2013-12-02 12:58:11 UTC 
I accidentally duplicated this bug. Closing this one.

*** This bug has been marked as a duplicate of bug 1035719 ***
Note You need to log in before you can comment on or make changes to this bug.