From: "Itamar Heim" <iheim(a)redhat.com>
To: "Alon Bar-Lev" <alonbl(a)redhat.com>
Cc: "Michal Skrivanek" <michal.skrivanek(a)redhat.com>,
Sent: Saturday, July 28, 2012 7:36:17 AM
Subject: Re: [Engine-devel] Adding VNC support
On 07/28/2012 03:31 AM, Alon Bar-Lev wrote:
> ----- Original Message -----
>> From: "Michal Skrivanek" <michal.skrivanek(a)redhat.com>
>> To: "Alon Bar-Lev" <alonbl(a)redhat.com>
>> Cc: "Ewoud Kohl van Wijngaarden"
>> <ewoud+ovirt(a)kohlvanwijngaarden.nl>, engine-devel(a)ovirt.org
>> Sent: Friday, July 27, 2012 12:01:32 PM
>> Subject: Re: [Engine-devel] Adding VNC support
>> On Jul 26, 2012, at 16:55 , Alon Bar-Lev wrote:
>>> On Thu, Jul 26, 2012 at 5:51 PM, Ewoud Kohl van Wijngaarden
>>> <ewoud+ovirt(a)kohlvanwijngaarden.nl> wrote:
>>>> On Thu, Jul 26, 2012 at 07:36:43AM -0700,
>>>> snmishra(a)linux.vnet.ibm.com wrote:
>>>>> I am looking at adding VNC support in ovirt. What does the
>>>>> think? Ideas, suggestions, comments?
>>>> By that I think you mean adding VNC support to the java-based
>>>> interface. In that case +1. I can recommend noVNC, but you do
>>>> need a
>>>> websockets proxy. I can recommend VNCAuthProxy as a
>>>> proxy with a JSON control channel. On the plus side all
>>>> dependencies are
>>>> in fedora/epel. Downside is no IPv6 support. Maybe you can also
>>>> write a
>>>> pure java implementation integrate this into the engine itself?
>>>> : http://kanaka.github.com/noVNC/
>>>> : https://code.osuosl.org/projects/twisted-vncauthproxy/
>>> Or launch client program via MIME bindings both for Vnc and
>>> Not as neat as "noVnc" but will work in most scenarios, without
>>> to maintain the actual console implementation.
>> I would think there are many people out there who are not able to
>> current spice client, or not willing to(hate switching from chrome
>> to firefox:-)
>> Sure they can set up things manually but it would be way more
>> convenient to allow a simple external launch of their VNC client
> Exactly what I think.
> In time the installation of the client can set up the MIME binding
that means patching all the vnc clients iiuc, to set mime for
At first we provide support at the engine side, and user get it manually:
User will get a dialog:
"(o) Open File"
"( ) Download"
When selecting "Open File" he will need to choose a program.
Initially we will provide programs (scripts) for both vnc and spice.
Then after user are satisfied we offer these programs to the appropriate upstream.
Best case: will be accepted (maybe with modifications).
Worse case: will be rejected so we provide engine-console package to our users with these