Description of problem: It is important for the integration in TripleO that we allow for configuration of the clients without configuring other roles. In this scenario the list of mons and the fsid will be given by the user as input and, together with keys:, should make it possible to configure a client without requiring access to the mons role.
Fixed in https://github.com/ceph/ceph-ansible/commit/0032640b7e6b0ab08e3eb19be1bd1751c548a151
That commit is not yet on master.
Guillaume do we need to merge https://github.com/ceph/ceph-ansible/pull/1749 as well to be able to use the new feature?
Sebastien, Giulio, would you please confirm this BZ is completely resolved in master today?
Ken, https://github.com/ceph/ceph-ansible/pull/1749 should have fixed that, we need to test now.
@Seb, couple of questions: 1) Is this fix going to be in Ubuntu based ceph-ansible also? 2) What is the input format to specify clients to be configured?
@Harish, the fix will work for both Ubuntu and Red Hat systems. To configure a client just add a [clients] section in your inventory with the hostname you want to be become a client.
I am adding this issue as a dependency here. Because of this issue I propose this get moved back to ASSIGNED though I am happy to try to send a PR to address it next. https://github.com/ceph/ceph-ansible/issues/1848
I was able to deploy an overcloud, whose client configuration was done by ceph-ansible, which successfully uses external ceph clusters (able to create cinder volumes and upload glance images) by using the following: - https://github.com/ceph/ceph-ansible/pull/1850 - https://review.openstack.org/#/q/topic:bug/1714271
I am setting this to POST as the following upstream changes have merged. - https://github.com/ceph/ceph-ansible/pull/1850 - https://review.openstack.org/#/q/topic:bug/1714271
Would you please tag and announce a new upstream version with this change so we can rebase to it downstream?
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:3387