The approach here is to use a flat file for the KV store for a VVOL based volume. Natively created sidecars for vvol volumes are vvols themselves, and there is no API to read/write a sidecar natively. Python interfaces to use existing native libraries don't seem to work well and hence unreliable to use for the KV store. For this reason, we don't use natively created sidecars for VVOL based volumes. Instead we create a flat file in the dockvols folder thats named just like a sidecar but created by the ESX service as a flat file.
Remove volume and clone volume workflows are updated with minor changes to handle the KV stores for VVOLs. Changes are minor in vmdk_ops.py and all handling is only in kvESX.py.
fixes #1998
The approach here is to use a flat file for the KV store for a VVOL based volume. Natively created sidecars for vvol volumes are vvols themselves, and there is no API to read/write a sidecar natively. Python interfaces to use existing native libraries don't seem to work well and hence unreliable to use for the KV store. For this reason, we don't use natively created sidecars for VVOL based volumes. Instead we create a flat file in the dockvols folder thats named just like a sidecar but created by the ESX service as a flat file.
Remove volume and clone volume workflows are updated with minor changes to handle the KV stores for VVOLs. Changes are minor in vmdk_ops.py and all handling is only in kvESX.py.