From: Zac Dover Date: Thu, 12 Jun 2025 11:28:57 +0000 (+1000) Subject: doc/radosgw: edit cloud-transition (1 of x) X-Git-Url: http://git.apps.os.sepia.ceph.com/?a=commitdiff_plain;h=d3cb4a8fbc0dacecc2a505884dc29c690fb1c628;p=ceph.git doc/radosgw: edit cloud-transition (1 of x) Edit the first hundred lines of doc/radosgw/cloud-transition.rst. Signed-off-by: Zac Dover (cherry picked from commit 9ad5a65fe6cf883cf34bceae0314f55bcf599c96) --- diff --git a/doc/radosgw/cloud-transition.rst b/doc/radosgw/cloud-transition.rst index 2e963cf889529..4012231bbe8fe 100644 --- a/doc/radosgw/cloud-transition.rst +++ b/doc/radosgw/cloud-transition.rst @@ -2,17 +2,18 @@ Cloud Transition ================ -This feature enables transitioning S3 objects to a remote cloud service as part -of `object lifecycle `_ +This feature makes it possible to transition S3 objects to a remote cloud +service as part of the `object lifecycle +`_ via :ref:`storage_classes`. The transition is unidirectional: data cannot be -transitioned back from the remote zone. The goal of this feature is to enable -data transition to multiple cloud providers. The currently supported cloud -providers are those that are compatible with AWS (S3). +transitioned back from the remote zone. The purpose of this feature is to +enable data transition to multiple cloud providers. Cloud providers compatible +with AWS (S3) are supported. -A special storage class of tier type ``cloud-s3`` or ``cloud-s3-glacier`` -is used to configure the remote cloud S3 object store service to which -data is transitioned. These are defined in terms of zonegroup placement -targets and, unlike regular storage classes, do not need a data pool. +We use a special storage class of tier type ``cloud-s3`` or +``cloud-s3-glacier`` to configure the remote cloud S3 object store service to +which data is transitioned. These classes are defined in terms of zonegroup +placement targets and, unlike regular storage classes, do not need a data pool. User credentials for the remote cloud object store service must be configured. Note that source ACLs will not be preserved. It is possible @@ -75,7 +76,8 @@ Cloud Transition Specific Configurables * ``host_style`` (path | virtual) - Type of host style to be used when accessing the remote cloud S3 service (default: ``path``). + Type of host style to be used when accessing the remote cloud S3 service + (default: ``path``). * ``acls`` (array) @@ -83,9 +85,10 @@ Cloud Transition Specific Configurables * ``acl_mapping`` (container) - Each ``acl_mapping`` structure contains ``type``, ``source_id``, and ``dest_id``. These - define the ACL mutation to be done on each object. An ACL mutation makes it possible to - convert a source userid to a destination userid. + Each ``acl_mapping`` structure contains ``type``, ``source_id``, and + ``dest_id``. These define the ACL mutation to be done on each object. An ACL + mutation makes it possible to convert a source userid to a destination + userid. * ``type`` (id | email | uri)