Nice, thanks for the info. Can you give a hint of a time frame for the implementation? I'm not asking for dates or even version numbers, just something along the lines of 'short term', 'mid term', etc.<br>
<br>Regards,<br><br><br clear="all">Maxim Burgerhout<br><a href="mailto:maxim@wzzrd.com" target="_blank">maxim@wzzrd.com</a><br>----------------<br>EB11 5E56 E648 9D99 E8EF 05FB C513 6FD4 1302 B48A<br><br><br>
<br><br><div class="gmail_quote">On Tue, Jul 31, 2012 at 3:19 PM, 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">
<div class="im">On 07/31/2012 04:07 PM, Maxim Burgerhout wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
Can someone tell me whether setting positive and negative VM affinity<br>
rules will be at all possible with oVirt at some point in time, i.e. is<br>
this on the roadmap?<br>
<br>
</blockquote>
<br></div>
it is.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I need to be able to tell VM's to run on different hosts, spread them<br>
around, so to speak. For example, domain controllers would be better off<br>
running on as many different hypervisors as possible, the way I see it.<br>
That way, the failure of a single hypervisor has minimal impact on the<br>
infrastructure. I know there is a feature to pin VM's to a single<br>
hypervisor, but that's not quite the same. I would like to group the<br>
domain controllers and then tell them not to run on the same host as<br>
other members of that group as much as possible.<br>
<br>
The other way around would be nice as well: have several VM's run on the<br>
same hardware. For example, a three tiered web application would<br>
probably perform better if the VM's are all on the same hypervisor. I<br>
know I could pin them all to the same hypervisor, but still: that's not<br>
quite the same. I want to be able to group the web app VM's and tell<br>
them to try to run on the same hypervisors as the other members of the<br>
group, so they can move to another hypervisor as a group if the need arises.<br>
<br>
Apologies if this has been asked before or documented in some place I<br>
haven't looked yet.<br>
<br>
</blockquote>
<br></div>
two ways for you to do this today:<br>
1. prefer/pin these VMs to different host<br>
2. use two clusters and put them in different ones<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Regards,<br>
<br>
Maxim Burgerhout<mailto:<a href="mailto:maxim@wzzrd.com" target="_blank">maxim@wzzrd.<u></u>com</a>><br>
<br>
<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/<u></u>mailman/listinfo/users</a><br>
<br>
</blockquote>
<br>
<br>
</blockquote></div><br>