You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Alex Wheeler (JIRA)" <ji...@apache.org> on 2018/02/09 16:50:00 UTC
[jira] [Updated] (CLOUDSTACK-10281) vSphere VM disks do not honor
the Service Offering Provisioning Type selected
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Wheeler updated CLOUDSTACK-10281:
--------------------------------------
Description:
Regardless of the Provisioning Type selected (Fat, Sparse, Thin), all instantiated vSphere VM disks are thin when the storage supports thin.
Doing a little sleuthing, it turns out that the creation of data disks is easily fixed in *VmwareStorageProcessor.java*
However, the root disk is always created as a clone with the same disk type as the template, which being ova is always thin. The vSphere API seems to allow specifying the disk type during clone, and we've taken a stab at that, but so far to no avail.
Hoping someone can shed some light on this. Code samples forthcoming.
We are using Cloudstack 4.10, and vSphere 6.0
was:
Regardless of the Provisioning Type selected (Fat, Sparse, Thin), all instantiated vSphere VM disks are thin when the storage supports thin.
Doing a little sleuthing, it turns out that the creation of data disks is easily fixed in *VmwareStorageProcessor.java*
However, the root disk is always created as a clone with the same disk type as the template, which being ova is always thin. The vSphere API seems to allow specifying the disk type during clone, and we've taken a stab at that, but so far to no avail.
Hoping someone can shed some light on this. Code samples forthcoming.
> vSphere VM disks do not honor the Service Offering Provisioning Type selected
> -----------------------------------------------------------------------------
>
> Key: CLOUDSTACK-10281
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10281
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Template, VMware
> Affects Versions: 4.10.0.0
> Reporter: Alex Wheeler
> Priority: Minor
>
> Regardless of the Provisioning Type selected (Fat, Sparse, Thin), all instantiated vSphere VM disks are thin when the storage supports thin.
> Doing a little sleuthing, it turns out that the creation of data disks is easily fixed in *VmwareStorageProcessor.java*
> However, the root disk is always created as a clone with the same disk type as the template, which being ova is always thin. The vSphere API seems to allow specifying the disk type during clone, and we've taken a stab at that, but so far to no avail.
> Hoping someone can shed some light on this. Code samples forthcoming.
> We are using Cloudstack 4.10, and vSphere 6.0
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)