Skip to content

Commit 7ca378d

Browse files
authored
Merge pull request ceph#63907 from zdover23/wip-doc-2025-06-12-radosgw-cloud-transition-1-of-x
doc/radosgw: edit cloud-transition (1 of x) Reviewed-by: Anthony D'Atri <[email protected]>
2 parents 84a6c76 + 9ad5a65 commit 7ca378d

File tree

1 file changed

+16
-13
lines changed

1 file changed

+16
-13
lines changed

doc/radosgw/cloud-transition.rst

Lines changed: 16 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -2,17 +2,18 @@
22
Cloud Transition
33
================
44

5-
This feature enables transitioning S3 objects to a remote cloud service as part
6-
of `object lifecycle <https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html>`_
5+
This feature makes it possible to transition S3 objects to a remote cloud
6+
service as part of the `object lifecycle
7+
<https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html>`_
78
via :ref:`storage_classes`. The transition is unidirectional: data cannot be
8-
transitioned back from the remote zone. The goal of this feature is to enable
9-
data transition to multiple cloud providers. The currently supported cloud
10-
providers are those that are compatible with AWS (S3).
9+
transitioned back from the remote zone. The purpose of this feature is to
10+
enable data transition to multiple cloud providers. Cloud providers compatible
11+
with AWS (S3) are supported.
1112

12-
A special storage class of tier type ``cloud-s3`` or ``cloud-s3-glacier``
13-
is used to configure the remote cloud S3 object store service to which
14-
data is transitioned. These are defined in terms of zonegroup placement
15-
targets and, unlike regular storage classes, do not need a data pool.
13+
We use a special storage class of tier type ``cloud-s3`` or
14+
``cloud-s3-glacier`` to configure the remote cloud S3 object store service to
15+
which data is transitioned. These classes are defined in terms of zonegroup
16+
placement targets and, unlike regular storage classes, do not need a data pool.
1617

1718
User credentials for the remote cloud object store service must be
1819
configured. Note that source ACLs will not be preserved. It is possible
@@ -76,17 +77,19 @@ Cloud Transition Specific Configurables
7677

7778
* ``host_style`` (path | virtual)
7879

79-
Type of host style to be used when accessing the remote cloud S3 service (default: ``path``).
80+
Type of host style to be used when accessing the remote cloud S3 service
81+
(default: ``path``).
8082

8183
* ``acls`` (array)
8284

8385
Contains a list of ``acl_mappings``.
8486

8587
* ``acl_mapping`` (container)
8688

87-
Each ``acl_mapping`` structure contains ``type``, ``source_id``, and ``dest_id``. These
88-
define the ACL mutation to be done on each object. An ACL mutation makes it possible to
89-
convert a source userid to a destination userid.
89+
Each ``acl_mapping`` structure contains ``type``, ``source_id``, and
90+
``dest_id``. These define the ACL mutation to be done on each object. An ACL
91+
mutation makes it possible to convert a source userid to a destination
92+
userid.
9093

9194
* ``type`` (id | email | uri)
9295

0 commit comments

Comments
 (0)