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

Ceph RBD rollback image #1014

Closed
BadKid90s opened this issue Jul 29, 2024 · 4 comments
Closed

Ceph RBD rollback image #1014

BadKid90s opened this issue Jul 29, 2024 · 4 comments

Comments

@BadKid90s
Copy link

How to determine if Ceph RBD rollback image is successful?

How to determine if the rollback is successful using the command line or HTTP API?

@phlogistonjohn
Copy link
Collaborator

Are you asking if how to tell if the function

func (snapshot *Snapshot) Rollback() error {
succeeded?

On an API level you should be checking the error is not nil. If you mean on some sort of higher level, you'd probably have to build something like a function that checksums an image before snapshotting and then verifies it after rollback. If you asking for something even more than that I suggest talking to the Ceph team directly because go-ceph is focused on making the Ceph APIs available, not making sure they work.

I don't really know what command line or HTTP you might be referring to. Again, if you're looking for general Ceph help you may want to try the ceph lists: https://lists.ceph.io/hyperkitty/list/[email protected]/

@BadKid90s
Copy link
Author

Perform a checksum on the image before the snapshot, and then validate it after the rollback. How should it be operated? How to calculate the comparative checksum?

@phlogistonjohn
Copy link
Collaborator

If I was going to implement that I would use the image read apis to copy the bytes into one of Go's hash algorithms like sha256.

Just as a reminder go-ceph provides the Ceph apis as a golang library, what you do with those apis is up to you. So take my suggestion above with a grain of salt, because I really don't know what your ultimate goal is. :-)

Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contribution.

@github-actions github-actions bot added the Stale label Aug 30, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants