----- Original Message ----- > From: "Itamar Heim" <ih...@redhat.com> > To: snmis...@linux.vnet.ibm.com > Cc: engine-devel@ovirt.org > Sent: Tuesday, July 31, 2012 2:18:50 AM > Subject: Re: [Engine-devel] Adding VNC support > > On 07/26/2012 05:36 PM, snmis...@linux.vnet.ibm.com wrote: > > > > Hi, > > > > I am looking at adding VNC support in ovirt. What does the > > community > > think? Ideas, suggestions, comments? > > so to sum this up: > 1. there is the new dialog to open vnc manually. > http://gerrit.ovirt.org/#/c/4790/ > > 2. Alon suggested it should be allowed to open this dialog for spice > as > well, not only for vnc. > > 3. Alon also suggested to have a launch button on that window (or > parallel to it) which will try to launch vnc or spice by returning a > specific mime type response, allowing client to choose the vnc/spice > client to run for this mime type, and passing command line parameters > to > it in the mime type reply. > > 4. provide a vnc xpi/activex wrappers to allow launching it via web > browsers like spice > main limitation of this compared to novnc is you need to do this for > every browser/platform. > > 5. novnc > 5.1 novnc client - i'd start with the one recently pushed to fedora. > https://bugzilla.redhat.com/show_bug.cgi?id=822187 > > 5.2 novnc websocket server - i see three options > > 5.2.1 extend qemu to do this, so novnc can connect to it directly > like > we do today for vnc/spice
One of the requirements we want to eliminate is the need for clients to connect directly to the hypervisor. I think the novnc server should be externally hosted not part of qemu > > 5.2.2 use the python based one from: > https://bugzilla.redhat.com/show_bug.cgi?id=822187 +1 > > 5.2.3 look at a java based websocket solution, assuming easier to > deploy > it as part of webadmin/user portal war than another service (requires > a > bit of research) > looking forward user portal and webadmin would be deployed on > multiple > hosts, so a websockets would need to be deployed next to them. > > from the little i looked at, the various websocket implementations > are > mostly nascent and are not scaleable/robust/etc. > I'd love to be proven wrong, and worth playing with them a bit to > measure that. > > 6. spice.html5 > while very nascent - worth mentioning on this thread and trying to > take > a look: > http://www.spice-space.org/page/Html5 > _______________________________________________ > Engine-devel mailing list > Engine-devel@ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel