RepoMirrors/ceph
1
0
Fork 0
mirror of https://github.com/ceph/ceph synced 2025-03-04 15:31:44 +00:00
Code Issues Packages Projects Releases Wiki Activity

doc: fix broken hyper link

Browse Source 
and always reference multisite.rst using tha label not the file.

Signed-off-by: Kefu Chai <kchai@redhat.com>
This commit is contained in:
Kefu Chai 2020-08-31 09:30:25 +08:00
parent ca1cca0abc
commit 5238f9f62b
3 changed files with 5 additions and 10 deletions

5
doc/radosgw/cloud-sync-module.rst
View File

@ -195,7 +195,7 @@ Minimum parts size to use when syncing objects using multipart upload.
How to Configure
~~~~~~~~~~~~~~~~
See `Multisite Configuration`_ for how to multisite config instructions. The cloud sync module requires a creation of a new zone. The zone
See :ref:`multisite` for how to multisite config instructions. The cloud sync module requires a creation of a new zone. The zone
tier type needs to be defined as ``cloud``:
::
@ -242,6 +242,3 @@ For example, creating a new profile for buckets starting with {prefix}:
An entry can be removed by using ``--tier-config-rm={key}``.
.. _Multisite Configuration: ./multisite

3
doc/radosgw/pubsub-module.rst
View File

@ -42,7 +42,7 @@ be accessed directly, but need to be pulled and acked using the new REST API.
PubSub Zone Configuration
-------------------------
The pubsub sync module requires the creation of a new zone in a `Multisite`_ environment.
The pubsub sync module requires the creation of a new zone in a :ref:`multisite` environment...
First, a master zone must exist (see: :ref:`master-zone-label`),
then a secondary zone should be created (see :ref:`secondary-zone-label`).
In the creation of the secondary zone, its tier type must be set to ``pubsub``:
@ -637,6 +637,5 @@ Request parameters:
- event-id: id of event to be acked
.. _Multisite : ../multisite
.. _Bucket Notification : ../notifications
.. _Bucket Operations: ../s3/bucketops

7
doc/radosgw/sync-modules.rst
View File

@ -4,7 +4,7 @@ Sync Modules
.. versionadded:: Kraken
The `Multisite`_ functionality of RGW introduced in Jewel allowed the ability to
The :ref:`multisite` functionality of RGW introduced in Jewel allowed the ability to
create multiple zones and mirror data and metadata between them. ``Sync Modules``
are built atop of the multisite framework that allows for forwarding data and
metadata to a different external tier. A sync module allows for a set of actions
@ -38,7 +38,7 @@ for configuring any sync plugin
Requirements and Assumptions
----------------------------
Let us assume a simple multisite configuration as described in the `Multisite`_
Let us assume a simple multisite configuration as described in the :ref:`multisite`
docs, of 2 zones ``us-east`` and ``us-west``, let's add a third zone
``us-east-es`` which is a zone that only processes metadata from the other
sites. This zone can be in the same or a different ceph cluster as ``us-east``.
@ -49,7 +49,7 @@ will not serve any end user requests directly.
Configuring Sync Modules
------------------------
Create the third zone similar to the `Multisite`_ docs, for example
Create the third zone similar to the :ref:`multisite` docs, for example
::
@ -92,7 +92,6 @@ Now start the radosgw in the zone
.. _`Multisite`: ../multisite
.. _`elasticsearch sync module`: ../elastic-sync-module
.. _`elasticsearch`: ../elastic-sync-module
.. _`cloud sync module`: ../cloud-sync-module