<div dir="ltr"><div>You can always overcommit, so hard to tell when no resources are left.<br></div>You can use quote to limit to physical resources.<br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><pre cols="72"><span style="font-family:arial,helvetica,sans-serif">Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109
Tel : +972 (9) 7692306
8272306
Email: <a href="mailto:ydary@redhat.com" target="_blank">ydary@redhat.com</a>
IRC : ydary</span></pre>
</div></div></div></div></div>
<br><div class="gmail_quote">On Mon, Jan 18, 2016 at 11:52 PM, David Jorm <span dir="ltr"><<a href="mailto:djorm@iix.net" target="_blank">djorm@iix.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi All<br>
<br>
My team is currently building an application based on the oVirt REST<br>
API, and we noticed that it is possible to create a VM with resources<br>
(i.e. RAM or CPU) that are not physically available in the cluster.<br>
Running the VM will fail with an appropriate error message, but for<br>
our use case it would be highly desirable that the VM creation fails.<br>
I haven't found any setting that enables this behavior, but I was<br>
wondering if one is hidden somewhere or there is a simple workaround<br>
to make VM creation fail if resources are not available to run it.<br>
<br>
Thanks<br>
David<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
</blockquote></div><br></div>