refactor(docs): replace "Scylla" with "ScyllaDB" (#4775)

* docs: Replace 'Scylla' with 'ScyllaDB' in documentation

Replace 'Scylla' with 'ScyllaDB' in all .rst files in docs/source/ directory
following context-aware rules:

Replaced:
- Product names (Scylla Manager, Scylla node, Scylla cluster, etc.)
- Narrative text describing the database product
- Link text descriptions

Preserved:
- Package names (scylla-manager, scylla-manager-agent)
- File paths (/etc/scylla, /var/lib/scylla)
- Configuration files (scylla.yaml)
- Environment variables (SCYLLA_MANAGER_CLUSTER)
- Command flags (--no-scylla-setup)
- Table column headers in command output
- Code blocks
- URLs
- SSTable filenames (big-Scylla.db)

Total: 166 replacements across 28 files

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* docs: Fix RST title underlines after Scylla to ScyllaDB replacement

Co-authored-by: Michal-Leszczynski <74614433+Michal-Leszczynski@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Michal-Leszczynski <74614433+Michal-Leszczynski@users.noreply.github.com>

Author: 3 people

docs/source/_ext/__pycache__/scylladb_dynamic_substitutions.cpython-312.pyc

@@ -4,18 +4,18 @@ Add a Cluster
 
 **Prerequisites**
 
-* Scylla Manager Agent is up and running on all Scylla nodes.
+* ScyllaDB Manager Agent is up and running on all ScyllaDB nodes.
 * All the Agents have the same :ref:`authentication token <configure-auth-token>` configured.
-* Traffic on the following ports is unblocked from the Scylla Manager Server to all the Scylla nodes.
+* Traffic on the following ports is unblocked from the ScyllaDB Manager Server to all the ScyllaDB nodes.
 
-  * ``10001`` - Scylla Manager Agent REST API (HTTPS)
+  * ``10001`` - ScyllaDB Manager Agent REST API (HTTPS)
   * CQL port (typically ``9042``) - required for CQL health check status reports
 
 .. _add-cluster:
 
 **Procedure**
 
-#. From the Scylla Manager Server, provide the IP address of one of the nodes, the generated auth token, and a custom name.
+#. From the ScyllaDB Manager Server, provide the IP address of one of the nodes, the generated auth token, and a custom name.
 
    Example (IPv4):
 
@@ -48,7 +48,7 @@ Add a Cluster
    * ``--host`` is hostname or IP of one of the cluster nodes. You can use an IPv6 or an IPv4 address.
    * ``--name`` is an alias you can give to your cluster.
      Using an alias means you do not need to use the ID of the cluster in all other operations.
-     This name must be used when connecting the managed cluster to Scylla Monitor, but does not have to be the same name you used in scylla.yaml.
+     This name must be used when connecting the managed cluster to ScyllaDB Monitor, but does not have to be the same name you used in scylla.yaml.
    * ``--auth-token`` is the :ref:`authentication token <configure-auth-token>` you generated.
 
    Each cluster has a unique ID (UUID), you will see it printed to stdout in ``sctool cluster add`` output when the cluster is added.
@@ -60,7 +60,7 @@ Add a Cluster
    This can be canceled using ``--without-repair``.
    To use a different repair schedule, see :ref:`Schedule a Repair <schedule-a-repair>`.
 
-   Scylla manager requires CQL credentials to the cluster with ``--username`` and ``--password`` flags.
+   ScyllaDB manager requires CQL credentials to the cluster with ``--username`` and ``--password`` flags.
    This enables :ref:`CQL query based health check <cql-query-health-check>` compared to :ref:`credentials agnostic health check <credentials-agnostic-health-check>` if you do not specify the credentials.
    This also enables CQL schema backup in text format, which isn't performed if credentials aren't provided.  Restore uses the backed up schema as part of the restore process.
    For security reasons the CQL user should NOT have access to read your data.
@@ -88,7 +88,7 @@ Add a Cluster
 
    .. note:: If you want to change the schedule for the repair, use the :ref:`repair update sctool <reschedule-a-repair>` command.
 
-#. Verify Scylla Manager can communicate with all the Agents, and the the cluster status is OK by running the ``sctool status`` command.
+#. Verify ScyllaDB Manager can communicate with all the Agents, and the the cluster status is OK by running the ``sctool status`` command.
 
    .. code-block:: none
 

docs/source/add-a-cluster.rst

@@ -83,7 +83,7 @@ Backup location
 ===============
 
 You need to create a backup location for example an S3 bucket.
-We recommend creating it in the same region as Scylla nodes to minimize cross region data transfer costs.
+We recommend creating it in the same region as ScyllaDB nodes to minimize cross region data transfer costs.
 In multi-dc deployments you should create a bucket per datacenter, each located in the datacenter's region.
 
 Details may differ depending on the storage engine, please consult:
@@ -98,10 +98,10 @@ Removing backups
 
 Backups may require a lot of storage space. They are purged according to the retention defined on the backup task.
 
-`Sctool` can be used to remove snapshots of clusters that are no longer managed by Scylla Manager.
-The removal process is performed through the Scylla Manager Agent installed on Scylla nodes.
+`Sctool` can be used to remove snapshots of clusters that are no longer managed by ScyllaDB Manager.
+The removal process is performed through the ScyllaDB Manager Agent installed on ScyllaDB nodes.
 
-However, it's recommended to delete the snapshots from the storage before removing the cluster from Scylla Manager.
+However, it's recommended to delete the snapshots from the storage before removing the cluster from ScyllaDB Manager.
 Otherwise, you will need to add the cluster again, list the snapshots in the given location, and remove them using the new cluster as the coordinator.
 Another option is to purge them manually. If you want to remove the snapshots manually, please refer to the :doc:`backup specification <specification>`
 and remove them accordingly.

docs/source/backup/index.rst

@@ -9,14 +9,14 @@ Setup Amazon S3
 Create a bucket
 ===============
 
-Go to `Amazon S3 <https://aws.amazon.com/s3/>`_ and create a new bucket in a region where Scylla nodes are.
+Go to `Amazon S3 <https://aws.amazon.com/s3/>`_ and create a new bucket in a region where ScyllaDB nodes are.
 If your cluster is deployed in multiple regions create a bucket per region.
 You may decide to backup only a single datacenter to save on costs, in that case create only one bucket in a region you want to backup.
 
 Grant access
 ============
 
-This procedure is required so that Scylla Manager can access your bucket.
+This procedure is required so that ScyllaDB Manager can access your bucket.
 
 Choose how you want to configure access to the bucket.
 You can use an IAM role (recommended) or you can add your credentials to the agent configuration file.
@@ -69,7 +69,7 @@ Sample IAM policy for *scylla-manager-backup* bucket:
 Config file
 -----------
 
-Note that this procedure needs to be repeated for each Scylla node.
+Note that this procedure needs to be repeated for each ScyllaDB node.
 
 **Procedure**
 
@@ -86,7 +86,7 @@ Edit the ``/etc/scylla-manager-agent/scylla-manager-agent.yaml``
 
       scylla-manager-agent check-location --location s3:<your S3 bucket name>
 
-#. Restart Scylla Manager Agent service.
+#. Restart ScyllaDB Manager Agent service.
 
    .. code-block:: none
 
@@ -97,12 +97,12 @@ Additional features
 
 You can enable additional Amazon S3 features such as **server side encryption** or **transfer acceleration**.
 Those need to be enabled on per Agent basis in the configuration file.
-Check out the ``s3`` section in :doc:`Scylla Manager Agent Config file <../config/scylla-manager-agent-config>`.
+Check out the ``s3`` section in :doc:`ScyllaDB Manager Agent Config file <../config/scylla-manager-agent-config>`.
 
 Troubleshoot connectivity
 =========================
 
-To troubleshoot Scylla node to bucket connectivity issues you can run:
+To troubleshoot ScyllaDB node to bucket connectivity issues you can run:
 
 .. code-block:: none
 

docs/source/backup/setup-amazon-s3.rst

@@ -12,17 +12,17 @@ Create a container
 ==================
 
 Go to `Azure Portal <https://portal.azure.com/>`_ and create a new container within your storage account.
-This container should be only used for storing Scylla Manager backups.
+This container should be only used for storing ScyllaDB Manager backups.
 If your cluster is deployed in multiple regions create a storage account and container per region.
 You may decide to backup only a single datacenter to save on costs, in that case create only one storage account and container in a region you want to backup.
 
 Grant access
 ============
 
-This procedure is required so that Scylla Manager can access your containers.
+This procedure is required so that ScyllaDB Manager can access your containers.
 
 Choose how you want to configure access to the container.
-You can use an `IAM role`_ (recommended) or you can add storage account credentials (account/key) to the Scylla Manager Agent configuration file.
+You can use an `IAM role`_ (recommended) or you can add storage account credentials (account/key) to the ScyllaDB Manager Agent configuration file.
 The latter method is not recommended because you are placing the security information directly on each node, which is much less secure than the IAM role method. In addition, if you need to change the key, you will have to replace it on every node.
 
 IAM role
@@ -75,7 +75,7 @@ You can use permissions from the provided sample but make sure to set proper val
 Config file
 -----------
 
-Note that this procedure needs to be repeated for each Scylla node.
+Note that this procedure needs to be repeated for each ScyllaDB node.
 
 **Procedure**
 
@@ -91,7 +91,7 @@ Edit the ``/etc/scylla-manager-agent/scylla-manager-agent.yaml``
 
       scylla-manager-agent check-location --location azure:<blob storage container name>
 
-#. Restart Scylla Manager Agent service.
+#. Restart ScyllaDB Manager Agent service.
 
    .. code-block:: none
 
@@ -100,7 +100,7 @@ Edit the ``/etc/scylla-manager-agent/scylla-manager-agent.yaml``
 Troubleshoot connectivity
 =========================
 
-To troubleshoot Scylla node to bucket connectivity issues you can run:
+To troubleshoot ScyllaDB node to bucket connectivity issues you can run:
 
 .. code-block:: none
 

docs/source/backup/setup-azure-blobstorage.rst

@@ -9,14 +9,14 @@ Setup Google Cloud Storage
 Create a bucket
 ===============
 
-Go to `Google Cloud Storage <https://cloud.google.com/storage>`_ and create a new bucket in a region where Scylla nodes are.
+Go to `Google Cloud Storage <https://cloud.google.com/storage>`_ and create a new bucket in a region where ScyllaDB nodes are.
 If your cluster is deployed in multiple regions create a bucket per region.
 You may decide to backup only a single datacenter to save on costs, in that case create only one bucket in a region you want to backup.
 
 Grant access
 ============
 
-This procedure is required so that Scylla Manager can access your bucket.
+This procedure is required so that ScyllaDB Manager can access your bucket.
 
 Choose how you want to configure access to the bucket.
 If your application runs inside a Google Cloud environment we recommend using automatic Service account authentication.
@@ -28,14 +28,14 @@ Automatic service account authorization
 
 **Procedure**
 
-#. Collect list of `service accounts <https://cloud.google.com/compute/docs/access/service-accounts>`_ used by **each** of the Scylla nodes.
+#. Collect list of `service accounts <https://cloud.google.com/compute/docs/access/service-accounts>`_ used by **each** of the ScyllaDB nodes.
 #. Make sure that each of service account has read/write `access scope <https://cloud.google.com/compute/docs/access/service-accounts#accesscopesiam>`_ to Cloud Storage.
 #. For each service account from the list, add `Storage Object Admin role <https://cloud.google.com/storage/docs/access-control/iam-roles>`_ in bucket permissions settings.
 
 Service account file
 --------------------
 
-Note that this procedure needs to be repeated for each Scylla node.
+Note that this procedure needs to be repeated for each ScyllaDB node.
 
 **Prerequisites**
 
@@ -44,7 +44,7 @@ Use `this instruction <https://cloud.google.com/docs/authentication/production#m
 **Procedure**
 
 #. Upload service account file to ``/etc/scylla-manager-agent/gcs-service-account.json``.
-   If you want to use different path change service_account_file parameter in ``gcs`` section in :doc:`Scylla Manager Agent Config file <../config/scylla-manager-agent-config>`.
+   If you want to use different path change service_account_file parameter in ``gcs`` section in :doc:`ScyllaDB Manager Agent Config file <../config/scylla-manager-agent-config>`.
 #. Validate that the manager has access to the backup location.
    If there is no response, the bucket is accessible. If not, you will see an error.
 

docs/source/backup/setup-gcs.rst

@@ -6,7 +6,7 @@ Setup S3 compatible storage
    :depth: 2
    :local:
 
-There are multiple S3 API compatible providers that can be used with Scylla Manager.
+There are multiple S3 API compatible providers that can be used with ScyllaDB Manager.
 Due to minor differences between them we require that exact provider is specified in the config file for full compatibility.
 The available providers are Alibaba, AWS, Ceph, DigitalOcean, IBMCOS, Minio, Wasabi, Dreamhost, Netease.
 
@@ -18,8 +18,8 @@ You need to create a bucket in your storage system of choice.
 Grant access
 ============
 
-This procedure is required so that Scylla Manager can access your bucket.
-You need to configure bucket access policy in your storage system and set credentials in the Scylla Manager Agent config file.
+This procedure is required so that ScyllaDB Manager can access your bucket.
+You need to configure bucket access policy in your storage system and set credentials in the ScyllaDB Manager Agent config file.
 
 Policy
 ------
@@ -60,7 +60,7 @@ Given `myminio` is an alias for your MinIO deployment.
 Config file
 -----------
 
-Note that this procedure needs to be repeated for each Scylla node.
+Note that this procedure needs to be repeated for each ScyllaDB node.
 
 **Procedure**
 
@@ -77,7 +77,7 @@ Edit the ``/etc/scylla-manager-agent/scylla-manager-agent.yaml``
 
       scylla-manager-agent check-location --location s3:<your S3 bucket name>
 
-#. Restart Scylla Manager Agent service.
+#. Restart ScyllaDB Manager Agent service.
 
    .. code-block:: none
 

docs/source/backup/setup-s3-compatible-storage.rst

@@ -9,8 +9,8 @@ Specification
 Directory Layout
 ----------------
 
-The Scylla Manager backup requires a backup location string that specifies the storage provider and name of a bucket (using Amazon S3 naming) ex. ``s3:<your S3 bucket name>``.
-In that bucket Scylla Manager creates a ``backup`` directory where all the backup data and metadata are stored.
+The ScyllaDB Manager backup requires a backup location string that specifies the storage provider and name of a bucket (using Amazon S3 naming) ex. ``s3:<your S3 bucket name>``.
+In that bucket ScyllaDB Manager creates a ``backup`` directory where all the backup data and metadata are stored.
 
 There are three subdirectories:
 
@@ -253,7 +253,7 @@ while ``mc-5-big-Data.db.sm_20210809095541UTC`` will be used when restoring ``sm
 Manifest File
 -------------
 
-Scylla Manager Manifest files are gzipped JSON files.
+ScyllaDB Manager Manifest files are gzipped JSON files.
 Each node has it's own manifest file.
 If a cluster has three nodes a backup would contain three manifest files with the same name but under different directories.
 Please find below the contents of the manifest file of the node shown in the sst section.
@@ -324,7 +324,7 @@ Please find below the contents of the manifest file of the node shown in the sst
 The manifest contains the following information.
 
 * version          - the version of the manifest
-* cluster_name     - name of the cluster as registered in Scylla Manager
+* cluster_name     - name of the cluster as registered in ScyllaDB Manager
 * ip               - public IP address of the node
 * index            - list of tables, each table holds a list of file names
 * size             - total size of files in index

docs/source/backup/specification.rst

@@ -1,4 +1,4 @@
 
-* Healthcheck - which checks the Scylla CQL, repeating every 15 seconds.
-* Healthcheck Alternator - which checks the Scylla Alternator API, repeating every 15 seconds.
-* Healthcheck REST - which checks the Scylla REST API, repeating every minute.
+* Healthcheck - which checks the ScyllaDB CQL, repeating every 15 seconds.
+* Healthcheck Alternator - which checks the ScyllaDB Alternator API, repeating every 15 seconds.
+* Healthcheck REST - which checks the ScyllaDB REST API, repeating every minute.

docs/source/common/health-check-tasks.rst

@@ -9,4 +9,4 @@ Configuration Files
    scylla-manager-config
    scylla-manager-agent-config
 
-This page is where you will find information on Scylla Manager and Scylla Manager Agent configuration files.
+This page is where you will find information on ScyllaDB Manager and ScyllaDB Manager Agent configuration files.