commit 461ed60d737849d53612e30610adc64aa06728ba
author Dzmitry Stremkouski <dstremkouski@mirantis.com> Tue Aug 20 16:58:02 2019 +0200
committer Dzmitry Stremkouski <dstremkouski@mirantis.com> Thu Aug 29 10:19:42 2019 +0200
tree ef55b17cd2375e10e6a9c60592fda94583b9ab2d
parent d2aab1c1e4b97459c0483eb3ad9270d05503bc51

[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