GitHub user StepBee edited a comment on the discussion: DRS doesn't take into account affinity rules
that's exactly the case, the host won't enter maintenance - and for my understanding that's the main reason why non-strict was invented, to prevent this case. If non-strict would mean kind-of-best effort but in the end cloudstack does not bind to it even if enough hosts are available, then i am with @bhouse-nexthop , the use-cases for non-strict are close to zero. I think the documentation of non-strict, as pasted above, is quite clear about fulfilling anti-affinity as long as there are enough hosts available. Looking from the other side - maybe my understanding is wrong and non-strict (anti-)affinity groups should only be considered for the initial deployment and not over the lifetime of a VM, for example in combination with DRS. Then it would be great to discuss about the extension of DRS to respect non-strict maybe? I see huge benefit from it, as i encourage using non-strict in my environment to make operations like rolling maintenance easier. GitHub link: https://github.com/apache/cloudstack/discussions/12485#discussioncomment-15563365 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
