vsphere-csi-driver
vsphere-csi-driver copied to clipboard
kubernetes-sigs
Update CSI doc to support svMotion of volumes from one datastore to another.
Is this a BUG REPORT or FEATURE REQUEST?:
/kind feature
What happened: Currently CNS solution does not support svMotion of volumes from one datastore to another due to limitations in the first class disks(FCD). With 7.0 U3 release, FCD now support svMotion of FCDs via FCD APIs and VM APIs(FCD attached case). The only limitation now is that the client cannot perform concurrent svMotion of FCDs that are attached to the same VM using the VM API. I'm filing this issue to document the limited svMotion support in the doc.
vSphere CSI Driver 2.3 and 2.4 releases will not have support for svmotion of volumes. Once we add a support for svmotion we will update documentation.
Related to https://github.com/kubernetes-sigs/vsphere-csi-driver/issues/1210#issuecomment-947073031, can we please have an update on the availability of the support to svmotion volumes between Datastores? We are having to manually recreate a volume and sync multiple terabytes (a time-consuming and dangerous procedure) to avoid filling a datastore due to volumes being thin-provisioned.
@tgelter vSphere 7.0 Update 3 is released that exposes an API to perform svMotion of volumes. We plan to build a tool that helps with this. Please talk to the VMware accounts team to get in touch with our PM on the requirements.
@SandeepPissay is there some public doc related to svmotion API for volumes in vSphere 7.0 Update 3? Thanks!
@tgelter vSphere 7.0 Update 3 is released that exposes an API to perform svMotion of volumes. We plan to build a tool that helps with this. Please talk to the VMware accounts team to get in touch with our PM on the requirements.
Thanks @SandeepPissay, our VMware team has submitted SR 21269099510 to hopefully help get this on the the near-term roadmap. We appreciate all the great work being done by the team, but filled datastores are particularly impactful, so I'm sure you can appreciate our concern.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Hello @SandeepPissay, could you please provide an update on svMotion for CSI driver managed disks?
We have built tooling that can move CNS-managed volumes from one datastore to another. We are providing early access of this tool. If you need early access, please get in touch with VMware team. The plan is to GA the tool sometime soon (I cannot commit on the actual date).
Adding @gohilankit to this issue.
We have built tooling that can move CNS-managed volumes from one datastore to another. We are providing early access of this tool. If you need early access, please get in touch with VMware team. The plan is to GA the tool sometime soon (I cannot commit on the actual date).
Adding @gohilankit to this issue.
Fantastic news, thank you very much!
@SandeepPissay any word? When reaching out to the VMware team we were told we cannot get early access as it is close to release. However, that was a month ago.
@braunsonm We just made the tool generally available today! Please check https://github.com/vmware-samples/cloud-native-storage-self-service-manager for deployment and usage of the tool, which currently supports migration of CNS volumes between datastores.
Let us know if you have any questions.
Thanks @gohilankit I've followed up with a question on that repo.
I will close this issue since you can follow up on that repo.
@lipingxue: Closing this issue.
In response to this:
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
