Page History

...

*All the perameters are optional but of the two parameters in bold atleast one is required.
If value is not provided we default it to 1, meaning no overcommiting of resources by default.

DB changes:

Adding new colums to table cluster to store There will be no changes to the db. We will add the cpu and ram overcommit ratios .

Upgrade scenario:

On upgrade the existing cluster table will be upadated with above new columnsin the cluster_details table.

Caveats

What should the behavior be if admin changes the overcommit factor for a cluster that conflicts with the current situation. For example,lets assume Cluster X has an over commit factor of 1.5x for memory and the admin wants to change this to 1x - i.e no overcommit (or changes from 2x to 1.5x) - however, based on the "older" factor, CS might already have assigned more VMs - when the admin reduces the overcommit value 

...