Versions Compared

Old Version 35

changes.mady.by.user Nitin Mehta

Saved on

compared with

New Version 36

changes.mady.by.user Nitin Mehta

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Cloudstack will deploy the vms based the overcommit ratios. If the overcommit ratio of a particular cluster is updated, only the vms deployed hereafter will be deployed based on the updated overcommit ratios, this is ensured by storing overcommit ratio with which the vm got deployed stored in user_vm_details. The overcommit ratios for cluster will be stored in the cluster details table and will be inherited from global setting at the time of creation. Also whenever we add a host we will check of the host has the capabilities to perform the cpu and ram overcommiting. These capabilities will be stored in the db.

supported Hypervisors.

XenServer
KVM
VMware

APIs:

AddCluster Will be modified to include the cpu and ram overcommit values in the cluster parameters.

UpdateOvercommitRatio Updates the overcommit ratios of a cluster.

API Name

API parameters

API response

Available only for root admin

Addcluster

apart form the existing parameters we are adding cpuovercommitratio and ramovercommitratio

will contain additional details of cpu and ram overcommit ratios

yes

Updatecluster

cpuovercommitratio, memoryovercommitratio

returns the detais of the updated cluster along with the overcommit ratios

yes

If value is not provided we default it to 1, meaning no overcommiting of resources by default.

Capacity calculations.

Capacity calculation model will be changed to align with the hypervisors calculation. When a vm is deployed with "x" overprovisioing factor we want to guarantee (service offering of vm / x ) during its lifecycle even though the over provisioning changes.

...