Update docs after dropping Ceph backend support.

Remove Ceph references from supported cloud lists and location management guidance, and generalize bucket-match wording to S3-compatible endpoints.

Author: benzekrimaha

docs/docsource/introduction/architecture/xdm_ui.rst

@@ -16,7 +16,6 @@ storage endpoints.
    -  Scality RING with SOFS
    -  Scality RING with S3 Connector
    -  AWS S3
-   -  Ceph RADOS Gateway
    -  Google Cloud Storage (GCS)
    -  NFS 
    -  Microsoft Azure Blob

docs/docsource/introduction/supported_clouds+services.rst

@@ -23,7 +23,6 @@ sources:
 *  Amazon Simple Storage Service
 *  Scality RING with S3 Connector
 *  Wasabi Hot Cloud Storage
-*  Ceph RADOS Gateway
 
 In addition to its compatibility with S3- and Azure Blob-compatible cloud
 frontends, |product| can ingest data and metadata from servers using the following
@@ -72,7 +71,6 @@ private and public clouds:
 *  Amazon-S3-based private clouds:
 
    * Scality RING S3 Connector
-   * Red Hat Ceph RADOS Gateway
 
 *  Other public clouds:
 

docs/docsource/operation/location_management/add_a_storage_location.rst

@@ -57,7 +57,6 @@ To add a storage location:
       You can choose:
 
       * Amazon S3
-      * Ceph RADOS Gateway
       * DigitalOcean Spaces
       * Google Cloud Storage
       * Microsoft Azure Blob Storage
@@ -130,9 +129,6 @@ system.
    +===============+==========+========+============+=========+
    | Amazon S3     | \-       | \-     | Yes        | \-      |
    +---------------+----------+--------+------------+---------+
-   | Ceph RADOS    | Yes      | \-     | \-         | \-      |
-   | Gateway       |          |        |            |         |
-   +---------------+----------+--------+------------+---------+
    | DigitalOcean  | Yes      | Yes    | \-         | \-      |
    | Spaces [#f2]_ |          |        |            |         |
    +---------------+----------+--------+------------+---------+
@@ -164,14 +160,10 @@ to name endpoints. Services for which |product| requests endpoint names may have
 additional naming requirements. For these requirements, review your cloud
 storage service provider's documentation.
 
-For Ceph RADOS Gateway endpoints, you can nominate a secure port. 
-If you do not nominate a secure port, the default is port 80. 
-Whichever port you assign, make sure it is accessible to |product| (firewall open, etc.).
-
 Bucket Match
 ~~~~~~~~~~~~
 
-|product| provides a "Bucket Match" option for Ceph RADOS Gateway. If this
+|product| provides a "Bucket Match" option for S3-compatible endpoints. If this
 option is left unchecked, |product| prepends a bucket identifier to every object
 in the target backend's namespace. This enables a "bucket of buckets"
 architecture in which the target backend sees and manages only one large bucket

docs/docsource/operation/location_management/index.rst

@@ -39,10 +39,6 @@ notice.
 
    https://wasabi.com/s3-compatible-cloud-storage/
 
--  Red Hat Ceph RADOS Gateway
-
-   https://access.redhat.com/documentation/en-us/red_hat_ceph_storage
-
 See :version-ref:`Zenko Installation
 <https://documentation.scality.com/Zenko/{version}/installation/index.html>` for
 advice on sizing, cluster configuration, and other preparations.
@@ -55,7 +51,7 @@ private cloud storage solution.
 
 Except as noted, you can integrate to S3 Connector exactly as you would
 integrate to any of the other S3-based cloud services, such as AWS, DigitalOcean
-Spaces, Wasabi Hot Cloud, or Ceph RADOS Gateway. See the S3 Connector and RING
+Spaces, or Wasabi Hot Cloud. See the S3 Connector and RING
 documentation at https://documentation.scality.com/ for more details on
 deploying and configuring S3 Connector with the RING.