On 03/25/2014 12:18 AM, Ray Lv wrote:
Hi there,
We got a case to use the C APIs of compound operation in librados. These
interfaces are only exported as C APIs from Firefly release, such as
https://github.com/ceph/ceph/blob/firefly/src/include/rados/librados.h#L1834.
But our RADOS deployment will stick to the Dumpling release right now.
So here are a few questions on that:
* Is the librados in Firefly backward compatible with RADOS servers in
Dumpling by design?
Yes. ABI compatibility is always preserved. There are some rare issues
that require changing minor semantics, but they are few and documented
in release notes. In this case the most important change is with
firefly osds and firefly librados the individual op return codes in
compound operations are filled in.
* Is Firefly librados + Dumpling RADOS a configuration validated by
the community?
Firefly isn't out yet, but we are running upgrade tests that include
this kind of configuration.
We tried to backport these C APIs from Firefly to Dumpling and noticed
there are a couple of commits on it.
* Do you guys know a tracker issue or Blueprint that covers the C APIs
of compound operation in Firefly?
The related commits are:
https://github.com/ceph/ceph/commit/4425f9edaa9f4108bd4a693760c5d7be4359ee4a
and most of this pull request:
https://github.com/ceph/ceph/pull/1256
* And moreover, does it make sense to backport these C APIs from
Firefly to Dumpling?
Backporting those will likely be more trouble than it's worth.
I'd suggest developing against librados from the firefly branch.
If you want to check individual op return codes, use firefly osds as
well, otherwise dumpling osds will work just fine.
Josh
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
