[
https://issues.apache.org/jira/browse/CLOUDSTACK-10281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16364745#comment-16364745
]
Isaac Truett commented on CLOUDSTACK-10281:
-------------------------------------------
I'm attaching the changes Alex and I made while trying to modify the clone
behavior.
Adding a VirtualDeviceConfigSpec to change the disk provisioning doesn't appear
to do anything here. Is there something else we need to do to change the device
configuration during the clone process?[^cloudstack-vmware-provisioning.zip]
> 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
> Attachments: cloudstack-vmware-provisioning.zip
>
>
> 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)
