-
Notifications
You must be signed in to change notification settings - Fork 247
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 support for rbd_create4 into ceph-go's rbd library #40
Comments
Adding this should not be a problem at all. The fastest approach is to submit a pull request. But I'll put this on the todo list. |
@noahdesu Can do. I do have a question though, there are a few ways of doing this, would it be preferred if somehow the existing I could try taking cues from how librbdpy does it and submit a PR, but it'd be nice to know if there's a convention/style being followed here. |
I think that adding something like |
If the goal is to maintain a go-ceph repo that can build against any installed librados, perhaps consider setting build tags via Makefile shell commands. For example, to handle the deprecation warnings mentioned in #42, a
Conditionally set
and for older libraries:
This would work so long as something (i.e., the Makefile) would set the build tag. It may not be so convenient if the go-ceph library was simply being slurped in by Alternatively, just git branch and maintain a different branch for older (LTS) releases of librados. Since the Ceph client libraries are generally backwards compatible, I don't see any harm in primarily / only supporting the latest Ceph client C library. |
Hello, I'm automatically closing all issues filed prior to 2018 that have not been commented on recently. If this issue is still relevant to you please reopen the issue and restart the discussion. Thank you for your understanding. |
Title says it all. librdb provides a rbd_create4 method. This method is not available in ceph-go's rbd implementation does not provide this at the moment.
Can this method be added?
The text was updated successfully, but these errors were encountered: