Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate a single PVC to the ceph-csi volume #17

Closed
travisn opened this issue Oct 26, 2021 · 1 comment · Fixed by #18
Closed

Migrate a single PVC to the ceph-csi volume #17

travisn opened this issue Oct 26, 2021 · 1 comment · Fixed by #18
Assignees

Comments

@travisn
Copy link
Member

travisn commented Oct 26, 2021

While #12 would provide an option to migrate all PVCs in a namespace, we also need the option to migrate a single PVC. Admins will want more fine-grained control to perform the migration to do it in a very controlled way per-application. Taking down an application would be disruptive, so it is especially critical if there are multiple apps in the same namespace.

@subhamkrai
Copy link
Collaborator

hmm agree and now, I think this issue Migrate a single PVC to the ceph-csi volume more useful/reliable option for the users than migrating all the PVC at once as you said this is very disruptive operation. So, in this we'll ask user to give name of pvc they want to migrate instead of the name of storageClass (which is what we are doing currently)

@subhamkrai subhamkrai self-assigned this Oct 26, 2021
subhamkrai added a commit to subhamkrai/persistent-volume-migrator that referenced this issue Oct 28, 2021
adding flag `pvcName` which take name of the
pvc user want to migrate and along with sourcestorageClass
flag.
This commit will enable support for single PVC.

Closes: ceph#17
Signed-off-by: subhamkrai <srai@redhat.com>
subhamkrai added a commit to subhamkrai/persistent-volume-migrator that referenced this issue Oct 28, 2021
adding flag `pvcName` which take name of the
pvc user want to migrate and along with sourcestorageClass
flag.
This commit will enable support for single PVC.

Closes: ceph#17
Signed-off-by: subhamkrai <srai@redhat.com>
subhamkrai added a commit to subhamkrai/persistent-volume-migrator that referenced this issue Oct 29, 2021
adding flag `pvcName` which take name of the
pvc user want to migrate and along with sourcestorageClass
flag.
This commit will enable support for single PVC.

Closes: ceph#17
Signed-off-by: subhamkrai <srai@redhat.com>
subhamkrai added a commit to subhamkrai/persistent-volume-migrator that referenced this issue Oct 29, 2021
adding flag `pvcName` which take name of the
pvc user want to migrate and along with sourcestorageClass
flag.
This commit will enable support for single PVC.

Closes: ceph#17
Signed-off-by: subhamkrai <srai@redhat.com>
subhamkrai added a commit to subhamkrai/persistent-volume-migrator that referenced this issue Nov 8, 2021
adding flag `pvcName` which take name of the
pvc user want to migrate and along with sourcestorageClass
flag.
This commit will enable support for single PVC.

Closes: ceph#17
Signed-off-by: subhamkrai <srai@redhat.com>
subhamkrai added a commit to subhamkrai/persistent-volume-migrator that referenced this issue Nov 8, 2021
adding flag `pvcName` which take name of the
pvc user want to migrate and along with sourcestorageClass
flag.
This commit will enable support for single PVC.

Closes: ceph#17
Signed-off-by: subhamkrai <srai@redhat.com>
subhamkrai added a commit to subhamkrai/persistent-volume-migrator that referenced this issue Nov 9, 2021
adding flag `pvcName` which take name of the
pvc user want to migrate and along with sourcestorageClass
flag.
This commit will enable support for single PVC.

Closes: ceph#17
Signed-off-by: subhamkrai <srai@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants