Hi Yair,
Thanks for your response!
Patches are very welcome. Even testing with various android devices
and version would be of great help.
As of now I'm polling the REST API periodically (for events, Vm stats ...)
and the current focus is on stabilization and features. But definitely push
server is on the long term future plan.
----- Original Message -----
From: "Yair Zaslavsky" <yzaslavs(a)redhat.com>
To: "Martin Betak" <mbetak(a)redhat.com>
Cc: users(a)ovirt.org
Sent: Wednesday, April 9, 2014 3:47:22 PM
Subject: Re: [Users] A mobile monitoring application for oVirt
Awesome,
Do you need help in developing that?
Are you getting the information via notification of events, or are you
polling?
----- Original Message -----
> From: "Martin Betak" <mbetak(a)redhat.com>
> To: users(a)ovirt.org
> Sent: Thursday, April 3, 2014 5:37:05 PM
> Subject: [Users] A mobile monitoring application for oVirt
>
> Hello oVirt users,
>
> I'm in the process of developing a simple monitoring application for oVirt
> on
> the Android platform.
> This is still under heavy development, but first usable version can be
> found
> at [1]
> Please note that this is still a development preview so it can be a little
> unstable and the UI design is not yet perfect
> (well ... design by programmer :-)) but I hope it could be useful. All
> comments, remarks,
> feature requests and general feedback are very welcome. You can file any
> issues directly at [2].
>
> Below follow the details of using and configuring the app.
>
> Description:
>
> The goal of this project was to create a simple Android app that would
> enable
> oVirt admins to configure conditions on Vms, Clusters,
> or whole datacenter upon which they want to be notified. At the moment you
> can configure 3 types of "Triggers":
> - when Vm CPU is over given level
> - when Vm Memory usage is over given level
> - when Vm enters given state (Down, Unknown ...)
> You can also choose if you want just simple standard android notification
> or
> also want the device to vibrate.
>
> You can also define all these triggers on per-Vm, per-Cluster or "global"
> level.
>
> Configuration:
>
> On first run the app will prompt you to enter connection parameters of your
> running oVirt engine instance.
> API URL should be in the form of
http://host:port/ovirt-engine/api
> Username is user@domain i.e. admin@internal
> Password is ... well the above user's password :-)
>
> sadly only http (not https) is supported so far for endpoint url.
>
> If you have any more questions feel free to use this thread and I'll do my
> best to answer them :-)
>
> Best regards,
>
> Martin
>
>
> [1]
https://github.com/matobet/moVirt/blob/master/moVirt/moVirt.apk
> [2]
https://github.com/matobet/moVirt/issues
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/users
>