1:03 a.m.
(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
>