[radosgw, upgrades] Fix for radosgw keyring path and user
Issue:
If customer has its own external ceph cluster and have
specified only one keyring for radosgw it is possible to use
linux.system.file to control this keyring, but it is not
possible to specify path properly for this keyring.
Also it is not possible to specify arbitrary username for keyring.
Fix:
Specify keyring_path variable. If not specified then it
is calculated by default.
Specify keyring_user variable. If not specified then it
is calculated by default.
What has been fixed:
- Added keystone_path variable
- Added keystone_user variable
- Added tests
- Updated README
Prod-Related: PROD-32721
Change-Id: I4b59442ac6d892ec33063eca5e289894d05257cd
diff --git a/README.rst b/README.rst
index a0c3d3c..8509a3b 100644
--- a/README.rst
+++ b/README.rst
@@ -544,6 +544,16 @@
osd: "allow class-read object_prefix rdb_children, allow rwx pool=images"
+Specify alternative keyring path and username
+
+.. code-block:: yaml
+
+ ceph:
+ radosgw:
+ keyring_user: radosgw.gateway
+ keyring_path: /etc/ceph/keyring.radosgw.gateway
+
+
Generate CRUSH map - Recommended way
-----------------------------------