Navigation Menu

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

[FEATURE] Rebuild logical volumes/replicas with SPDK #3044

Closed
keithalucas opened this issue Sep 21, 2021 · 2 comments
Closed

[FEATURE] Rebuild logical volumes/replicas with SPDK #3044

keithalucas opened this issue Sep 21, 2021 · 2 comments
Assignees
Labels
area/replica Volume replica where data is placed area/v2-data-engine v2 data engine (SPDK) duplicated experimental beta highlight Important feature/issue to highlight priority/0 Must be fixed in this release (managed by PO)
Milestone

Comments

@keithalucas
Copy link

Create a proof of concept to demonstrate that it is possible to recreate a SPDK logical volume from an existing logical volume with snapshots. Both volumes should have the same snapshots and the same data at each snapshot.

First, do this for two logical volumes running on the same spdk_tgt instance. To ensure that the data is copied, a different logical volume with a different underlying bdev can be used.

Develop a means to extract the "blob" for each snapshot. This is needed to verify that the data in each snapshot is exactly the same.

Also, add the ability to revert the logical volumes to a specific snapshot. Verify that original volume and copied volume contain the same data after reverting both to the same snapshot.

Add the ability to rebuild the logical volumes from two separate spdk_tgt instances running on different hosts. Try to use NVMeoF to expose the blobs for each snapshot.

@keithalucas keithalucas added the kind/poc Potential feature request but need POC label Sep 21, 2021
@yasker yasker added this to the v1.3.0 milestone Sep 21, 2021
@innobead innobead added the priority/0 Must be fixed in this release (managed by PO) label Sep 27, 2021
@innobead innobead added the highlight Important feature/issue to highlight label Oct 21, 2021
@innobead
Copy link
Member

innobead commented Dec 6, 2021

Moving to theanalysis state.

@innobead innobead added the area/v2-data-engine v2 data engine (SPDK) label Mar 31, 2022
@keithalucas keithalucas modified the milestones: v1.3.0, v1.4.0 Jun 7, 2022
@innobead innobead assigned joshimoo and unassigned keithalucas Jun 29, 2022
@innobead innobead modified the milestones: v1.4.0, v1.5.0 Nov 29, 2022
@innobead innobead changed the title [POC] Rebuild logical volumes/replicas with SPDK [FEATURE] Rebuild logical volumes/replicas with SPDK Nov 30, 2022
@innobead innobead added area/replica Volume replica where data is placed experimental beta and removed kind/poc Potential feature request but need POC labels Dec 4, 2022
@innobead
Copy link
Member

innobead commented Jan 5, 2023

Track #5216 instead.

@innobead innobead closed this as not planned Won't fix, can't repro, duplicate, stale Jan 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/replica Volume replica where data is placed area/v2-data-engine v2 data engine (SPDK) duplicated experimental beta highlight Important feature/issue to highlight priority/0 Must be fixed in this release (managed by PO)
Projects
Status: Resolved/Scheduled
Development

No branches or pull requests

5 participants