Hello,
I have found that migration doesn't work when using vms_rule
Enforcing Hard.
Scenario vms in an affinity group with Enforcing Hard no host members when
trying to migrate vms it comes back with no host to migrate to even when
selecting all vms in the affinity group.
Regards,
Paul S.
________________________________________
From: Martin Sivak <[email protected]>
Sent: 15 October 2018 09:43
To: Darrell Budic
Cc: Ovirt Users
Subject: [ovirt-users] Re: Affinity rules in ovirt
Hi,
> 3) What is the difference between VM to VM affinity and VM to Host affinity?
- VM - VM rule expresses the relationship of all running VMs from the
specified list to each other.
- VM - Host rule describes the relationship of all running VMs from
the list to the selected hosts
> Say I have 2 hosts, so what happens in case of failure of host running the
> VMs?
VMs that are not up are not considered by scheduler. So it will
(assuming those are highly available VMs) start the first VM somewhere
and then the second VM will be started at the same host where the
first one is running.
> Enforcing will keep the scheduler from launching a VM if it can’t meet those
> criteria, and will try and make changes to which hosts are running where if
> it can. If you don’t set it, it will still try and launch VMs on different
> hosts, but if it can’t, it will still launch the VM.
Correct.
> It also won’t make
> changes to bring all VMs into compliance with the Affinity rules, from what
> I can tel.
It will try that too, but rather less aggressively.
Best regards
Martin Sivak
On Sun, Oct 14, 2018 at 7:59 PM, Darrell Budic <[email protected]> wrote:
> VM to VM affinity will try and run the VMs on the same host if positive, and
> different hosts if negative.
>
> VM to Host affinity will try and run the VM on a specific set of Hosts if
> positive, and not on those hosts if negative.
>
> Enforcing will keep the scheduler from launching a VM if it can’t meet those
> criteria, and will try and make changes to which hosts are running where if
> it can. If you don’t set it, it will still try and launch VMs on different
> hosts, but if it can’t, it will still launch the VM. It also won’t make
> changes to bring all VMs into compliance with the Affinity rules, from what
> I can tel.
>
> On Oct 14, 2018, at 8:15 AM, Hari Prasanth Loganathan
> <[email protected]> wrote:
>
> Hi Team,
>
> I tried to follow up the affinity rules using this tutorial :
> https://www.youtube.com/watch?v=rs_5BSqacWE but I have few clarifications in
> it.,
>
> 1) I understand the VM to VM affinity, It means both the individual VMs
> needs to run on a single common host, Say I have 2 hosts, so what happens in
> case of failure of host running the VMs?
> 2) If I create a affinity group and I get the following data,
> i) What is host rule / vms rule - enabled, enforcing and
> positive ?
>
> "enforcing": "true",
> "hosts_rule": {
> "enabled": "true",
> "enforcing": "true",
> "positive": "false"
> },
> "vms_rule": {
> "enabled": "false",
> "enforcing": "true",
> "positive": "false"
> }
>
> 3) What is the difference between VM to VM affinity and VM to Host affinity?
>
> Doc's are not very clear, so please any help is appreciated.
>
> Thanks,
> Hari
>
>
>
> DISCLAIMER - MSysTechnologies LLC
>
>
> This email message, contents and its attachments may contain confidential,
> proprietary or legally privileged information and is intended solely for the
> use of the individual or entity to whom it is actually intended. If you have
> erroneously received this message, please permanently delete it immediately
> and notify the sender. If you are not the intended recipient of the email
> message,you are notified strictly not to disseminate,distribute or copy this
> e-mail.E-mail transmission cannot be guaranteed to be secure or error-free
> as Information could be intercepted, corrupted, lost, destroyed, incomplete
> or contain viruses and MSysTechnologies LLC accepts no liability for the
> contents and integrity of this mail or for any damage caused by the
> limitations of the e-mail transmission.
>
>
> _______________________________________________
> Users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/[email protected]/message/ST35SIO45EO647BJKUVCUZQBRSAHAUSA/
>
>
>
> _______________________________________________
> Users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/[email protected]/message/GXWG7ICW2YN7HZKWVVMRLO53YAIA5DCI/
>
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/[email protected]/message/7R6KZVHKVGGTMRLMYKF4PO2GR32QMIXC/
To view the terms under which this email is distributed, please go to:-
http://disclaimer.leedsbeckett.ac.uk/disclaimer/disclaimer.html
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/[email protected]/message/K7GOSJBXFG3ZKYZQTFVIH3X2FZS5H5M5/
