4cfae03606
When the caller of the RPC API has all the necessary information about how to access a Ceph cluster, then having to create configuration files before calling the RPC API is problematic (has to touch files owned by a local admin, changes must be removed again). But having to encode support for certain configuration options in SPDK is also problematic, because that might change depending on the librados version. The approach taken here is to merely pass through arbitrary key/value config options. Existing config files are ignored when that happens. The caller of the RPC then has full control over the connection setup and can be sure that he does not inherit settings from a local file accidentally. In addition, user management is supported now, with or without a config. This is useful for accessing a volume with a less privileged user. Previously, passing NULL to rados_create implicitly chose the "admin" user. Change-Id: I5e7f36092df663a3d7ac503c04fc624a8fe1208e Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Reviewed-on: https://review.gerrithub.io/430460 Reviewed-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> |
||
---|---|---|
.. | ||
bdev_rbd_rpc.c | ||
bdev_rbd.c | ||
bdev_rbd.h | ||
Makefile |