Since live migration has been moved to the conductor, there was no
possibility for the conductor to verify if the destination had
enough RAM just because it didn't know the allocation ratios given
by the scheduler.
Now that ComputeNodes provide a ram_allocation_field, we can fix
that check and provide the same validation than RAMFilter to make
sure that the destination is good.
Reviewed: https:/ /review. openstack. org/180151 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=f5e35dcfe8e e586106438bcfa5 51426babc75bf6
Committed: https:/
Submitter: Jenkins
Branch: master
commit f5e35dcfe8ee586 106438bcfa55142 6babc75bf6
Author: Sylvain Bauza <email address hidden>
Date: Thu Sep 17 17:51:06 2015 +0200
Correct memory validation for live migration
Since live migration has been moved to the conductor, there was no
possibility for the conductor to verify if the destination had
enough RAM just because it didn't know the allocation ratios given
by the scheduler.
Now that ComputeNodes provide a ram_allocation_ field, we can fix
that check and provide the same validation than RAMFilter to make
sure that the destination is good.
Closes-Bug: #1451831
Closes-Bug: #1214943
Change-Id: Ie6c768fc915553 da73160ea519610 78bfbacec77