- moVirt - oVirt List Archives

Android Studio Security Alert: Update to Android Studio 2.1.1
by Android Studio Developer Support 16 May '16

16 May '16

Dear Android Studio Developer, As an app developer on Google Play, we wanted to make you aware of an important security update for Android Studio. On May 11th, we released the Android Studio 2.1.1 update. This incremental update addresses a security vulnerability in the underlying IntelliJ platform that affects all previous versions of Android Studio. The vulnerability concerns the IDE itself and has no effect on individual apps. Please update to Android Studio 2.1.1 as soon as possible. More information about the vulnerability can be found in this G+ posting. JetBrains has also released more details on the vulnerability. To address this security vulnerability, simply go into Android Studio and check updates. For OS X users, navigate to the Android Studio Menu and click Check for Updates. For Windows or Linux users, navigate to the Help menu and click Check for Updates. You should be running at least Android Studio 2.1.1. The update message was sent as a in-product notification to all users of Android Studio. If you want a new install, you can download v2.1.1 from the Android Studio website. If you're still using v1.5.x and not able to switch to v2.x immediately, please download Android Studio v1.5.2 from the Android Studio tools website. Regards, The Android Studio Team ©2016 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043 Email preferences: You have received this mandatory email service announcement to update you about important changes to your Google Play account.

1 0

Neha Agarwal's invitation is awaiting your response
by Neha Agarwal via LinkedIn 06 Apr '16

06 Apr '16

Neha Agarwal would like to connect on LinkedIn. How would you like to respond? Accept: https://www.linkedin.com/e/v2?e=-val0r3-imolbqxw-wx&a=preRegInvite&ek=secon… View Neha Agarwal's profile: https://www.linkedin.com/e/v2?e=-val0r3-imolbqxw-wx&a=preRegInvite&ek=secon… You received an invitation to connect. LinkedIn will use your email address to make suggestions to our members in features like People You May Know. Unsubscribe here: https://www.linkedin.com/e/v2?e=-val0r3-imolbqxw-wx&t=lun&midToken=AQFmrFVh… This email was sent to movirt(a)ovirt.org. If you need assistance or have questions, please contact LinkedIn Customer Service: https://www.linkedin.com/e/v2?e=-val0r3-imolbqxw-wx&a=customerServiceUrl&ek… © 2016 LinkedIn Corporation, 2029 Stierlin Court, Mountain View CA 94043. LinkedIn and the LinkedIn logo are registered trademarks of LinkedIn.

1 0

Neha Agarwal's invitation is awaiting your response
by Neha Agarwal via LinkedIn 30 Mar '16

30 Mar '16

Neha Agarwal would like to connect on LinkedIn. How would you like to respond? Accept: https://www.linkedin.com/e/v2?e=-val0r3-imel0znf-m&a=preRegInvite&ek=first_… View Neha Agarwal's profile: https://www.linkedin.com/e/v2?e=-val0r3-imel0znf-m&a=preRegInvite&ek=first_… You received an invitation to connect. LinkedIn will use your email address to make suggestions to our members in features like People You May Know. Unsubscribe here: https://www.linkedin.com/e/v2?e=-val0r3-imel0znf-m&t=lun&midToken=AQFmrFVhG… This email was sent to movirt(a)ovirt.org. If you need assistance or have questions, please contact LinkedIn Customer Service: https://www.linkedin.com/e/v2?e=-val0r3-imel0znf-m&a=customerServiceUrl&ek=… © 2016 LinkedIn Corporation, 2029 Stierlin Court, Mountain View CA 94043. LinkedIn and the LinkedIn logo are registered trademarks of LinkedIn.

1 0

Hi from Neha
by Neha Agarwal 23 Mar '16

23 Mar '16

Hey, Discover high quality jobs and connect with recruiters on LinkedIn. - Neha Accept invite: https://www.linkedin.com/e/v2?e=0-im50lj73-8g&t=ssuw&ek=invite_guest&li=14&… You received an invitation to connect. LinkedIn will use your email address to make suggestions to our members in features like People You May Know. Unsubscribe here: https://www.linkedin.com/e/v2?e=0-im50lj73-8g&t=lun&midToken=AQFmrFVhGEd36Q… This email was sent to movirt(a)ovirt.org. If you need assistance or have questions, please contact LinkedIn Customer Service: https://www.linkedin.com/e/v2?e=0-im50lj73-8g&a=customerServiceUrl&ek=invit… © 2016 LinkedIn Corporation, 2029 Stierlin Court, Mountain View CA 94043. LinkedIn and the LinkedIn logo are registered trademarks of LinkedIn.

1 0

Google Play Developer Program Policy Update
by Google Play 01 Mar '16

01 Mar '16

Hello Google Play Developer, We're excited to announce the launch of a redesigned Google Play Developer Policy Center, an online resource which strives to provide developers with greater transparency and insight into our program policies. This redesign includes a new organizational structure for the Developer Program Policies, which are now grouped into six themes. We've also introduced detailed guidelines and visual examples to help you better understand the policies. In our continuing effort to make Google Play the most trusted community for developers and consumers, we also took this opportunity to update a few policies in accordance with current practices. This email is to notify you of the latest changes to our policies, a few of which are highlighted below. We've updated our Ads policy to prohibit inappropriate ads. We've clarified our Ads policy to prohibit certain ad behaviors that interfere with device functionality. We've introduced restrictions on apps that try to bypass system power management features under the Device and Network Abuse policy. We've clarified our User Data policy to include a privacy policy requirement when collecting contact/phonebook data. Any new apps or app updates published after this notification will be immediately subject to the latest version of the Developer Program Policy. If you find any existing apps in your catalog that don't comply, we ask that you unpublish the app, or fix and republish the app within 30 calendar days of receiving this email. After this period, existing apps discovered to be in violation may be subject to warning or removal from Google Play. Thanks for partnering with us to deliver the world's most innovative and trusted apps to over a billion Google Play users. We're always looking for feedback, so please take a minute to check out the new site and tell us what you think! Thanks for supporting Google Play, The Google Play Team ©2016 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043 Email preferences: You have received this mandatory email service announcement to update you about important changes to your Google Play service or account.

1 0

Proposed prototypes for UI enhancements
by Neha Agarwal 22 Oct '15

22 Oct '15

Hello everyone, I've made some prototypes for changes to the existing UI of the application. These shall make the content look clearer and give a better user experience. As these are rough prototypes, the actual coded app will be much better in terms of positioning, color and feel. Please go to the following link: https://ninjamock.com/s/6R43T Neha Agarwal.

2 5

Feature page for Doctor Rest Integration
by Martin Betak 08 Sep '15

08 Sep '15

Hi All, During the implementation of the moVirt project [1], a client frontend communicating with the oVirt engine purely via REST-API, many shortcomings of this approach surfaced. Namely: * Need for periodic polling: absence of any push notifications (especially bad for monitoring clients whose main purpose is to display current dashboard-like overview of the system.) * Even when polling need to issue excessive amounts of HTTP requests (list of entities and then have to individually query each entity's sub-resources). * Very limited and ad-hoc support for data-aggregation (just VMs' statistics/disks/nics and Hosts' statistics) * No support for finer grained selection of data client is actually interested in - always have to fetch full VM entitties only when we are actually interested in only a handful of fields. To address the above shortcomings, and improve user experience for our mobile users and of our future frontend, the Doctor REST project [2] was created to solve the above concerns in a generic way that is agnostic of any specific data-format or backend architecture so it can be used by anyone who wishes to add Doctor's capabilities to their project. The feature page [3] should track progress of this integration effort and status of necessary engine patches. To find more information about the overall design of Doctor REST, please see the linked wiki page [3], README of the github repo [2] or the attached presentation that was given to the UX team this summer. I still need to update the project's README to new overhauled authentication architecture (designed to work with oVirt SSO), but your questions, suggestions and other remarks are very welcome. Thank you and best regards, Martin Betak [1] https://github.com/matobet/moVirt [2] https://github.com/matobet/doctor-rest [3] http://www.ovirt.org/Features/Doctor_REST

1 0

Re: [moVirt] Replace the current search box with something nicer (#107)
by Jakub Niedermertl 31 Aug '15

31 Aug '15

He Sphoorti, Neha, if you want debug the problem of stuck vm, you can attach an ISO of same system you are running in the VM (assuming Fedora) to VM, boot live system, mount partition of broken system, and read system logs of failed boot by `# journalctl --file <path_to_failed_system_root>/var/log/journal/<some_id>/system.journal` Best regards Jakub ----- Forwarded Message ----- From: "Tomas Jelinek" <tjelinek(a)redhat.com> To: "Jakub Niedermertl" <jniederm(a)redhat.com> Sent: Monday, August 31, 2015 2:05:20 PM Subject: Fwd: [moVirt] Replace the current search box with something nicer (#107) ----- Forwarded Message ----- From: "Tomas Jelinek" <tjelinek(a)redhat.com> To: "Sphoorti Joglekar" <sphoorti.joglekar(a)gmail.com> Cc: "matobet/moVirt" <reply+0023e4ace0b835ae7d6c481277cd23291a2b5d9423b8868592cf0000000111fbe25792a169ce05fe4da7(a)reply.github.com>, "matobet/moVirt" <moVirt(a)noreply.github.com> Sent: Monday, August 31, 2015 2:00:13 PM Subject: Re: [moVirt] Replace the current search box with something nicer (#107) He Sphoorti, Neha, well, not sure what exactly can be the issue, so just some recommendations: 1: please make sure the VMX is enabled on the virtualized processor. - first make sure in the BIOS of the physical machine on which you run the virtual machine the hardware virtualization is enabled - than make sure that the virtual machine has this enabled (in virt-manager you can simply go to processor-> configuration -> pick "copy host CPU Configuration") 2: during boot you can press "esc" key and see some boot logs, maybe there will be something useful 3: try some different version of the all-in-one 4: try the ovirt-live (http://www.ovirt.org/OVirt_Live) which is a live ISO. Just burn this to some CD or put to an USB stick and boot from it. It should be stateless and setup itself. Or you can boot a virtual machine from it. Please let me know if something of this helped. Tomas ----- Original Message ----- > From: "Sphoorti Joglekar" <sphoorti.joglekar(a)gmail.com> > To: "matobet/moVirt" > <reply+0023e4ace0b835ae7d6c481277cd23291a2b5d9423b8868592cf0000000111fbe25792a169ce05fe4da7(a)reply.github.com>, > "Tomas Jelinek" <tjelinek(a)redhat.com> > Cc: "matobet/moVirt" <moVirt(a)noreply.github.com> > Sent: Monday, August 31, 2015 11:57:05 AM > Subject: Re: [moVirt] Replace the current search box with something nicer (#107) > > Hi Tomas, > > Me and Neha have been trying to setup the ovirt all in one iso on a VM with > 4gb RAM. However we are facing setup issue since after successful > installation and reboot, the screen hangs on loading icon. Could you help > us with this? > On Aug 31, 2015 3:07 PM, "Tomas Jelinek" <notifications(a)github.com> wrote: > > > @Neha--Agarwal <https://github.com/Neha--Agarwal> any progress? Are you > > stuck somewhere? Some issues I could maybe help with? > > > > — > > Reply to this email directly or view it on GitHub > > <https://github.com/matobet/moVirt/issues/107#issuecomment-136316161>. > > >

2 1

"moVirt" is now listed at Knicket App Search
by Uwe from Knicket 10 Aug '15

10 Aug '15

Dear Team oVirt, congratulations for your new app release from Knicket App Search, the independent filter- and tag-based app search engine. Your App: moVirt https://play.google.com/store/apps/details?id=org.ovirt.mobile.movirt is now also listed at Knicket App Search: http://en.knicket.com/android/movirt/woyl3 Feel free to set a link from your landing page to this page @ knicket.com Please also provide us with magazine/blog review snippets of articles about your app. It literally takes just seconds for each snippet and is completely login free. Just click |ADD MAGAZINE REVIEW| on your app's page at knicket. If you have any questions or to learn about app promotion options, please feel free to contact me. Best, Uwe --------- If you don't want to be notified at your next app release, pls. reply to this email with "No, thanks" in the header. Follow us on Facebook https://www.facebook.com/knicket.apps Get our app: https://play.google.com/store/apps/details?id=com.echtzeiten.knicket.appsea… What is knicket? Knicket is a meta app search engine. We are listing all iOS and Android apps to give them more exposure and chances for downloads. Our engine offers filters and tags, so apps can be found easier than at the official appstores. Another feature is our own algorithm to display similar apps and competitors. Click to see yours: http://en.knicket.com/similar-to/woyl3/android/movirt knicket.com A Company of Echtzeiten GmbH Uwe Flade Founder / CCO (T) +49 30 3642838-41 Echtzeiten Gmbh c/o Konradi Schlesische Str. 20 10997 Berlin

1 0

Re: [moVirt] Advertising opportunity for Movirt
by Clara Lambert 10 Aug '15

10 Aug '15

Hi, Did you receive the email below? Kindest regards, On Fri, Aug 7, 2015 at 12:10 PM, Clara Lambert <clara(a)adbuddiz.com> wrote: > Dear Ovirt team, > > My name is Clara and I am specialized in helping android developers to > better monetize their apps on Google Play. Our premium advertisers are > currently looking to buy android traffic at a very high price in apps like > Movirt. > > We think you can generate up to $10 CPM with their full screen ads, which > are very clean. Indeed, most of our advertisers are willing to pay , on > average, between $1 and $3 per installation. You're free to display these > ads whenever you want in your app so that it's not intrusive. > > If you'd like to learn more, don't hesitate to ask me. You can also visit > our website: the link is in my signature ;) > > What do you think? Do you want to give it a try? > > Kindest regards, > > Clara Lambert > Account manager > www.adbuddiz.com

1 0

Advertising opportunity for Movirt
by Clara Lambert 07 Aug '15

07 Aug '15

Dear Ovirt team, My name is Clara and I am specialized in helping android developers to better monetize their apps on Google Play. Our premium advertisers are currently looking to buy android traffic at a very high price in apps like Movirt. We think you can generate up to $10 CPM with their full screen ads, which are very clean. Indeed, most of our advertisers are willing to pay , on average, between $1 and $3 per installation. You're free to display these ads whenever you want in your app so that it's not intrusive. If you'd like to learn more, don't hesitate to ask me. You can also visit our website: the link is in my signature ;) What do you think? Do you want to give it a try? Kindest regards, Clara Lambert Account manager www.adbuddiz.com

1 0

[appname, fallback=Your App] Got a Score of [score, fallback=50] out of 100!
by Mobile Action 05 Aug '15

05 Aug '15

[letterscore,fallback=C+] [score,fallback=50] Do you know why [appname,fallback=Your App] got a visibility score of [score,fallback=50]? Congratulations on your new app. Now it's time take your app to the next level. We have prepared a specific page for your app, gathered some data and even created a list of recommended actions. We know how to get your app to the TOP! Show my APP details ! How can I improve my downloads? Here at Mobile Action, we'd love to help your app get more visibility, higher rankings and therefore more organic downloads. That's why we created this company. Simply go to the link below and access our FREE tools to take you to the 1st place in the Play Store. Give me FREE Access ! Cheers Mobile Action Team Don't like these annoying emails? Unsubscribe.

1 0

Hey, nice app! Did you know it’s on Appszoom, too?
by Nico Sánchez 05 Aug '15

05 Aug '15

Hola from Barcelona, and congratulations on your new app! My name's Nico Sánchez. I work for Appszoom, and it's my job to check out new apps every day. I found your e-mail on Google Play, and I thought I would introduce myself. (If you're not interested, just ignore this e-mail and I won’t bother you anymore) You already have a page for your app moVirt [1] in Appszoom. Sign up [2] to officially link other apps you might have to your account, create a Developer Page for oVirt [3], and make sure that your app will be searchable by our 4 million monthly visitors - it's super fast and 100% free. You might be wondering… what is Appszoom, and why is this person writing to me? :) We list every app in the iOS and Android catalogs in our platform, so I'm reaching you to let you know we've got your app too. We handpick the very best high-quality and original apps, test them, and write reviews and articles about them. If our editors notice your app as exceptional, we'll contact you directly. Our community of millions of users and over 25,000 developers shares app experiences on Appszoom. Our mission is to help people discover what app to install next. Once they have made their decision, we send them to the official markets to download. Any questions, don't hesitate to drop me a line. I love hearing from mobile devs. See you in Appszoom! [4] PS: If you're having trouble getting your app off the ground, we can help. Check out our App Boost service [5]! ______________________________ Nico Sánchez Developer Relations nico(a)appszoom.com [6] We help people discover what app to install next Website [7] | Android app [8] | Magazine [9] | About us [10] Links: ------ [1] http://m.appszoom.com/nmt/l?s=20974b.1&u=aHR0cDovL3d3dy5hcHBzem9vbS5jb20vYW… [2] http://m.appszoom.com/nmt/l?s=20974b.1&u=aHR0cDovL3d3dy5hcHBzem9vbS5jb20vZG… [3] http://m.appszoom.com/nmt/l?s=20974b.1&u=aHR0cDovL3d3dy5hcHBzem9vbS5jb20vYW… [4] http://m.appszoom.com/nmt/l?s=20974b.1&u=aHR0cDovL3d3dy5hcHBzem9vbS5jb20vZG… [5] http://m.appszoom.com/nmt/l?s=20974b.1&u=aHR0cDovL2RldmVsb3BlcnMuYXBwc3pvb2… [6] http://m.appszoom.com/nmt/l?s=20974b.1&u=bWFpbHRvOm5pY29AYXBwc3pvb20uY29t [7] http://m.appszoom.com/nmt/l?s=20974b.1&u=aHR0cDovL3d3dy5hcHBzem9vbS5jb20vP3… [8] http://m.appszoom.com/nmt/l?s=20974b.1&u=aHR0cDovL3d3dy5hcHBzem9vbS5jb20vYW… [9] http://m.appszoom.com/nmt/l?s=20974b.1&u=aHR0cDovL3d3dy5hcHBzem9vbS5jb20vbW… [10] http://m.appszoom.com/nmt/l?s=20974b.1&u=aHR0cDovL3d3dy5hcHBzem9vbS5jb20vYW… To unsubscribe click: <http://email.appszoom.com/u/eJwdyzkOgzAQAMDX4NJa7-Gj2CJPQawhLiwjB6Xg9USpphr…>

1 0

Problem
by НеБезIT 05 Aug '15

05 Aug '15

2 1

dashboard feature proposal in moVirt
by Tomas Jelinek 23 Jun '15

23 Jun '15

Hi all, I'd propose a new feature to the movirt: a dashboard. It is highly inspired by the dashboard feature proposed to the oVirt 4.0 [1]. The specific use case I'd like to solve with it is this: - The admin arrives to the office at the morning, puts his tablet/phone to the charger and opens moVirt's dashboard - It will be showing the current health of the whole datacenter, but since it is on a tablet/phone it does not occupy his primary screen so he can freely do his work (considering that oVirt administration is not his only job) - It will play well with the current events/triggers features of moVirt (e.g. if some VM/host is over-utilized, down or..., the phone will start blinking grabbing the attention of the admin) The specific proposal is this: - add a new tab to moVirt which will be opened as the first tab (instead of the current VMs tab) - as the first thing to add is the Utilization section of the [1] without the charts (since we don't have historical data) - please see the attached picture - this should be the first increment, when merged, we can add the top N most utilized VMs and top N utilized hosts (showing only on screens where actually fit in - e.g. not phone but tablet) - as a last step, we could add a stream of events Any comments? Thanx, Tomas [1]: http://uxd-stackabledesign.rhcloud.com/fresh-look-ovirt-administrator-porta…

1 0

when connection fails, user does not know the data are old
by Tomas Jelinek 01 Jun '15

01 Jun '15

Hey All, we have an interesting bug report from Sandro [1] which says that after the connection between engine and moVirt goes down, moVirt does not notify the user about this and keeps showing the old data in the UI as if nothing happened even they are weeks old. This is obviously not correct but not exactly clear how should it behave. I see this options: - if the connection fails during the refresh, set all the statuses of everything to "unknown" (I would not do this since this would generate the notifications and may be temporal (e.g. phone in tunnel or something)) - leave the data as they are and have some top bar or something saying how old the data are. This would be updated at every poll (Not sure, would occupy place and would make it hard for partial updates. And track this for each entity is costy) - leave the data as they are and if some server communication fails add a top bar with a warning that the connection to server is lost and the data are old - maybe with some note when was the last successful connection. (this seems simple enough and my favorite but still not convinced I like it...) Any more ideas? Thanx, Tomas [1]: https://github.com/matobet/moVirt/issues/66

4 6

moVirt: new testing release
by Tomas Jelinek 20 Apr '15

20 Apr '15

Hey all, a new testing release of moVirt[1] (an android client for oVirt) has been just published. You can get it from [2]. It contains significant contributions from the outreachy [3] candidates provided during application period - thank you for that! New stuff: - Persistent auth sessions (e.g. will not keep login/logout at on all request) - Import custom CA (e.g. if you have a custom or self signed cert you can import it directly from moVirt to be used and trusted by moVirt - e.g. no need to trust all hosts) - Triggers support regex (e.g. you can monitor your data center for it's events containing some regex like ".*The Storage Domain does not contain any.*) - Integrated new entities (VM disks, VM nics, Host details) - Material design (e.g. it looks like a modern Android application now :) ) A big thank you for all who contributed! Any feedback more than welcome, Tomas [1]: https://github.com/matobet/moVirt [2]: https://github.com/matobet/moVirt/blob/master/moVirt/moVirt-debug.apk?raw=t… [3]: https://www.gnome.org/outreachy/

1 0

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