Hi, CloudStack currently leverages storage overcommit/overprovisioning by specifying global setting storage.overprovisioning.factor I would like to extend the granularity of global params to make storage overprovisioning as a per primary store basis. Also it would allow admin to make more intuitive choice for overprovision factor depending upon the actual storage used.
Bug Reference : https://issues.apache.org/jira/browse/CLOUDSTACK-6092 Related : https://issues.apache.org/jira/browse/CLOUDSTACK-5806 FS : https://cwiki.apache.org/confluence/display/CLOUDSTACK/Storage+OverProvisioning+as+Per+Primary+Basis Thanks, Saksham
