<div dir="ltr"><div>Ok, thanks. Can you give me some details/example of a filter for the ovirt schedular?<br><br></div>Kind regards and thank you,<br><br>Koen<br></div><div class="gmail_extra"><br><div class="gmail_quote">2015-01-05 10:44 GMT+01:00 Doron Fediuck <span dir="ltr">&lt;<a href="mailto:dfediuck@redhat.com" target="_blank">dfediuck@redhat.com</a>&gt;</span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF" text="#000000"><div><div class="h5">
    <br>
    <div>On 05/01/15 11:26, Koen Vanoppen wrote:<br>
    </div>
    <blockquote type="cite">
      <div dir="ltr">
        <div>Thanks for your reply. But I maybe explained it badly...
          All the 4 hypervisors are in the same Datacenter on oVirt. But
          they are physically in a different datacenter.<br>
        </div>
        That is why I want to force them to run on a different
        hypervisor. IF 1 physical datacenter would go down (electricity
        power failure or whatever) At least one VM will continue to run.<br>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">2015-01-05 10:21 GMT+01:00 Doron
          Fediuck <span dir="ltr">&lt;<a href="mailto:dfediuck@redhat.com" target="_blank">dfediuck@redhat.com</a>&gt;</span>:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000">
              <div>
                <div> <br>
                  <div>On 05/01/15 10:54, Koen Vanoppen wrote:<br>
                  </div>
                  <blockquote type="cite">
                    <div dir="ltr">
                      <div>
                        <div>
                          <div>
                            <div>
                              <div>
                                <div>
                                  <div>
                                    <div>
                                      <div>
                                        <div>Hi All,<br>
                                          <br>
                                        </div>
                                        First of all, let me say a Happy
                                        New Year with all the best
                                        wishes!!<br>
                                        <br>
                                      </div>
                                      Now, let&#39;s get down to business
                                      :-).<br>
                                      <br>
                                    </div>
                                    I would lik eto implement the
                                    Affinity option in our datacenter.<br>
                                  </div>
                                  I already activated it, put the 2 vms
                                  in it and set in on negative so they
                                  won&#39;t run together on the same
                                  hypervisor. Now, the question...<br>
                                </div>
                                Is there a way I can force the VM&#39;s so
                                they will run on a hypervisor that is
                                not in the same datacenter? We have
                                this;<br>
                                <br>
                              </div>
                              Hyp1 -&gt; Datacenter1<br>
                            </div>
                            Hyp2 -&gt; Datacenter2<br>
                            Hyp3 -&gt; Datacenter1<br>
                            Hyp4 -&gt; Datacenter2<br>
                            <br>
                          </div>
                          For the moment they run on a different
                          Hypervisor, but they are in the same
                          Datacenter. I can manually now move them to
                          the other one, but I would like this that
                          oVirt manages this...<br>
                        </div>
                        Is this possible...?<br>
                        <br>
                      </div>
                      Kind regards,<br>
                      <br>
                      Koen<br>
                    </div>
                    <br>
                    <fieldset></fieldset>
                    <br>
                  </blockquote>
                </div>
              </div>
              Hi Koen.<br>
              <br>
              VMs cannot move between data centers while still running.<br>
              Just to provide some basic concepts in terms of hierarchy,
              we have:<br>
              <br>
              Data-Center1<br>
              |<br>
              |\ Cluster A<br>
              | |<br>
              | |\ Host (a)<br>
              | |\ Host (b)<br>
              |<br>
              |\ Cluster B<br>
              | |<br>
              | |\ Host (c)<br>
              | |\ Host (d)<br>
              | |\ Host (e)<br>
              <br>
              Data-Center2<br>
              |<br>
              |\ Cluster A<br>
              | |<br>
              | |\ Host (f)<br>
              |<br>
              |\ Cluster B<br>
              | |<br>
              | |\ Host (g)<br>
              | |\ Host (h)<br>
              | |\ Host (i)<br>
              <br>
              As you can see, a host may be a part of a single cluster
              and a VM<br>
              will run on one of the hosts. Live migration can be done
              between<br>
              hosts of the same cluster. The only way to move VM between
              clusters<br>
              and DCs are when the VM is down, in a manual way.<br>
              <br>
              So Affinity works in the cluster level, and the rules are
              valid for a<br>
              specific cluster who currently owns the VM.<br>
              In your case if Hyp1 and Hyp3 belong to the same cluster,
              the affinity<br>
              rules will apply every time you start or migrate a VM.
              However, there&#39;s<br>
              no rule which is valid for Datacenter1 and Datacenter2.<br>
              <br>
              HTH,<br>
              Doron<br>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br></div></div>
    Koen,<br>
    this is clear now. <br>
    Currently affinity applies to VMs only. For 3.6 we&#39;re planning &quot;pin
    to hosts&quot;<br>
    which will allow you to pin VMs to a group of hosts, such as
    Datacenter1 hosts<br>
    in your case. Until 3.6 will be available (which will take a while),
    you can consider<br>
    writing a filter module for the ovirt scheduler. Let me know if you
    need more<br>
    details.<span class="HOEnZb"><font color="#888888"><br>
    <br>
    Doron<br>
  </font></span></div>

</blockquote></div><br></div>