we tried to run aSPICE from moVirt via intent, this is what we got:
- we used aSPICE from Google Play (3.7.6)
- we spawned a VM with SPICE console without password on port 5900
- in moVirt, we created dummy intent that was executing
-> the system didn't run any application
- when we tried to change the intent url to "vnc://our_ip:our:port"
-> system asks which application we want to run the intent - it displays popup with
two items: bVNC and aSPICE
- when proceed with aSPICE option, aSPICE client will indeed execute, but an error
- that means aSPICE is also paired with "vnc://" intent
(- we were successful with connecting to this VM manually by punching in SPICE server
ip:port from within aSPICE)
Thank you for your work on these cool projects!
----- Original Message -----
From: "i iordanov" <iiordanov(a)gmail.com>
To: "Sphoorti Joglekar" <sphoorti.joglekar(a)gmail.com>
Sent: Tuesday, February 10, 2015 8:21:43 AM
Subject: Re: [moVirt] Integrating aSpice with moVirt
I haven't tested launching aSPICE with an intent, only bVNC.
Are you using aSPICE v3.7.6 from the market, an older version, or a
version that you've built according to the instructions in BUILDING?
If using the version from Google Play, it *should* work. If building
your own, the following changes are necessary:
sed -i 's/VncUsername/SpiceUsername/'
sed -i 's/VncPassword/SpicePassword/'
These values need to be determined programmatically, but for the
moment, they are constants that need to be changed.
Please note that the version in the market has VncUsername and
VncPassword changed to SpiceUsername, and SpicePassword respectively
as you can see above.
Apart from those changes it should function, but like I said, I
haven't tested aSPICE explicitly.
If you would like me to test as well, please provide me a binary of
movirt to save me some time as I am swamped with work at the moment.
On Sun, Feb 8, 2015 at 3:14 PM, Sphoorti Joglekar
Thank you for sharing the vnc specifications document. We were
successful in calling bVnc from movirt. We now wish to extend this
feature for aSpice.
We have tried to connect to a VM using aSPICE filling the needed
params (only IP and port) from inside aSPICE and it worked nice.
When we tried to call it using an intent filling in the params using
the same names as in case of bVNC it did not connect. The aSPICE
client has started though - just refused to connect.
Have you tested aSPICE to be called using an intent? Do we have to do
something specific comparing to what is needed for bVNC?
On Thu, Dec 11, 2014 at 11:53 PM, i iordanov <iiordanov(a)gmail.com> wrote:
> Here is the VNC Spec document that we came up with in concert with a
> principal dev at Dell.
> Can you please look through it and see if it'll do for our purposes?
> Can you please identify which parameters will need to be renamed to
> not be VNC specific but SPICE specific?
> On Tue, Dec 9, 2014 at 12:28 PM, Sphoorti Joglekar
> <sphoorti.joglekar(a)gmail.com> wrote:
>> Hi Iordan,
>> Thank you so much :)
>> Maybe next round you could mentor someone :)
>> It would be great if we could have aSpice and moVirt communicate with each
>> Eagerly awaiting your response.
>> Best Regards,
>> On Tue, Dec 9, 2014 at 10:52 PM, i iordanov <iiordanov(a)gmail.com> wrote:
>>> Hi Sphoorti,
>>> This is a very interesting program you're participating in, I didn't
>>> know of its existence. It's good to see!
>>> Incidentally, very recently, in collaboration with Dell, I added a
>>> very detailed URI scheme support into bVNC (of which aSPICE is a
>>> derivative). I believe with small modifications (spice:// instead of
>>> vnc://), aSPICE can be made to benefit from this new support as well.
>>> Let me ask my contact at Dell whether the URI specification is ready
>>> to be shared, and I can show you what we came up with.
>>> On Tue, Dec 9, 2014 at 12:13 PM, Sphoorti Joglekar
>>> <sphoorti.joglekar(a)gmail.com> wrote:
>>> > Hi,
>>> > I am Sphoorti Joglekar, an OPW intern for oVirt.( http://gnome.org/opw/
>>> > )
>>> > My OPW project is working on moVirt, an android application, to manage
>>> > and
>>> > monitor oVirt's datacentre.
>>> > As a part of the extending the project, we are looking for integrating
>>> > moVirt with aSpice. Are there any intents for aSpice which can be used
>>> > with
>>> > moVirt?
>>> > Can aSpice be used from other applications? Could you guide us in this
>>> > matter?
>>> > We have been looking at this github repository for reference.
>>> > Looking forward to hear from you.
>>> > Best Regards,
>>> > Sphoorti
>>> The conscious mind has only one thread of execution.
> The conscious mind has only one thread of execution.
The conscious mind has only one thread of execution.
moVirt mailing list