Quoting Itamar Heim <iheim(a)redhat.com>:
On 07/26/2012 05:36 PM, snmishra(a)linux.vnet.ibm.com wrote:
> 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.
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.
I like the idea of being able to launch vnc and spice from the same place.
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
I like the noVNC option better since most modern web browsers support
the canvas element of HTML 5. With noVNC we don't have to port to
5.1 novnc client - i'd start with the one recently pushed to fedora.
that is an added advantage.
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
5.2.2 use the python based one from:
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
I can see myself going either way with java or python based websockets.
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
while very nascent - worth mentioning on this thread and trying to
take a look: