[Engine-devel] Adding VNC support
Michal Skrivanek
michal.skrivanek at redhat.com
Fri Jul 27 09:01:32 UTC 2012
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
>
> Regards,
> Alon.
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=843410
> _______________________________________________
> Engine-devel mailing list
> Engine-devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
More information about the Engine-devel
mailing list