[moVirt] Integrating aSpice with moVirt

Wed Feb 11 15:00:57 UTC 2015

Hi iordan,

we are just starting the activity letting the user to pick the proper client. 
If there is none which would handle it, we show a toast showing that please install aSPICE or bVNC (depending if the user connects to SPICE or VNC).

Also in project page (http://wiki.ovirt.org/Project_moVirt) we list bVNC as dependency - aSPICE not yet since the integration is just a proof of concept and not merged yet. 
Once finished, we will list it.

Don't worry, we are integrating your clients, not hiding them ;)

Tomas

----- Original Message -----
> From: "i iordanov" <iiordanov at gmail.com>
> To: "Frantisek Kobzik" <fkobzik at redhat.com>
> Cc: "Sphoorti Joglekar" <sphoorti.joglekar at gmail.com>, movirt at ovirt.org, "Tomas Jelinek" <tjelinek at redhat.com>
> Sent: Wednesday, February 11, 2015 3:18:30 PM
> Subject: Re: [moVirt] Integrating aSpice with moVirt
> 
> Hey Franta,
> 
> Glad to hear it works for you now. I hope your plan is for movirt to
> check whether com.iiordanov.freeaspice or com.iiordanov.aspice is
> installed and direct people to install v.3.7.7 or higher either from
> where I distribute the APK on github or from Google Play.
> 
> I would really appreciate it if my client saw the light of day on
> people's devices and wasn't hidden somewhere within movirt.
> 
> Thanks!
> iordan
> 
> 
> 
> 
> On Wed, Feb 11, 2015 at 3:45 AM, Frantisek Kobzik <fkobzik at redhat.com> wrote:
> > Hi Iordan,
> >
> > We tried this today and it works like a charm :)
> > I'll try to integrate it to moVirt in near future.
> >
> > Thank you very much!
> > Franta.
> >
> > ----- Original Message -----
> > From: "i iordanov" <iiordanov at gmail.com>
> > To: "Frantisek Kobzik" <fkobzik at redhat.com>
> > Cc: "Sphoorti Joglekar" <sphoorti.joglekar at gmail.com>, movirt at ovirt.org
> > Sent: Wednesday, February 11, 2015 7:13:04 AM
> > Subject: Re: [moVirt] Integrating aSpice with moVirt
> >
> > Hi Franta, Sphoorti,
> >
> > I looked at the manifest and the code, and indeed, I had some issues.
> >
> > I've built you a test APK that you can try with an attempt at
> > correcting these issues.
> >
> > The main thing that was fixed was that aSPICE now correctly registers
> > that it supports spice:// URI scheme, not vnc:// URI scheme. In
> > addition, the code now accepts and parses any of three schemes
> > programmatically - vnc, spice, and rdp. It will accept specifying the
> > user/pwd as SpiceUsername and SpicePassword respectively.
> >
> > Finally, IF you choose to set SecurityType in the URI, you'll have to
> > make sure it is set to 1 if you would like to NOT set SpicePassword.
> > Alternatively, you may choose to set SecurityType to 2 and specify an
> > empty SpicePassword in the URI. Not specifying SecurityType saves you
> > from these requirements.
> >
> > Please find the new APK at:
> >
> > https://github.com/iiordanov/remote-desktop-clients/releases/download/v3.7.7/freeaSPICE-3.7.7-final.apk
> >
> > Cheers!
> > iordan
> >
> >
> > On Tue, Feb 10, 2015 at 9:21 AM, Frantisek Kobzik <fkobzik at redhat.com>
> > wrote:
> >> Hello!
> >>
> >> 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
> >>  "spice://our_ip:our_port"
> >>    -> 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 popup appears
> >>    - 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!
> >>
> >> Cheers!
> >> Franta.
> >>
> >> ----- Original Message -----
> >> From: "i iordanov" <iiordanov at gmail.com>
> >> To: "Sphoorti Joglekar" <sphoorti.joglekar at gmail.com>
> >> Cc: movirt at ovirt.org
> >> Sent: Tuesday, February 10, 2015 8:21:43 AM
> >> Subject: Re: [moVirt] Integrating aSpice with moVirt
> >>
> >> Hi Sphoorti,
> >>
> >> 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/getScheme().equals("vnc")/getScheme().equals("spice")/'
> >> bVNC/eclipse_projects/bVNC/src/com/iiordanov/freeaSPICE/RemoteCanvasActivity.java
> >> sed -i 's/VncUsername/SpiceUsername/'
> >> bVNC/eclipse_projects/bVNC/src/com/iiordanov/freeaSPICE/Constants.java
> >> sed -i 's/VncPassword/SpicePassword/'
> >> bVNC/eclipse_projects/bVNC/src/com/iiordanov/freeaSPICE/Constants.java
> >>
> >> 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.
> >>
> >> Cheers!
> >> iordan
> >>
> >> On Sun, Feb 8, 2015 at 3:14 PM, Sphoorti Joglekar
> >> <sphoorti.joglekar at gmail.com> wrote:
> >>> 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.
> >>
> >>
> >>
> >> --
> >> The conscious mind has only one thread of execution.
> >> _______________________________________________
> >> moVirt mailing list
> >> moVirt at ovirt.org
> >> http://lists.ovirt.org/mailman/listinfo/movirt
> >
> >
> >
> > --
> > The conscious mind has only one thread of execution.
> 
> 
> 
> --
> The conscious mind has only one thread of execution.
> 