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

Add verify functionality to the testing tool #108

Open
Rakshith-R opened this issue Jan 16, 2025 · 1 comment · May be fixed by #117
Open

Add verify functionality to the testing tool #108

Rakshith-R opened this issue Jan 16, 2025 · 1 comment · May be fixed by #117
Assignees

Comments

@Rakshith-R
Copy link
Contributor

Is your feature request related to a problem?/Why is this needed

Currently the testing tool snapshot-metadata-lister only lists the changed blocks.
There needs to be a way to verify end to end the working of changed block tracking framework.

Describe the solution you'd like in detail

A verify functionality that works as follows:

  • GetMetadataAllocated:
    • source-device: restored PVC from the target snapshot
    • target-device: fresh PVC
    • verify: this function would copy the changed blocks returned from the csi-driver from source-device to the target device and then compares both the devices to make sure there's no differences.
  • GetMetadataDelta:
    • source-device: restored PVC from the target snapshot
    • target-device: restored PVC from the base snapshot
    • verify: this function would copy the changed blocks returned from the csi-driver from source-device to the target device and then compares both the devices to make sure there's no differences.

Describe alternatives you've considered

The above approach seems like the best way to test changed block tracking framework end to end without knowing the
internals of a storage system.

Additional context

@Rakshith-R
Copy link
Contributor Author

/assign

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.

1 participant