Hi,
we got the following problem:
we create / start / stop
hole vms /data centers / storage etc
(basically: everything ovirt can handle
via REST-API)
But if you want to know e.g. the status
of a vm (or anything) you need to constantly
poll the API.
This is not what we desire to do, as it
does n
On 12/17/2013 03:08 AM, Sven Kieske wrote:
Hi,
we got the following problem:
we create / start / stop
hole vms /data centers / storage etc
(basically: everything ovirt can handle
via REST-API)
But if you want to know e.g. the status
of a vm (or anything) you need to constantly
poll the API.
T
Note that you can usually get all the information you want using 1 API
call, which should still scale.
For instance, /ovirt-engine/api/vms will give you a list of all VMs and
their statuses, so you can just run an XPath and get the status of all of
them.
On Tue, Dec 17, 2013 at 10:18 AM, Itamar H
Hi,
thanks for your fast replies.
We are aware that we can poll this via API, but we don't want to poll
it, as it's not a good solution, from a design point of view.
We will maybe write a little python script, which runs on engine-node
via SDK which polls the API and let this script push the inf
uesday, December 17, 2013 10:08:11 AM
> Subject: [Engine-devel] Polling vs Pushing engine events
>
> Hi,
>
> we got the following problem:
>
> we create / start / stop
> hole vms /data centers / storage etc
> (basically: everything ovirt can handle
> via REST-API)
&g
Hi,
the following seems to be killing our
plans to use a pythonscript to fetch the list of vms:
This comes from the users list:
Am 17.12.2013 15:04, schrieb Sander Grendelman:> Fetching the list of
vms through the API with the python SDK
> takes several seconds[1] with 100% cpu usage in the pyth
