Page History

...

Allocation logic: Refer to flow chart below. There are 3 primary use cases:-

• VM's current host has capacity - If VM's current host has capacity to scale up the vm then we put the vm in Reconfiguring state and lock the delta capacity. We then send the ReconfigureVMCommand to the HV to reconfigure the vm and scale it to the new values. Whether success / failure we put the vm back into running state, but release the delta capacity in case of failure.
• VM's current host doesnt doesn't have capacity but the vm's cluster has - If VM's current host doesnt have capacity, then we call up the planners to find a suitable host that can take the scaled up vm in the cluster. Once the host is found out we lock the new required capacity on the new host and migrate the vm to that host. Once migrated we send ReconfigureVMCommand to the HV. IF there is failure in reconfiguring here then we release the delta capacity on the new host.
• Cluster in which vm is running doesnt doesn't have capacity - we simply return failure to the end user saying that we dont have enough capacity to scale up the vm.

Web Services APIs

Following APIs needs to be changed:

...

• Created a subtask for this https://issues.apache.org/jira/browse/CLOUDSTACK-1041^{Image Removed}

Open Issues

• Should scale down be allowed? It can be explicitly prevented since none of the HVs/guest OS supports it.

...