Hi Christophe, They share a part of their code-base, primarily in the native implementation. However, Opaque has a substantially reimplemented UI. They both live in the same repository, though, and the plan was to bring them closer together over time. I see aSPICE as analogous to spicy and Opaque as analogous to virt-viewer. Cheers, iordan On Thu, Jan 15, 2015 at 8:22 AM, Christophe Fergeau <cfergeau@redhat.com> wrote:
On Mon, Jan 05, 2015 at 04:17:58PM +0100, Michal Skrivanek wrote:
Thank you, Tomas
----- Original Message -----
From: "i iordanov" <iiordanov@gmail.com> To: "users" <users@ovirt.org>, devel@ovirt.org Cc: "Sphoorti Joglekar" <sphoorti.joglekar@gmail.com> Sent: Thursday, December 25, 2014 11:19:58 PM Subject: Re: [ovirt-users] [ovirt-devel] [RFC] oVirt mobile client
Hey guys,
Thanks for remembering about Opaque. For those who are not familiar with the project, it is an oVirt/RHEV graphics console client which supports the SPICE protocol so far. It uses libgovirt to connect to the oVirt/RHEV API. I also created a separate pure SPICE client (called aSPICE) for Android based on libspice.
It would be nice if I got more feedback from Red Hat developers, but you guys are probably as busy as I am :). The app is getting attention on Google Play and people are using it successfully for their installations, it seems.
I have plans to add the following features to Opaque, time permitting:
- Ability to edit default settings, so that people who connect with console.vv file will be able to configure Audio, keyboard layout, etc. - The ability to allocate VMs from a pool. - The ability to control Audio Playback and Recording separately.
I don't think Opaque needs to get portal-management functionality.
I was contacted by an intern working on movirt (Sphoorti Joglekar, cc-ed), asking whether I would be willing to support a URI Intent scheme that movirt can use to launch aSPICE. I think I already have a pretty well specified URI scheme that may work for the purpose, so we'll see how that goes. I am wondering whether it wouldn't be better to launch aSPICE or Opaque with a console.vv file instead, though. I guess the developers of movirt will have to consider both options.
At any rate, Opaque is far from dead. I'm security supporting it, I just don't find a lot of time to work on additional features.
I am cc-ing Brian Proffitt, because at one point we discussed setting up Opaque as a sub-project of oVirt. I don't know whether there is any interest for that in Red Hat, or any interest at all in supporting mobile clients for oVirt/RHEV, etc. It would be nice to hear an official stance on the topic.
(adding Brian properly this time)
I think it makes sense to add it together with something…though maybe more related to SPICE clients. So adding Christophe for his thoughts…
Opaque seems to be more an oVirt client than a SPICE client, so I'd tend to think it would be a better fit as an oVirt project. aSPICE would fit well together with other SPICE repositories, dunno if these are the same code base or not (?).
On Jan 5, 2015, at 13:38 , Tomas Jelinek <tjelinek@redhat.com> wrote:
One more question - does aSPICE support spice proxy?
libgovirt is not parsing the proxy information at this point, so answer would be no. See http://lists.freedesktop.org/archives/spice-devel/2014-December/018475.html and its followup http://lists.freedesktop.org/archives/spice-devel/2015-January/018609.html
Christophe
-- The conscious mind has only one thread of execution.