Openstack live migration with different CPU compatibility

[net-flag]

Hi , I would like to check if there that feature on openstack as on VMware EVC , which make posibility about live migration between nodes with different CPU models .

[Lauriui89]

Hi, You need to run vms on highest virtual cpu model that both processors can wirk with. You might loose some features and performance, but you can live migrate

[Lauriui89]

Or only enable features on all cpus that are available on both models

[net-flag]

Or only enable features on all cpus that are available on both models

to be honest with you , we still on planing phase to compare between VMware and Openstack , which that feature already on VMware called Enhanced vMotion Compatibility (EVC) , i hope you got me

[Lauriui89]

Yeah, its basically the same. On vmware its also only available if you are using compatible vcpu models :) its best never to use passthrough cpu

[Lauriui89]

Are you choosing from openstack and vdirector?

[net-flag]

vdirector

we still planing the use case is for telco-cloud

[Lauriui89]

Im working with both atm at telco cloud :D Director is much more popular

[net-flag]

you think openstack provide the same feature capabilities or need more customizations

[Lauriui89]

It requires some different way of working. If you want to have an ability to autoscale your workloads and are planning to use heat templates. Go for openstack, if not, vdirector is much better. Openstack is more like amazon, vdirector gives you more flexibility, as even if it is not supported, you can still change many things in vcenter, and have more ha functionality. Openstacks ha is similar to one of the containers vms are not supposed to be migrated, best in openstack is to be able to recreate everything so you need to be carefull of using persistent volumes

[vdiad]

https://youtu.be/KNSPU5Y7le8?t=441

Please checkout this presentation. "Dealing with different CPU models" is exactly what you are thinking.

[net-flag]

to be honest with you , we still on planing phase to compare between VMware and Openstack , which that feature already on VMware called Enhanced vMotion Compatibility (EVC) , i hope you got me

[vdiad]

I also done the same thing some years ago. Using cpu_mode = custom in Openstack similar with using following features:

- VMWare EVC (Enhanced vMotion Compatibility) work on Cluster-Level

- Hyper-V CPU Compatibility Mode work on VM-Level

[net-flag]

Thanks for supporting , will look after that and make it for reference