<div dir="ltr">Note that you can usually get all the information you want using 1 API call, which should still scale.<div>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. </div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Dec 17, 2013 at 10:18 AM, Itamar Heim <span dir="ltr"><<a href="mailto:iheim@redhat.com" target="_blank">iheim@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 12/17/2013 03:08 AM, Sven Kieske wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
we got the following problem:<br>
<br>
we create / start / stop<br>
hole vms /data centers / storage etc<br>
(basically: everything ovirt can handle<br>
via REST-API)<br>
<br>
But if you want to know e.g. the status<br>
of a vm (or anything) you need to constantly<br>
poll the API.<br>
<br>
This is not what we desire to do, as it<br>
does not scale very well (e.g. polling<br>
100 vms).<br>
</blockquote>
<br>
well, you can search events since last event you searched for, only for the specific type of event you are interested in, then check which vm its for.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Is there a standardized way of pushing information<br>
from the engine?<br>
<br>
<br>
</blockquote>
<br>
well, the notification service which sends emails on these actually polls for them every minute in order to send the emails.<br>
<br>
we are discussing snmptraps here[1]<br>
one of the options this could be implemented with is via log4j getting all the audit log events, then you could use any log4j appender (db table, jms queue, etc.)<br>
<br>
[1] Bug 1032661 - Add SNMP trap as notification method to to ovirt-engine-notification<br>
______________________________<u></u>_________________<br>
Engine-devel mailing list<br>
<a href="mailto:Engine-devel@ovirt.org" target="_blank">Engine-devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/engine-devel" target="_blank">http://lists.ovirt.org/<u></u>mailman/listinfo/engine-devel</a><br>
</blockquote></div><br></div>