Just a reminder here that primary storage can also be at the zone level as of 4.2.
On Fri, Feb 14, 2014 at 4:44 AM, Koushik Das <koushik....@citrix.com> wrote: > Please add more details for upgrade scenario. Also can you give some > examples as to how the capacity computation is done for operations where > the volume gets migrated from one PS to another having different over > provisioning factors. > > Is there any value add if you give this also at cluster scope? > > -Koushik > > On 14-Feb-2014, at 2:13 PM, Saksham Srivastava < > saksham.srivast...@citrix.com> wrote: > > > 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 > > > > -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play> *(tm)*
