On 10/13/2013 02:49 PM, Bob wrote:
Hi,
I'm exploring thin client connections to oVirt in a VDI context, and
after having read the overviews I've found I still have some questions,
and hope you can point me to the right place for more information.
It appears that oVirt supports a VDI model where thin client sessions
can be load balanced to a set of VMs, or directed to VMs with existing
sessions for the user. Is this correct?
they can get a VM from a pool or a specific VM.
At what level of the architecture does the connection brokering take
place (i.e. where is it determined which VM a thin client should be
connected to, and what pieces of the system are involved)? Can it work
for both VNC and SPICE based clients?
vnc, spice or rdp.
rdp is to the guest.
vnc and spice to the host, or for spice via a proxy, or for
novnc/spice.html5 via a websocket proxy.
If a developer were interested in adding support for connection
brokering of new thin client protocols, where would they start looking?
can you elaborate on which protocol? is it to the host (qemu), or to the
guest?
Pointers to relevant documentation or mailing lists would be much
appreciated. Is this more of an engine or a node question (or does it
span both)?
Thanks!
-Bob Doolittle
_______________________________________________
Arch mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/arch
_______________________________________________
Arch mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/arch
