Bug 1732126
| Summary: | docs required for migrating existing single to multisite config | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Tim Wilkinson <twilkins> |
| Component: | Documentation | Assignee: | Ranjini M N <rmandyam> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Tejas <tchandra> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.3 | CC: | asriram, hyelloji, jharriga, kdreyer, vumrao |
| Target Milestone: | rc | ||
| Target Release: | 4.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | RHCS 4.1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-06-04 10:26:44 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1727980, 1809603 | ||
|
Description
Tim Wilkinson
2019-07-22 18:24:52 UTC
Tim - I think this doc https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html-single/object_gateway_guide_for_red_hat_enterprise_linux/index#migrating-a-single-site-system-to-multi-site-rgw covers converting already exisiting clusters to multisite clusters? Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri (In reply to Vikhyat Umrao from comment #1) > Tim - I think this doc > https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html- > single/object_gateway_guide_for_red_hat_enterprise_linux/index#migrating-a- > single-site-system-to-multi-site-rgw covers converting already existing > clusters to multisite clusters? <soapbox> I think the purpose of this bz was for customers who find themselves in a similar position where we had an existing cluster (with data to preserve and replicate) to which we wanted to apply a secondary site via the multisite playbook. Executing the playbook on the existing site and then on a secondary site did not accomplish that goal. It leaves the user in a situation where they must know how to undo what the playbook attempted and THEN apply the instructions in the aforementioned docs to convert their existing cluster into what multisite will accept as site1 PRIOR to running the ms playbook on both. Somewhere up front in the multisite docs it should distinguish whether the customer wishes to configure multisite on two new clusters and start fresh, or apply multisite to an existing cluster and have it replicated to a second so in that case it's clear they have to apply the steps outlined in the migrating-a-single-site-system-to-multi-site-rgw doc before they attempt to apply the ms playbook. </soapbox> (In reply to Tim Wilkinson from comment #4) > (In reply to Vikhyat Umrao from comment #1) > > Tim - I think this doc > > https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html- > > single/object_gateway_guide_for_red_hat_enterprise_linux/index#migrating-a- > > single-site-system-to-multi-site-rgw covers converting already existing > > clusters to multisite clusters? > > <soapbox> > I think the purpose of this bz was for customers who find themselves in a > similar position where we had an existing cluster (with data to preserve and > replicate) to which we wanted to apply a secondary site via the multisite > playbook. Executing the playbook on the existing site and then on a > secondary site did not accomplish that goal. It leaves the user in a > situation where they must know how to undo what the playbook attempted and > THEN apply the instructions in the aforementioned docs to convert their > existing cluster into what multisite will accept as site1 PRIOR to running > the ms playbook on both. Somewhere up front in the multisite docs it should > distinguish whether the customer wishes to configure multisite on two new > clusters and start fresh, or apply multisite to an existing cluster and have > it replicated to a second so in that case it's clear they have to apply the > steps outlined in the migrating-a-single-site-system-to-multi-site-rgw doc > before they attempt to apply the ms playbook. > </soapbox> Thanks, Tim for the feedback. I think this doc covers manual steps to convert the already existing single site to multi-site configuration. If I understand correct you looking for documentation to convert the single site to multisite with the help of ceph-ansible playbook. I think this feature is not available and hence it is not documented. Can you please open a Ceph Ansible feature request for converting the single site to multisite. That RFE already exists in bz 1739199. The only takeaway for me is that the multisite doc should determine whether the customer wishes to configure multisite on two new clusters or apply multisite to an existing cluster. Feel free to close. (In reply to Tim Wilkinson from comment #6) > That RFE already exists in bz 1739199. The only takeaway for me is that the > multisite doc should determine whether the customer wishes to configure > multisite on two new clusters or apply multisite to an existing cluster. > Feel free to close. Thanks, Tim. I agree with this part I will have doc team to mention the requirement in Multisite section that both clusters have to be new and also the doc[1] for multisite need in one place which is the object-storage guide[2]. [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://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html-single/object_gateway_guide_for_red_hat_enterprise_linux/index#rgw-multisite-rgw |