RE: [PROPOSAL] Storage OverProvisioning as Per Primary Basis
Hi, Created review request at https://reviews.apache.org/r/19036/ Tested the common scenarios and added Marvin test for the same. Thanks, Saksham -Original Message- From: Saksham Srivastava [mailto:saksham.srivast...@citrix.com] Sent: Monday, February 17, 2014 4:56 PM To: dev@cloudstack.apache.org Subject: RE: [PROPOSAL] Storage OverProvisioning as Per Primary Basis Koushik/Mike, Thanks for comments. The current behavior is that we calculate the totalOverProvCapacity (storage.overprovisioning.factor * total storage capacity) for the destination PS. When volume is being migrated across PS, the destination PS must have a higher totalOverProvCapacity than the expected total allocated space. This feature will be on same lines as the current behavior except that now the storage.overprovisioning.factor will be a configurable parameter for the PS. I will include this information with more detailed capacity computation along with more explanation on upgrade scenarios as soon as cwiki comes up. As Mike pointed out, we can have Primary Storages at 3 levels : Local Storage (HOST), Cluster Storage(CLUSTER) , ZWPS (ZONE). Storage scope was introduced for enhancing Granularity for configuration parameters in 4.2, so it would be good to use the same as an individual per-primary setting instead of multi scopes. Thanks, Saksham -Original Message- From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] Sent: Saturday, February 15, 2014 4:25 AM To: dev@cloudstack.apache.org Subject: Re: [PROPOSAL] Storage OverProvisioning as Per Primary Basis 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+OverPro visioning+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 cloudhttp://solidfire.com/solution/overview/?video=play *(tm)*
RE: [PROPOSAL] Storage OverProvisioning as Per Primary Basis
Koushik/Mike, Thanks for comments. The current behavior is that we calculate the totalOverProvCapacity (storage.overprovisioning.factor * total storage capacity) for the destination PS. When volume is being migrated across PS, the destination PS must have a higher totalOverProvCapacity than the expected total allocated space. This feature will be on same lines as the current behavior except that now the storage.overprovisioning.factor will be a configurable parameter for the PS. I will include this information with more detailed capacity computation along with more explanation on upgrade scenarios as soon as cwiki comes up. As Mike pointed out, we can have Primary Storages at 3 levels : Local Storage (HOST), Cluster Storage(CLUSTER) , ZWPS (ZONE). Storage scope was introduced for enhancing Granularity for configuration parameters in 4.2, so it would be good to use the same as an individual per-primary setting instead of multi scopes. Thanks, Saksham -Original Message- From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] Sent: Saturday, February 15, 2014 4:25 AM To: dev@cloudstack.apache.org Subject: Re: [PROPOSAL] Storage OverProvisioning as Per Primary Basis 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+OverPro visioning+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 cloudhttp://solidfire.com/solution/overview/?video=play *(tm)*
Re: [PROPOSAL] Storage OverProvisioning as Per Primary Basis
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
Re: [PROPOSAL] Storage OverProvisioning as Per Primary Basis
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 cloudhttp://solidfire.com/solution/overview/?video=play *(tm)*
