11:54 a.m.
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
12:21 p.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--
12:26 p.m.
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.
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.
2015-01-05 10:21 GMT+01:00 Doron Fediuck <dfediuck(a)redhat.com>:
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
12:44 p.m.
This is a multi-part message in MIME format.
--------------060105020606090901010702
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
On 05/01/15 11:26, Koen Vanoppen wrote:
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.
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.
2015-01-05 10:21 GMT+01:00 Doron Fediuck <dfediuck(a)redhat.com
<mailto:dfediuck@redhat.com>>:
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
Koen,
this is clear now.
Currently affinity applies to VMs only. For 3.6 we're planning "pin to
hosts"
which will allow you to pin VMs to a group of hosts, such as Datacenter1
hosts
in your case. Until 3.6 will be available (which will take a while), you
can consider
writing a filter module for the ovirt scheduler. Let me know if you need
more
details.
Doron
--------------060105020606090901010702
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 05/01/15 11:26, Koen Vanoppen
wrote:<br>
</div>
<blockquote
cite="mid:CACfY+MbbQvjboCJLwBmW16YNm1wE379SsV7p9tYxVU3FDm0ytA@mail.gmail.com"
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"><<a
moz-do-not-send="true"
href="mailto:dfediuck@redhat.com"
target="_blank">dfediuck@redhat.com</a>></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 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'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></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's<br>
no rule which is valid for Datacenter1 and Datacenter2.<br>
<br>
HTH,<br>
Doron<br>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
Koen,<br>
this is clear now. <br>
Currently affinity applies to VMs only. For 3.6 we're planning "pin
to hosts"<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.<br>
<br>
Doron<br>
</body>
</html>
--------------060105020606090901010702--
12:46 p.m.
Ok, thanks. Can you give me some details/example of a filter for the ovirt
schedular?
Kind regards and thank you,
Koen
2015-01-05 10:44 GMT+01:00 Doron Fediuck <dfediuck(a)redhat.com>:
On 05/01/15 11:26, Koen Vanoppen wrote:
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.
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.
2015-01-05 10:21 GMT+01:00 Doron Fediuck <dfediuck(a)redhat.com>:
>
> 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
>
Koen,
this is clear now.
Currently affinity applies to VMs only. For 3.6 we're planning "pin to
hosts"
which will allow you to pin VMs to a group of hosts, such as Datacenter1
hosts
in your case. Until 3.6 will be available (which will take a while), you
can consider
writing a filter module for the ovirt scheduler. Let me know if you need
more
details.
Doron
5:28 p.m.
If you want that each vm will run on different host, you can:
1) just not pinned it to specific host(placement and migration options under vm
properties)?
2) create two clusters, each cluster will have hosts from different physical datacenters,
and for each cluster administrate different set of vms.
3) And in the end we have possibility to use external scheduler, so you can write your own
python script, and use it as filter, weight or balance module for ovirt scheduler:
http://www.ovirt.org/Features/oVirt_External_Scheduling_Proxy
http://www.ovirt.org/External_Scheduler_Samples
You need to install package ovirt-scheduler-proxy and also enable it via engine-config
-s ExternalSchedulerEnabled=True.
Also additional info you can find under cd /usr/share/doc/ovirt-scheduler-proxy*
I hope it will help you.
Thanks
----- Original Message -----
From: "Koen Vanoppen" <vanoppen.koen(a)gmail.com>
To: "Doron Fediuck" <dfediuck(a)redhat.com>, users(a)ovirt.org
Sent: Monday, January 5, 2015 11:26:26 AM
Subject: Re: [ovirt-users] Affinity
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.
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.
2015-01-05 10:21 GMT+01:00 Doron Fediuck < dfediuck(a)redhat.com > :
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
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
10:40 a.m.
Ok, Super! Big thanks for your help!
2015-01-05 15:28 GMT+01:00 Artyom Lukianov <alukiano(a)redhat.com>:
If you want that each vm will run on different host, you can:
1) just not pinned it to specific host(placement and migration options
under vm properties)?
2) create two clusters, each cluster will have hosts from different
physical datacenters, and for each cluster administrate different set of
vms.
3) And in the end we have possibility to use external scheduler, so you
can write your own python script, and use it as filter, weight or balance
module for ovirt scheduler:
http://www.ovirt.org/Features/oVirt_External_Scheduling_Proxy
http://www.ovirt.org/External_Scheduler_Samples
You need to install package ovirt-scheduler-proxy and also enable it
via engine-config -s ExternalSchedulerEnabled=True.
Also additional info you can find under cd
/usr/share/doc/ovirt-scheduler-proxy*
I hope it will help you.
Thanks
----- Original Message -----
From: "Koen Vanoppen" <vanoppen.koen(a)gmail.com>
To: "Doron Fediuck" <dfediuck(a)redhat.com>, users(a)ovirt.org
Sent: Monday, January 5, 2015 11:26:26 AM
Subject: Re: [ovirt-users] Affinity
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.
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.
2015-01-05 10:21 GMT+01:00 Doron Fediuck < dfediuck(a)redhat.com > :
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
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
3608
days inactive
3609
days old
6 comments
3 participants
participants (3)
-
Artyom Lukianov -
Doron Fediuck -
Koen Vanoppen