[moVirt] Integrating aSpice with moVirt

Sphoorti Joglekar sphoorti.joglekar at gmail.com
Sun Feb 8 20:14:31 UTC 2015


Hi,

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?


Best Regards,
Sphoorti


On Thu, Dec 11, 2014 at 11:53 PM, i iordanov <iiordanov at gmail.com> wrote:
> Hey,
>
> 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?
>
> Thanks!
> iordan
>
> On Tue, Dec 9, 2014 at 12:28 PM, Sphoorti Joglekar
> <sphoorti.joglekar at 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
>> other.
>> Eagerly awaiting your response.
>>
>>
>> Best Regards,
>> Sphoorti
>>
>> On Tue, Dec 9, 2014 at 10:52 PM, i iordanov <iiordanov at 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.
>>>
>>> Cheers,
>>> iordan
>>>
>>> On Tue, Dec 9, 2014 at 12:13 PM, Sphoorti Joglekar
>>> <sphoorti.joglekar at 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.
>>> >
>>> > https://github.com/iiordanov/remote-desktop-clients/tree/master/eclipse_projects/Opaque
>>> >
>>> > 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.



More information about the moVirt mailing list