Hi, yes, the affinity enforcement engine does work with soft rules. However, soft affinity is just one input to the weighting part of the algorithm and other inputs (free memory, cpu load, ..) can counter it.
You could increase the weight of the affinity policy units in the Scheduling policy configuration, but it should already be high enough (I think the default is 100). There is an table in the log when debug logging is enabled: https://ovirt.org/develop/release-management/features/sla/scheduling-weight-normalization/#testing You can check the internal weights and the selection process by enabling this like this: - use the logcontrol script from here https://github.com/oVirt/ovirt-engine/blob/master/contrib/log-control.sh - and enable DEBUG for org.ovirt.engine.core.bll.scheduling.policyunits.RankSelectorPolicyUnit Best regards -- Martin Sivak SLA, oVirt On Mon, Jun 18, 2018 at 4:52 PM, <[email protected]> wrote: > Hi, > > i operate a 3 node ovirt42 cluster (hyperconverged). > > Now i would like to isolate the HostedEngine from the other VMs. > The reason is to minimize the impact of outage of one of the nodes. > When the node with the HE is away there is no impact at all on the running > VMs. > If one of the other nodes goes down, then i have still a running HE which > restarts > the missing VMs on remaining nodes fast again. > > I cannot use hard affinity because in case of failure i need all resources of > the 2 remaining modes, > so i configured a soft negative affinity group for every VM between this VM > and the HE. > > As a first test i migrated the HE to a node with VMs but even after a while > nothing happened. > I would have expected that either the HE or the VMs on this node would have > been migrated to > fullfill the soft negative affinity. > > Now my questions: > > Are my thoughts correct? > Is there a better solution than making one (soft negative) affinity group for > every VM to isolate from HE? > Does the affinity group enforcement engine work at all with soft rules? > > Regards, > Robert > _______________________________________________ > 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/XKHYWZD6CO5FQG67IL6OIBAHVKVBSX5Q/ _______________________________________________ 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/X52PVRF2U7R5XFPL7M4IUZIJOXL54HXC/
