[Engine-devel] Adding VNC support

[Alon Bar-Lev]

----- Original Message -----
> From: "Itamar Heim" <iheim at redhat.com>
> To: "Alon Bar-Lev" <alonbl at redhat.com>
> Cc: "Michal Skrivanek" <michal.skrivanek at redhat.com>, engine-devel at ovirt.org
> 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 at redhat.com>
> >> To: "Alon Bar-Lev" <alonbl at redhat.com>
> >> Cc: "Ewoud Kohl van Wijngaarden"
> >> <ewoud+ovirt at kohlvanwijngaarden.nl>, engine-devel at 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 at kohlvanwijngaarden.nl> wrote:
> >>>> On Thu, Jul 26, 2012 at 07:36:43AM -0700,
> >>>> snmishra at linux.vnet.ibm.com wrote:
> >>>>> I am looking at adding VNC support in ovirt. What does the
> >>>>> community
> >>>>> think? Ideas, suggestions, comments?
> >>>> By that I think you mean adding VNC support to the java-based
> >>>> web
> >>>> interface. In that case +1. I can recommend noVNC[1], but you do
> >>>> need a
> >>>> websockets proxy. I can recommend VNCAuthProxy[2] as a
> >>>> programmable
> >>>> 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?
> >>>>
> >>>> [1]: http://kanaka.github.com/noVNC/
> >>>> [2]: https://code.osuosl.org/projects/twisted-vncauthproxy/
> >>>
> >>> Or launch client program via MIME bindings[1] both for Vnc and
> >>> Spice.
> >>> Not as neat as "noVnc" but will work in most scenarios, without
> >>> having
> >>> to maintain the actual console implementation.
> >> I would think there are many people out there who are not able to
> >> use
> >> 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
> >> of
> >> choice
> >
> > Right.
> > Exactly what I think.
> > In time the installation of the client can set up the MIME binding
> > automatically.
> 
> that means patching all the vnc clients iiuc, to set mime for
> multiple
> browser versions?
> 

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 programs.

Regards,
Alon.