Is disk type=thin ignored for vsan in favor or vsan storage policy ?
Opened this issue · 2 comments
Support Question
When trying to enable thin provisionning for vsan disks using persistent disk type=thin
, I observe in vsphere UI that the disk isn't explicitely labelled as thin provisionning, despite the cpi vsphere api calls do indeed specify it
https://bosh.io/docs/vsphere-cpi/#disk-pools
type [String, optional]: Virtual disk type used for persistent disks: thick, thin, preallocated, eagerZeroedThick. Defaults to preallocated. Available in v12. Overrides the global default_disk_type.
CPI disk log:
<backing xsi:type="VirtualDiskFlatVer2BackingInfo">
<fileName>[my-vsan-datastore-name]
12e55064-f0ef-b748-1987-e20a67700087/Integration/disks/disk-7bc4322d-c54f-4c0d-bc3e-2c4873db179c.vmdk
</fileName>
<datastore type="Datastore">datastore-18</datastore>
<backingObjectId>34aa8666-8486-446a-f404-e20a67700073</backingObjectId>
<diskMode>independent_persistent</diskMode>
<split>false</split>
<writeThrough>false</writeThrough>
<thinProvisioned>true</thinProvisioned>
<eagerlyScrub>false</eagerlyScrub>
<uuid>6000C295-de95-41db-306d-3628ce4aaf2f</uuid>
<contentId>f1261bf083a0fcddc6d7216afffffffe</contentId>
<digestEnabled>false</digestEnabled>
<sharing>sharingNone</sharing>
</backing>
Is this the normal expected behavior from VSAN disks, and would a PR on bosh-docs be accepted to clarify scope of persistent disk types (i.e. ignored on vsan) ?
You can also reach out to us via:
@klakin-pivotal, you have any thoughts on this?
@gberche-orange If you change the disk provisioning type to thick
or eagerZeroedThick
, does that change the VM storage policy of the related disk?
Given that it seems like we're passing through the instruction to thin provision the disk to vCenter, I wonder if this is a bug in the IAAS... whether a vCenter display bug, or a VSAN bug.