--7uYPyRQQ5N0D02nI
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Jan 05, 2015 at 04:17:58PM +0100, Michal Skrivanek wrote:
=20
> Thank you,
> Tomas
>=20
> ----- Original Message -----
>> From: "i iordanov" <iiordanov(a)gmail.com>
>> To: "users" <users(a)ovirt.org>, devel(a)ovirt.org
>> Cc: "Sphoorti Joglekar" <sphoorti.joglekar(a)gmail.com>
>> Sent: Thursday, December 25, 2014 11:19:58 PM
>> Subject: Re: [ovirt-users] [ovirt-devel] [RFC] oVirt mobile client
>>=20
>> Hey guys,
>>=20
>> 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.
>>=20
>> 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.
>>=20
>> I have plans to add the following features to Opaque, time permitting:
>>=20
>> - 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.
>>=20
>> I don't think Opaque needs to get portal-management functionality.
>>=20
>> 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.
>>=20
>> 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.
>>=20
>> 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.
=20
(adding Brian properly this time)
=20
I think it makes sense to add it together with something=E2=80=A6though m=
aybe
more related to SPICE clients. So adding Christophe for his
thoughts=E2=
=80=A6
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(a)redhat.com>
wrote:
>=20
> One more question - does aSPICE support spice proxy?
>=20
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
--7uYPyRQQ5N0D02nI
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJUt78jAAoJEKnYwhQprGyCF+0QAJDuW5oYH1hxhuNURVtPIYQD
yyYGUSfmXdw8Bc+M9GBweicKd00Mv4WzZbHxSYU0PoJOYzc7nIZ8tNwBigM4jP6Z
lO604gIdhPW7QVMerEKcUDszr0c8J0mNhR6zEUffRcwFGaep2BXfCpBwKOqqvMFm
frDnpMuqUuRzCj3LR8+JO00l2z1HuuJQQ7QYdrBpNXRnHSD+3DAfLG7YhrxMoC3z
xJLtaGkv/CqZHP+j/bkKe/qh9f7kO7ww0SGjN+45+279vt6TU68t9dQuxNfcxBie
rNpsxuSN/62bbn9s58BsgFgho/nx22wljz2a6Q6P/sfDMGY840DwxPppMCETotas
I8gX2sWe4VXjc5PvmBTMzU7w/q7EPrYapZkaTO0V0+pv7icfzTg3sTpSlCuGxDph
xl4IvKOn/0377uSw63HvTSZkqcJK+ywH3KobyDDq1K/KQwD0EToE65cyfVuT+I84
fWFb6VdAtokZbNobuwDmHgiiLUWDzw4QuUHKyDrYCuGTgoUkXcojANqEOfp6lqYK
KMsqfj0C7ZaSZr95cTPal7wIVPGqJeRfGm8VcK9kCuYkAxEV9xp3BEFbopvdPUQ7
dWXADuuYJk0aqDd/U2iV5AmC+IP01ZFIQkcI0wACoLAw5pJlPlhluBFcJDXnVl2V
EOXr/HuARRVch49pOnPf
=gOzP
-----END PGP SIGNATURE-----
--7uYPyRQQ5N0D02nI--