Page History

...

Today, CloudStack assigns VM down to host level, in VM startup phase, once it has assigned the VM to a particular host, it assumes the state-sync information comes from this original host. With DRS, this may because not true, since DRS may re-arrange the VM even at this stage, and if DRS has done that, it may have some effect to CloudStack VM startup process. (CloudStack is able to handle VM replacement after VM has been started). Additionally, we need to sync up VMware better – something like, when an out of band vMotion happens, we need to know it faster/asynchronously to enable CS to get the up-to-date resource situation. Moreover, today, all VMware clusters are assumed to be HA or not – i.e. all or nothing – this needs to be more granular, preferably automatically learnt from vCenter.

DRS has 3 automation levels – Manual, Partially Automated and Fully Automated.

CloudStack assigns VM down to host level, in VM startup phase, once it has assigned the VM to a particular host, it assumes the state-sync information comes from this original host. With DRS, this may because not true, since DRS may re-arrange the VM even at this stage, and if DRS has done that, it may have some effect to CloudStack VM startup process. (CloudStack is able to handle VM replacement after VM has been started)

...