11:21 a.m.
This is a multi-part message in MIME format.
--------------060006090001070004030006
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
On 05/01/15 10:54, Koen Vanoppen wrote:
Hi All,
First of all, let me say a Happy New Year with all the best wishes!!
Now, let's get down to business :-).
I would lik eto implement the Affinity option in our datacenter.
I already activated it, put the 2 vms in it and set in on negative so
they won't run together on the same hypervisor. Now, the question...
Is there a way I can force the VM's so they will run on a hypervisor
that is not in the same datacenter? We have this;
Hyp1 -> Datacenter1
Hyp2 -> Datacenter2
Hyp3 -> Datacenter1
Hyp4 -> Datacenter2
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...
Is this possible...?
Kind regards,
Koen
Hi Koen.
VMs cannot move between data centers while still running.
Just to provide some basic concepts in terms of hierarchy, we have:
Data-Center1
|
|\ Cluster A
| |
| |\ Host (a)
| |\ Host (b)
|
|\ Cluster B
| |
| |\ Host (c)
| |\ Host (d)
| |\ Host (e)
Data-Center2
|
|\ Cluster A
| |
| |\ Host (f)
|
|\ Cluster B
| |
| |\ Host (g)
| |\ Host (h)
| |\ Host (i)
As you can see, a host may be a part of a single cluster and a VM
will run on one of the hosts. Live migration can be done between
hosts of the same cluster. The only way to move VM between clusters
and DCs are when the VM is down, in a manual way.
So Affinity works in the cluster level, and the rules are valid for a
specific cluster who currently owns the VM.
In your case if Hyp1 and Hyp3 belong to the same cluster, the affinity
rules will apply every time you start or migrate a VM. However, there's
no rule which is valid for Datacenter1 and Datacenter2.
HTH,
Doron
--------------060006090001070004030006
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 05/01/15 10:54, Koen Vanoppen
wrote:<br>
</div>
<blockquote
cite="mid:CACfY+Ma9+WBzJrJnyZwWip26HYHG9nGUvKAoBMKFxLOzu1JObw@mail.gmail.com"
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'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't run together on the
same hypervisor. Now, the question...<br>
</div>
Is there a way I can force the VM's so they will run
on a hypervisor that is not in the same datacenter? We
have this;<br>
<br>
</div>
Hyp1 -> Datacenter1<br>
</div>
Hyp2 -> Datacenter2<br>
Hyp3 -> Datacenter1<br>
Hyp4 -> 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 class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
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's<br>
no rule which is valid for Datacenter1 and Datacenter2.<br>
<br>
HTH,<br>
Doron<br>
</body>
</html>
--------------060006090001070004030006--