Bug 1035719 - Make default VNC console mode configurable
Summary: Make default VNC console mode configurable
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: 3.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.4.0
Assignee: Frantisek Kobzik
QA Contact: Ilanit Stein
URL:
Whiteboard: virt
: 1020406 (view as bug list)
Depends On:
Blocks: 1057994
TreeView+ depends on / blocked
 
Reported: 2013-11-28 10:31 UTC by Frantisek Kobzik
Modified: 2014-12-15 12:46 UTC (History)
7 users (show)

Fixed In Version: ovirt-3.4.0-alpha1
Doc Type: Enhancement
Doc Text:
Feature: This feature adds an (engine-wide) option to configure default VNC client console mode (both SPICE and RDP have this option already). Reason: Enhancement. Result (if any): Now admin can set 'Native' or 'NoVnc' client modes using engine-config via 'ClientModeVncDefault' engine option. If NoVnc is chosen and is not available on the engine (i.e. WebSocketProxy config not set), Native is used as a fallback.
Clone Of:
: 1057994 (view as bug list)
Environment:
Last Closed: 2014-03-31 12:26:52 UTC
oVirt Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


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

Description Frantisek Kobzik 2013-11-28 10:31:24 UTC 
Description of problem:
Add an (engine-wide) option to configure default VNC client
console mode (both SPICE and RDP have this option already).

Reason:
Since there are multiple invocation methods for VNC available, it makes sense to have the default invocation method configurable (as in SPICE and RDP case).
Comment 1 Frantisek Kobzik 2013-11-28 14:02:53 UTC 
Merged U/S as 5371c0815633adc9de37d10e657c31795b38475e
Comment 2 Frantisek Kobzik 2013-12-02 12:58:11 UTC 
*** Bug 1020406 has been marked as a duplicate of this bug. ***
Comment 3 Sandro Bonazzola 2014-01-13 13:56:29 UTC 
oVirt 3.4.0 alpha has been released including the fix for this issue.
Comment 4 Yedidyah Bar David 2014-01-23 10:15:53 UTC 
1. Installed ovirt-engine from 3.4 beta and setup
2. Verified that if creating a VM with display protocol VNC, it defaults to Native client
3. Did 'engine-config -s ClientModeVncDefault=NoVnc' and then 'service ovirt-engine restart'
4. Created a VM with display VNC, started it, opened console, NoVNC was started
Comment 5 Sandro Bonazzola 2014-03-31 12:26:52 UTC 
this is an automated message: moving to Closed CURRENT RELEASE since oVirt 3.4.0 has been released
Note You need to log in before you can comment on or make changes to this bug.