mike-tutkowski removed a comment on issue #4911: URL: https://github.com/apache/cloudstack/issues/4911#issuecomment-819038730
Like what @skattoju4 mentioned: It used to be that you would just manually set the capacity bytes for managed storage. The idea is that you might have a large SAN (like a SolidFire SAN), which does all sorts of fancy things like compressing and de-duplicating data - in addition to thin provisioning. That being the case, whatever the physical storage capacity is of this kind of a SAN, you might get, say, 2 - 3x more out of it because of those data-efficiency techniques (of course, depending on the type of data you're storing). In any case, to make this easy to use from CloudStack, the admin just sets a capacity number manually. It can be large or small. This number should not automatically be updated at any point: It's just a number that an admin can manually update. As an example, let's say you pick a (small) number like 100 GB. If you create a volume that has a 10 GB virtual size, then you now only have 90 GB left from this managed storage. If you create a back-end snapshot on this 10-GB volume, that takes another 10 GB off of the 100 GB of the managed storage (even though neither the volume nor the snapshot is likely really taking10 GB of physical capacity on the SAN). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
