February 2015 - moVirt - oVirt List Archives

Re: [moVirt] [ovirt-devel] [ovirt-users] Announcing the moVirt Incubator Project!
by Tomas Jelinek 20 Feb '15

20 Feb '15

Well, this is quite a milestone! Thanx everyone! ----- Original Message ----- > From: "Donny D" <donny(a)cloudspin.me> > To: "Brian Proffitt" <bproffit(a)redhat.com>, "board" <board(a)ovirt.org> > Cc: announce(a)ovirt.org, "users" <users(a)ovirt.org>, devel(a)ovirt.org > Sent: Tuesday, February 17, 2015 5:31:29 PM > Subject: Re: [ovirt-devel] [ovirt-users] Announcing the moVirt Incubator Project! > > That is great project. This makes me very happy. BTW we have been and are still heavily using your cloudspin.me during moVirt development and testing. Wanted to use this opportunity to thank you for the great service! > > > > Happy Connecting. Sent from my Sprint Samsung Galaxy S® 5 > > > -------- Original message -------- > From: Brian Proffitt <bproffit(a)redhat.com> > Date: 02/17/2015 9:17 AM (GMT-07:00) > To: board <board(a)ovirt.org> > Cc: announce(a)ovirt.org, users <users(a)ovirt.org>, devel(a)ovirt.org > Subject: [ovirt-users] Announcing the moVirt Incubator Project! > > This message is to announce moVirt as a new oVirt incubator project, approved > by unanimous vote of the Board mailing list! > > Details about the project can be found at > > http://www.ovirt.org/Project_moVirt > > More information about the incubator at oVirt can be found at > > http://www.ovirt.org/Incubating_an_oVirt_Subproject > > Please check out this project and see what you can do to help! > > -- > Brian Proffitt > > Community Liaison > oVirt > Open Source and Standards, Red Hat - http://community.redhat.com > Phone: +1 574 383 9BKP > IRC: bkp @ OFTC > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > _______________________________________________ > Devel mailing list > Devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel

3 2

Re: [moVirt] Integrating aSpice with moVirt
by Frantisek Kobzik 12 Feb '15

12 Feb '15

Hi Iordan, RDP is implemented in slightly different way in oVirt engine and I don't know if moVirt pulls all data needed for RDP from the engine. I'll take a look right after I deal with SPICE in moVirt. Thanks! Franta. ----- Original Message ----- From: "i iordanov" <iiordanov(a)gmail.com> To: "Tomas Jelinek" <tjelinek(a)redhat.com> Cc: "Frantisek Kobzik" <fkobzik(a)redhat.com>, "Sphoorti Joglekar" <sphoorti.joglekar(a)gmail.com>, movirt(a)ovirt.org Sent: Thursday, February 12, 2015 2:17:30 AM Subject: Re: [moVirt] Integrating aSpice with moVirt Hi Tomas, Thank you very much. Do you plan to use aRDP for Windows VMs that have a RDP console in a similar fashion? If so, I'll have to create a new version of aRDP with the fixes outlined above for you. Sincerely, iordan On Wed, Feb 11, 2015 at 10:00 AM, Tomas Jelinek <tjelinek(a)redhat.com> wrote: > 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(a)gmail.com> >> To: "Frantisek Kobzik" <fkobzik(a)redhat.com> >> Cc: "Sphoorti Joglekar" <sphoorti.joglekar(a)gmail.com>, movirt(a)ovirt.org, "Tomas Jelinek" <tjelinek(a)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(a)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(a)gmail.com> >> > To: "Frantisek Kobzik" <fkobzik(a)redhat.com> >> > Cc: "Sphoorti Joglekar" <sphoorti.joglekar(a)gmail.com>, movirt(a)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.… >> > >> > Cheers! >> > iordan >> > >> > >> > On Tue, Feb 10, 2015 at 9:21 AM, Frantisek Kobzik <fkobzik(a)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(a)gmail.com> >> >> To: "Sphoorti Joglekar" <sphoorti.joglekar(a)gmail.com> >> >> Cc: movirt(a)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(a)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(a)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(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 >> >>>>> other. >> >>>>> Eagerly awaiting your response. >> >>>>> >> >>>>> >> >>>>> Best Regards, >> >>>>> Sphoorti >> >>>>> >> >>>>> 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. >> >>>>>> >> >>>>>> Cheers, >> >>>>>> iordan >> >>>>>> >> >>>>>> 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. >> >>>>>> > >> >>>>>> > https://github.com/iiordanov/remote-desktop-clients/tree/master/eclipse_pro… >> >>>>>> > >> >>>>>> > 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(a)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. >> -- The conscious mind has only one thread of execution.

1 0

Re: [moVirt] Integrating aSpice with moVirt
by Tomas Jelinek 11 Feb '15

11 Feb '15

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(a)gmail.com> > To: "Frantisek Kobzik" <fkobzik(a)redhat.com> > Cc: "Sphoorti Joglekar" <sphoorti.joglekar(a)gmail.com>, movirt(a)ovirt.org, "Tomas Jelinek" <tjelinek(a)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(a)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(a)gmail.com> > > To: "Frantisek Kobzik" <fkobzik(a)redhat.com> > > Cc: "Sphoorti Joglekar" <sphoorti.joglekar(a)gmail.com>, movirt(a)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.… > > > > Cheers! > > iordan > > > > > > On Tue, Feb 10, 2015 at 9:21 AM, Frantisek Kobzik <fkobzik(a)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(a)gmail.com> > >> To: "Sphoorti Joglekar" <sphoorti.joglekar(a)gmail.com> > >> Cc: movirt(a)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(a)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(a)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(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 > >>>>> other. > >>>>> Eagerly awaiting your response. > >>>>> > >>>>> > >>>>> Best Regards, > >>>>> Sphoorti > >>>>> > >>>>> 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. > >>>>>> > >>>>>> Cheers, > >>>>>> iordan > >>>>>> > >>>>>> 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. > >>>>>> > > >>>>>> > https://github.com/iiordanov/remote-desktop-clients/tree/master/eclipse_pro… > >>>>>> > > >>>>>> > 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(a)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. >

1 0

Re: [moVirt] Integrating aSpice with moVirt
by Frantisek Kobzik 11 Feb '15

11 Feb '15

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(a)gmail.com> To: "Frantisek Kobzik" <fkobzik(a)redhat.com> Cc: "Sphoorti Joglekar" <sphoorti.joglekar(a)gmail.com>, movirt(a)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.… Cheers! iordan On Tue, Feb 10, 2015 at 9:21 AM, Frantisek Kobzik <fkobzik(a)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(a)gmail.com> > To: "Sphoorti Joglekar" <sphoorti.joglekar(a)gmail.com> > Cc: movirt(a)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(a)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(a)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(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 >>>> other. >>>> Eagerly awaiting your response. >>>> >>>> >>>> Best Regards, >>>> Sphoorti >>>> >>>> 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. >>>>> >>>>> Cheers, >>>>> iordan >>>>> >>>>> 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. >>>>> > >>>>> > https://github.com/iiordanov/remote-desktop-clients/tree/master/eclipse_pro… >>>>> > >>>>> > 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(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/movirt -- The conscious mind has only one thread of execution.

1 0

Re: [moVirt] Integrating aSpice with moVirt
by Sphoorti Joglekar 10 Feb '15

10 Feb '15

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(a)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(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 >> other. >> Eagerly awaiting your response. >> >> >> Best Regards, >> Sphoorti >> >> 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. >>> >>> Cheers, >>> iordan >>> >>> 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. >>> > >>> > https://github.com/iiordanov/remote-desktop-clients/tree/master/eclipse_pro… >>> > >>> > 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.

3 2

Re: [moVirt] Some thoughts about moVirt
by Tomas Jelinek 10 Feb '15

10 Feb '15

----- Original Message ----- > From: "Yair Zaslavsky" <yzaslavs(a)redhat.com> > To: "Martin Polednik" <mpolednik(a)redhat.com> > Cc: "Tomas Jelinek" <tjelinek(a)redhat.com>, "Greg Sheremeta" <gshereme(a)redhat.com>, "Martin Betak" > <mbetak(a)redhat.com>, "Doron Fediuck" <doron(a)redhat.com>, "sphoorti joglekar" <sphoorti.joglekar(a)gmail.com>, > movirt(a)ovirt.org > Sent: Monday, February 9, 2015 2:31:08 PM > Subject: Re: Some thoughts about moVirt > > > > ----- Original Message ----- > > From: "Martin Polednik" <mpolednik(a)redhat.com> > > To: "Tomas Jelinek" <tjelinek(a)redhat.com> > > Cc: "Yair Zaslavsky" <yzaslavs(a)redhat.com>, "Greg Sheremeta" > > <gshereme(a)redhat.com>, "Martin Betak" > > <mbetak(a)redhat.com>, "Doron Fediuck" <doron(a)redhat.com>, "sphoorti > > joglekar" <sphoorti.joglekar(a)gmail.com>, > > movirt(a)ovirt.org > > Sent: Monday, February 9, 2015 12:58:36 PM > > Subject: Re: Some thoughts about moVirt > > > > > > > > ----- Original Message ----- > > > From: "Tomas Jelinek" <tjelinek(a)redhat.com> > > > To: "Yair Zaslavsky" <yzaslavs(a)redhat.com> > > > Cc: "Greg Sheremeta" <gshereme(a)redhat.com>, "Martin Betak" > > > <mbetak(a)redhat.com>, "Doron Fediuck" <doron(a)redhat.com>, > > > "sphoorti joglekar" <sphoorti.joglekar(a)gmail.com>, "Martin Polednik" > > > <mpoledni(a)redhat.com>, movirt(a)ovirt.org > > > Sent: Monday, February 9, 2015 8:03:19 AM > > > Subject: Re: Some thoughts about moVirt > > > > > > (adding martin and movirt list - rest inline) > > > > > > ----- Original Message ----- > > > > From: "Yair Zaslavsky" <yzaslavs(a)redhat.com> > > > > To: "Greg Sheremeta" <gshereme(a)redhat.com> > > > > Cc: "Martin Betak" <mbetak(a)redhat.com>, "Doron Fediuck" > > > > <doron(a)redhat.com>, > > > > "sphoorti joglekar" > > > > <sphoorti.joglekar(a)gmail.com>, "Tomas Jelinek" <tjelinek(a)redhat.com> > > > > Sent: Sunday, February 8, 2015 3:37:46 PM > > > > Subject: Re: Some thoughts about moVirt > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > From: "Greg Sheremeta" <gshereme(a)redhat.com> > > > > > To: "Yair Zaslavsky" <yzaslavs(a)redhat.com> > > > > > Cc: "Martin Betak" <mbetak(a)redhat.com>, "Doron Fediuck" > > > > > <doron(a)redhat.com>, > > > > > "sphoorti joglekar" > > > > > <sphoorti.joglekar(a)gmail.com>, "Tomas Jelinek" <tjelinek(a)redhat.com> > > > > > Sent: Sunday, February 8, 2015 4:27:22 PM > > > > > Subject: Re: Some thoughts about moVirt > > > > > > > > > > ----- Original Message ----- > > > > > > From: "Yair Zaslavsky" <yzaslavs(a)redhat.com> > > > > > > To: "Martin Betak" <mbetak(a)redhat.com>, "Greg Sheremeta" > > > > > > <gshereme(a)redhat.com> > > > > > > Cc: "Doron Fediuck" <doron(a)redhat.com> > > > > > > Sent: Sunday, February 8, 2015 2:12:20 AM > > > > > > Subject: Some thoughts about moVirt > > > > > > > > > > > > 1. I will be glad to see a wiki page on how I can get involved with > > > > > > moVirt. > > > > > > For example, I have a new galaxy note4 phone. I will get soon a > > > > > > "monster > > > > > > machine" with 16 gigs, and some SSD, and 1 TB disk on it. Ok, I can > > > > > > install > > > > > > ovirt all-in-one on it, now what? > > > > > > I don't even know how to configure browsing via the mobile device > > > > > > to > > > > > > my > > > > > > home > > > > > > network (i.e - access my mahcine) - yes, i know this is not a > > > > > > "strictly > > > > > > moVirt" problem, but if you provide this info it will ease others > > > > > > to > > > > > > start > > > > > > developing. I would like to know how I can start contributing to > > > > > > moVirt. > > > > > > > > > > > > 2. Maybe I missed it - what is the decision about the technology? > > > > > > Native > > > > > > Java > > > > > > ? Cordova? Something else? If native, maybe we should encourage > > > > > > somehow > > > > > > others to start porting to IOS/ Windows Phone, etc? > > > > > > > > > > > > > > > > > > Cheers, > > > > > > Yair > > > > > > > > > > > > > > > > > > > > > > Adding Sphoorti and Tomas, as they are running this show :) > > > > > > > > Oops, sorry for that. > > > > > > > > > > > > > > 1. 16 GB is not "monster" -- better put 32 or 64 in it :D > > > > > I think Sphoorti has already worked on some documentation, and may > > > > > have > > > > > plans > > > > > to do more? > > > > > > > > Yeah, so as I wrote down, if I have let's say some modem + router at > > > > home, > > > > how can I work against my "all-in-one" ovirt installation? > > > > > > Well, if both your phone and your monster machine is connected to the > > > same > > > router you are both on the same network. So if you can not see oVirt from > > > mobile, there is some problem with firewall on the all-in-one. > > > > > > On https://github.com/matobet/moVirt is the project page. It contains the > > > sources, an unsigned build you can install to play with, some > > > documentation > > > on how to setup movirt and also how to setup the devel env. > > > Ping us all the time if you have any issues setting it up. But please > > > make > > > sure you are using exactly the versions of everything as stated on wiki - > > > any change in gradle or android-studio can have fatal consequences :D > > > > > > Connecting to your environment - well, you need to have access to the > > > engine's REST API from your phone. Than in the moVirt you just need to > > > fill > > > the API URL, name and password. > > > Connecting securely using https is a bit tricky - you need to have the CA > > > cert imported to your phone and connect to REST using the proper URL as > > > stated in the cert. > > > For devel env you can use the HTTPS and pick the "Disable HTTPS" - it > > > will > > > not check the cert and will work without proper url (e.g. with IP) and > > > without cert imported. > > > > > > > > > > > > > > > > > > > > > 2. The decision was native Java. For now, afaik, iOS isn't being > > > > > considered. > > > > > Windows Phone is not popular, but it might be more popular among > > > > > server > > > > > admin types? Not sure. > > > > > > Currently Android and surprisingly it works nice as-is on blackberry :) > > > Even > > > the devel env with debugger etc(!!!) > > > Martin (Polednik) was considering to port it to iOS, not sure - Martin? > > > Also a friend of Sphoorti (the current OPW intern) is very insterested in > > > porting it to iOS as a different OPW. But this is very uncertain - not > > > sure > > > who could lead her and not sure about funding etc... > > > > Heya, > > I'm looking into building native iOS oVirt app, so far I've started > > designing > > the storyboard (UI) and interaction. Some of the decisions were going with > > objective-C (due to internal hate for swift) and going iPhone only as the > > first > > iteration target in order to get the UI as iOSy as possible. > > > > But I have to admit that my experience with iOS or mobile development > > overall > > is quite limited, so I see no issues with either joint efforts or > > developing > > two apps and seeing which one is more suited for iVirt. :) > > What about porting of spice client to IOS? there are issues even on android with it :) I'd say it would be a lot of work porting it for not too much gain - we have the option of VNC. And until we don't have the client itself, I don't see too much point in porting a console for it. > > > > > > > > > > > Ok, good to know. > > > > > > > > > > Greg > > > > > > > > > > > > > > >

4 8

Re: [moVirt] Some thoughts about moVirt
by Tomas Jelinek 09 Feb '15

09 Feb '15

(adding martin and movirt list - rest inline) ----- Original Message ----- > From: "Yair Zaslavsky" <yzaslavs(a)redhat.com> > To: "Greg Sheremeta" <gshereme(a)redhat.com> > Cc: "Martin Betak" <mbetak(a)redhat.com>, "Doron Fediuck" <doron(a)redhat.com>, "sphoorti joglekar" > <sphoorti.joglekar(a)gmail.com>, "Tomas Jelinek" <tjelinek(a)redhat.com> > Sent: Sunday, February 8, 2015 3:37:46 PM > Subject: Re: Some thoughts about moVirt > > > > ----- Original Message ----- > > From: "Greg Sheremeta" <gshereme(a)redhat.com> > > To: "Yair Zaslavsky" <yzaslavs(a)redhat.com> > > Cc: "Martin Betak" <mbetak(a)redhat.com>, "Doron Fediuck" <doron(a)redhat.com>, > > "sphoorti joglekar" > > <sphoorti.joglekar(a)gmail.com>, "Tomas Jelinek" <tjelinek(a)redhat.com> > > Sent: Sunday, February 8, 2015 4:27:22 PM > > Subject: Re: Some thoughts about moVirt > > > > ----- Original Message ----- > > > From: "Yair Zaslavsky" <yzaslavs(a)redhat.com> > > > To: "Martin Betak" <mbetak(a)redhat.com>, "Greg Sheremeta" > > > <gshereme(a)redhat.com> > > > Cc: "Doron Fediuck" <doron(a)redhat.com> > > > Sent: Sunday, February 8, 2015 2:12:20 AM > > > Subject: Some thoughts about moVirt > > > > > > 1. I will be glad to see a wiki page on how I can get involved with > > > moVirt. > > > For example, I have a new galaxy note4 phone. I will get soon a "monster > > > machine" with 16 gigs, and some SSD, and 1 TB disk on it. Ok, I can > > > install > > > ovirt all-in-one on it, now what? > > > I don't even know how to configure browsing via the mobile device to my > > > home > > > network (i.e - access my mahcine) - yes, i know this is not a "strictly > > > moVirt" problem, but if you provide this info it will ease others to > > > start > > > developing. I would like to know how I can start contributing to moVirt. > > > > > > 2. Maybe I missed it - what is the decision about the technology? Native > > > Java > > > ? Cordova? Something else? If native, maybe we should encourage somehow > > > others to start porting to IOS/ Windows Phone, etc? > > > > > > > > > Cheers, > > > Yair > > > > > > > > > > Adding Sphoorti and Tomas, as they are running this show :) > > Oops, sorry for that. > > > > > 1. 16 GB is not "monster" -- better put 32 or 64 in it :D > > I think Sphoorti has already worked on some documentation, and may have > > plans > > to do more? > > Yeah, so as I wrote down, if I have let's say some modem + router at home, > how can I work against my "all-in-one" ovirt installation? Well, if both your phone and your monster machine is connected to the same router you are both on the same network. So if you can not see oVirt from mobile, there is some problem with firewall on the all-in-one. On https://github.com/matobet/moVirt is the project page. It contains the sources, an unsigned build you can install to play with, some documentation on how to setup movirt and also how to setup the devel env. Ping us all the time if you have any issues setting it up. But please make sure you are using exactly the versions of everything as stated on wiki - any change in gradle or android-studio can have fatal consequences :D Connecting to your environment - well, you need to have access to the engine's REST API from your phone. Than in the moVirt you just need to fill the API URL, name and password. Connecting securely using https is a bit tricky - you need to have the CA cert imported to your phone and connect to REST using the proper URL as stated in the cert. For devel env you can use the HTTPS and pick the "Disable HTTPS" - it will not check the cert and will work without proper url (e.g. with IP) and without cert imported. > > > > > > 2. The decision was native Java. For now, afaik, iOS isn't being > > considered. > > Windows Phone is not popular, but it might be more popular among server > > admin types? Not sure. Currently Android and surprisingly it works nice as-is on blackberry :) Even the devel env with debugger etc(!!!) Martin (Polednik) was considering to port it to iOS, not sure - Martin? Also a friend of Sphoorti (the current OPW intern) is very insterested in porting it to iOS as a different OPW. But this is very uncertain - not sure who could lead her and not sure about funding etc... > > Ok, good to know. > > > > Greg > > >

2 1

new movirt video
by Tomas Jelinek 05 Feb '15

05 Feb '15

Hey Group! A new video about moVirt has been uploaded to youtube, check it out :) https://www.youtube.com/watch?v=QnD9v70oefA Tomas

1 0