Hi Stackers, I noticed that there are some blueprints trying to move the logic of live migration/resize/code migration/provision from nova scheduler to nova conductor, but the blueprint did not describe clearly the benefits of doing so, can some experts give some explanation on this?
I know the original design for nova conductor is for a non-db nova compute, but what's the reason of moving scheduling logic to nova conductor? Thanks, Jay
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
