Sandeep Pissay
Sandeep Pissay
> If there is anythin we can do to help add context, use cases, referneces etc. In order to help push this forwards i would be glad to help with...
@farodin91 I'm trying to understand why you want to relocate the volumes from one datastore to another. Is it because you want to decommission the datastore, or is it because...
We have heard the following storage vMotion requirements for CNS volumes: 1. Capacity load balancing between storage (could be mixed datastore types like VMFS, NFS, vSAN, vVol). 2. Datastore maintenance...
> @SandeepPissay For our case mainly, 2 and 3 would best match for our requirements. @farodin91 regarding requirement (3), do you have separate vCenters managing the datacenters or a single...
/remove-lifecycle stale
@tgelter we are looking into it. Cc @RaunakShah
The plan is to implement the orphan volume detection and removal in [CNS Manager](https://github.com/vmware-samples/cloud-native-storage-self-service-manager). I filed an issue in that repo to track it - https://github.com/vmware-samples/cloud-native-storage-self-service-manager/issues/2. I'm closing this issue...
@tgelter we added support for thick volume provisioning in vSphere 8.0 for VMFS datastores. See https://core.vmware.com/resource/whats-new-vsphere-8-core-storage#sec21636-sub5. With this, you should be able to define an SPBM policy with FullyInitialized capability...
@tgelter do you think we can close this issue now since you have a solution to create thick volumes and also move them between datastores?