Bug 1732135 - multisite docs for fresh config need to include ceph-ansible
Summary: multisite docs for fresh config need to include ceph-ansible
Keywords:
Status: NEW
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: Documentation
Version: 3.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 4.1
Assignee: ceph-docs@redhat.com
QA Contact: Tejas
URL:
Whiteboard:
Depends On:
Blocks: 1727980
TreeView+ depends on / blocked
 
Reported: 2019-07-22 18:49 UTC by Tim Wilkinson
Modified: 2020-01-14 07:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Tim Wilkinson 2019-07-22 18:49:17 UTC
Description of problem:
The existing documentation for multisite configuration [1] does not include the ceph-ansible playbook [2]. All of the steps outlined in section 3.6.1 of the doc mentioned are included in the playbook. As it was for us, if we used the instructions to do it all on the cmdline rather than the playbook, the procedure is broken by having the user limiting the playbook rerun to just the RGW nodes, which creates new keyrings and breaks the existing cluster.


[1] https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html-single/installation_guide_for_red_hat_enterprise_linux/#configuring-a-multisite-ceph-object-gateway-install

[2] https://github.com/ceph/ceph-ansible/blob/master/README-MULTISITE.md



Version-Release number of selected component (if applicable):
7.6 (Maipo)   3.10.0-957.el7.x86_64
ceph-base.x86_64   2:12.2.8-128.el7cp


How reproducible:
Consistent. We were never able to successfully configure multisite with existing documentation and had far more success using the playbook.

Comment 1 Tim Wilkinson 2019-07-22 18:55:51 UTC
Correction, section 3.6.1 does reference the playbook's use but is missing some of the info included in the upstream readme (e.g.,  rgw_multisite_endpoints_list) and it does have the user limit the playbook to the RGWs which failed for me for the reason mentioned above.

Comment 2 Giridhar Ramaraju 2019-08-05 13:11:29 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 3 Giridhar Ramaraju 2019-08-05 13:12:28 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri


Note You need to log in before you can comment on or make changes to this bug.