From 6eded8a1297bdabbdb9afaefac63e9380a16905c Mon Sep 17 00:00:00 2001 From: John Wilkins Date: Mon, 28 Oct 2013 18:03:28 -0700 Subject: [PATCH] doc: Fixes to normalize header hierarchy. Tweaked IA slightly. Signed-off-by: John Wilkins --- doc/radosgw/federated-config.rst | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/doc/radosgw/federated-config.rst b/doc/radosgw/federated-config.rst index 78ab3fbb30db0..2fdb242514702 100644 --- a/doc/radosgw/federated-config.rst +++ b/doc/radosgw/federated-config.rst @@ -16,7 +16,7 @@ regions, and with multiple zones for a region. Background ----------- +========== When you deploy a :term:`Ceph Object Store` service that spans geographical locales, configuring Ceph Object Gateway regions and metadata synchronization @@ -36,7 +36,7 @@ each zone (typical). You may also deploy a separate Ceph Storage Cluster for each zone if your requirements and resources warrant this level of redundancy. About this Guide ----------------- +================ In the following sections, we will demonstrate how to configure a federated cluster in two logical steps: @@ -703,10 +703,15 @@ with the following differences: #. `Start Gateway Instances`_. -#. `Replicate Data`_ by specifying the master zone of the master region as the - source zone and the master zone of the secondary region as the secondary - zone. When activating the ``radosgw-agent``, specify ``--metadata-only`` so - that it only copies metadata. +Replicate Metadata +------------------ + +`Replicate Data`_ by specifying the master zone of the master region as the +source zone and the master zone of the secondary region as the secondary +zone. When activating the ``radosgw-agent``, specify ``--metadata-only`` so +that it only copies metadata. For example:: + + radosgw-agent -c inter-region-data-sync.conf --metadata-only Once you have completed the foregoing procedure, you should have a cluster consisting of a master region (``us``) and a secondary region (``eu``) where -- 2.39.5