bhouse-nexthop commented on PR #14743:
URL: https://github.com/apache/cloudstack/pull/14743#issuecomment-7070490111

   Tested in a lab: a nested KVM cluster of three hosts, with 
`vm.allocation.algorithm=firstfitleastconsumed`. The lab runs a main-based 
(24.0) build with this PR cherry-picked, not the 4.22 branch itself. The code 
this PR changes is the same on both.
   
   Setup:
   1. Three VMs started on kvm1, then kvm1 put into maintenance with kvm3 
disabled, so they migrate to kvm2. Their last host is now kvm1.
   2. kvm3 re-enabled. Four filler VMs on kvm1, so kvm1 is the most consumed 
host (kvm1 8192 MiB allocated, kvm2 3072, kvm3 512).
   3. kvm2 put into maintenance.
   
   | | Before this PR | With this PR |
   |---|---|---|
   | Where kvm2's VMs went | all back to kvm1, the most consumed host | all to 
kvm3, the least consumed |
   | Planner log | `Last host [... kvm1 ...] ... is UP and has enough capacity` 
for each | no last-host lines; `Found destination ... Host(3)` for each |
   | kvm1 allocated memory afterwards | 8192 → 11264 MiB | 8192 MiB (unchanged) 
|
   | kvm3 allocated memory afterwards | 512 MiB (unchanged) | 512 → 3584 MiB |
   
   A start still uses the last host as before, which the new unit tests cover.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to