Describe the issue ================== Steps to configure stretched ceph cluster could be simplified further if we use feature of ceph orchestrator to set initial crush location of a host. So instead of manual setup of crush buckets for 2 zones/datacenters, done via set of `ceph osd crush add-bucket` and `ceph osd crush move` commands, we could specify the crush location in cluster service configuration yaml file directly. Describe the task you were trying to accomplish =============================================== Deploy a stretched ceph cluster for MetroDR. Suggestions for improvement =========================== In example of cluster service config file, show how to specify location of a host so that it's not necessary to create zone/datacenter buckets and move hosts there manually after initial cluster setup. Document URL ============ https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.10/html/configuring_openshift_data_foundation_for_metro-dr_with_advanced_cluster_management/configuring-rhcs-stretch-cluster_rhodf Chapter/Section Number and Title ================================ Section 3.5. Cluster bootstrapping with Cephadm Chapter 4. Configuring Red Hat Ceph Storage stretch cluster Product Version =============== ODF 4.10 Environment Details =================== MetroDR with ACM: deployment with stretched RHCS cluster. Any other versions of this document that also needs this update =============================================================== This text was introduced in 4.10, and should be fixed at least in 4.11. Additional information ====================== See also: - https://docs.ceph.com/en/latest/cephadm/host-management/?#setting-the-initial-crush-location-of-host - BZ 2089188 (ceph doc BZ for the same feature) - Note that this assumes that BZ 2089534 and BZ 2089535 are addressed first.
Looking at the current draft from stage (commit ef84b6f): The text mentions cluster spec yaml file with datacenter location labels, so that cluster bucket structure will be created during deployment, without any need for reconfiguration.