What is the expected behaviour during non-live migration for VMs bind by affinity rule?

asked 2016-12-14 06:49:24 -0600

Pranshu gravatar image



Two VMs , suppose VM1 and VM2 are present on same host, bind by affinity rule. Non-live mirgation is planned for VM1 but not for VM2.


Will migration operation fail, if it is executed only for VM1? Or, Will migration of VM2 automatically happen as affinity rule is set?

Please let me know the expected behaviour.

Thanks in advance!

BR, Pranshu

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2016-12-14 09:55:21 -0600

volenbovsky gravatar image

Hi, for sure there is no such thing as 'automatic migration of VM2 when VM1 is migrated' I am not 100% sure, but I think that migration or evacuation will fail for either VM1 or VM2 in case you will not specify target Compute Host. Unless you work on some release earlier than ~Kilo the policies are hard policies, so affinity will be forced (but it will not take effect in case you specify target hypervisor- that will override scheduler) To make it worse I think it will fail also in case you attempt to migrate/evacuate them simultaneously.

The answer to that could be using soft affinity/anti-affinity, supported from Mitaka

edit flag offensive delete link more


Hi Volenbovsky, By migration i was referring to non-live migration, stating the target compute host. The question is, If two VMs are bond by affinity rule, and we will try to migrate one VM to another host, what should be the expected behaviour?Will migration fail as we are migrating only one VM?

Pranshu gravatar imagePranshu ( 2016-12-15 06:30:36 -0600 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2016-12-14 06:49:24 -0600

Seen: 146 times

Last updated: Dec 14 '16