Hi,

Thanks for adding this. When we wrote the support rados_create2 was not available so that
explains why we didn't use it. You could add support for it if you add it in the same way we
support the changed write API e.g. #if LIBRADOS_VERSION_CODE <= 17408
you only need to find out since which version rados_create2 is part of API.

I would also like to rebase things into 2 commits e.g. one for the rados-fd and one for the backend.
As far as I can see the two others are mostly fixes to one of the previous ones.

Hi Marco,

I see! I will have a closer look at the ceph integration in the next time. This is just a quick fix so we can use a non-admin key in our infrastructure and I wanted to make sure it will find it's way to upstream. I will have a look at a rados_create2() integration as well in the next time.

Did a rebase to combine the last commits.

Cheers,
Christian

I think there is one typo in the patch for the storage backend.

{ "id=", argument_id, 9 },

should probably be

{ "id=", argument_id, 3 },

Maybe we should also call it clientid ?
If you can fix that then I can merge the pull request.

Hi, I changed the name to clientid.

I see one typo e.g. clientd instead of clientid.
I close the pull request just saved the patches and will commit them after some cleanups under your name in master. So it will be visible by the end of the week when we sync to github.