From: "Yair Zaslavsky" <yzaslavs(a)redhat.com>
To: "Greg Sheremeta" <gshereme(a)redhat.com>
Cc: "users" <users(a)ovirt.org>, devel(a)ovirt.org
Sent: Friday, October 31, 2014 11:16:33 AM
Subject: Re: [ovirt-devel] [ovirt-users] [RFC] oVirt mobile client
----- Original Message -----
> From: "Yair Zaslavsky" <yzaslavs(a)redhat.com>
> To: "Greg Sheremeta" <gshereme(a)redhat.com>
> Cc: "users" <users(a)ovirt.org>, devel(a)ovirt.org
> Sent: Friday, October 31, 2014 8:03:58 AM
> Subject: Re: [ovirt-users] [ovirt-devel] [RFC] oVirt mobile client
>
>
>
> ----- Original Message -----
> > From: "Greg Sheremeta" <gshereme(a)redhat.com>
> > To: "users" <users(a)ovirt.org>, devel(a)ovirt.org
> > Sent: Friday, October 31, 2014 3:49:11 AM
> > Subject: [ovirt-devel] [RFC] oVirt mobile client
> >
> > Hi,
> >
> > The focus of our OPW internship program starting in December will be
> > mobile and/or lightweight engine clients -- hopefully integrating the
> > new ovirt.js project.
>
> +100
>
> Sorry for the ignorant question - does this mean the technology will be web
> based or native? (i.e - java on top of android, Swift/Objective-C on top of
> IOS)
>
>
> >
> > I see that there are some already existing mobile clients for oVirt.
> > I'm trying to grasp what we have and what the needs are.
> >
> > moVirt:
https://github.com/matobet/moVirt (mbetak)
> > This appears to be more of a lightweight webadmin. No console access,
> > but I believe it's planned as part of OPW. (?)
>
> I spoke with mbetak about this a few months ago.
> When you speak of console, you mean to actually view the VM using spice?
> sounds very interesting.
> If I recall, Alon levy (a former red hatter) worked on some spice
> implementation for html5 or something like that.
>
> Anyway, back in TLV I also had some ideas around that. Do you have some IRC
> meetings or something that I can join?
>
> Cheers,
> Yair
>
>
> >
> > nomad:
http://www.ovirt.org/Project_Proposal_-_Nomad and
> >
https://github.com/Vizuri/ovirt-nomad
> > Looks dead -- last commit 3 years ago.
> > Anyone know more about this one?
> >
> > That's all I see on the first few pages of google.
> >
> > When I think of a mobile client for oVirt, I think the most useful
> > part would be the user portal -- simple operations for start, stop,
> > and the ability to view the console of vms. moVirt mentions it wants
> > to support some basic management operations, though. I think it would
> > be difficult to do complex management in a mobile client. (I'm biased
> > towards huge screens, though.)
Sorry, I was very excited about the news, so I forgot to answer the rest.
I agree about "user portal" - sounds good to begin with.
Another idea I had in the past is to have an app (push-based) that will push
events to a special client.
We will have a push sever that will get notifications from the event
notifier, and this server will push the events to registered clients.
Excellent idea! Could we get such notifications and publish them to some
event bus within Engine backend (exposing them to other webapps running
within Engine EAR context) + have WebSocket webapp that pushes them to
connected clients? (or, if we don't want WebSocket, some other push-like
alternative)
Imagine a different way to build JavaScript web applications - it first
fetches all relevant data, caches it, and then just receives updates that
modify its cache.
> >
> > I'd like to see an official subproject started that coordinates our
> > mobile efforts.
> >
> > Is this possible? What would it take to start it?
What do you mean "is that possible"? technically sounds feasible to me (well,
we'll need to figure out about the console, but an mgmt app without the
console, why not?) )
> >
> > What would people like to see in such an app?
> >
> > Greg Sheremeta
> > Red Hat, Inc.
> > Sr. Software Engineer, RHEV
> > Cell: 919-807-1086
> > gshereme(a)redhat.com
> > _______________________________________________
> > Devel mailing list
> > Devel(a)ovirt.org
> >
http://lists.ovirt.org/mailman/listinfo/devel
> >
> _______________________________________________
> 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