[
https://issues.apache.org/jira/browse/CLOUDSTACK-5061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815066#comment-13815066
]
ASF subversion and git services commented on CLOUDSTACK-5061:
-------------------------------------------------------------
Commit 2210f1b0e49aaaaf15bfba4ec613546d69977003 in branch refs/heads/4.2 from
[~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2210f1b ]
CLOUDSTACK-5061 - Cloudstack doesn't consider storage overprovisioning factor
when using thin Provisioning over VMWare VMFS datastores
Fix is use the storage overprovisioning factor (global configuration parameter
"storage.overprovisioning.factor") to calculate total provisioning capacity for
storage space allocation over VMFS based storage pools as well.
There are two level of thin provisioning provided in VMware, storage level and
file-level (VMDK) thin provisioning. in CloudStack, all volumes are provisioned
with thin VMDK format, so at hypervisor level, we ALWAYS do thin provisioning.
If storage vendor has the ability to provide storage level thin provisioning in
addition to VMDK thin provisioning, it is also allowed since it is transparent
to Cloudstack.
Signed-off-by: Sateesh Chodapuneedi <[email protected]>
> Cloudstack doesn't consider storage overprovisioning factor when using thin
> Provisioning over VMWare VMFS datastores
> --------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-5061
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5061
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
> Affects Versions: 4.2.0
> Reporter: Sateesh Chodapuneedi
> Assignee: Sateesh Chodapuneedi
> Priority: Critical
> Fix For: 4.2.1
>
>
> Cloudstack does not let us to create new VMs as it cannot calculate a free
> space correctly when using Thin Provisioning with VMware. It calculates space
> from the size of the volumes rather then what is truly utilized on the SAN.
> DETAILS
> ===================
> 1. DB
> mysql> select p.name, p.pool_type, p.used_bytes, p.capacity_bytes,
> sum(v.size) as volumes_allocated from volumes v join storage_pool p on
> v.pool_id=p.id where v.removed is null group by v.pool_id;
> -------------------------------------------------------------------------------------
> name pool_type used_bytes capacity_bytes volumes_allocated
> -------------------------------------------------------------------------------------
> PrimaryStorage1 VMFS 804432904192 1023812829184 940446842880
> PrimaryStorage2 VMFS 901673648128 1023812829184 347791687680
> -------------------------------------------------------------------------------------
> 2 rows in set (0.01 sec)
> 2. vCenter reports as the datastore size, storage allocated, and storage used
> Capacity : 953.50GB
> Provisioned Space : 944.76GB
> Free Space : 751.60GB
--
This message was sent by Atlassian JIRA
(v6.1#6144)
