From 1621bd10b1c9cad414ce78687b41a856f1b0ea67 Mon Sep 17 00:00:00 2001 From: jcirino Date: Mon, 18 Nov 2024 12:47:16 +0100 Subject: [PATCH] docs(gen): harmonization of local and block storage casings --- compute/gpu/how-to/create-manage-gpu-instance.mdx | 2 +- compute/gpu/how-to/use-gpu-with-docker.mdx | 6 +++--- .../how-to/use-scratch-storage-h100-instances.mdx | 2 +- compute/gpu/quickstart.mdx | 2 +- compute/instances/api-cli/migrating-instances.mdx | 6 +++--- compute/instances/concepts.mdx | 2 +- compute/instances/how-to/create-a-snapshot.mdx | 8 +++----- compute/instances/how-to/create-an-instance.mdx | 4 +--- compute/instances/how-to/use-standby-mode.mdx | 2 +- .../reference-content/choosing-instance-type.mdx | 6 +++--- .../reference-content/identify-devices.mdx | 14 +++++++------- containers/kubernetes/concepts.mdx | 8 ++++---- .../understanding-differences-kapsule-kosmos.mdx | 2 +- faq/billing.mdx | 12 ++++++------ faq/blockstorage.mdx | 14 ++++++-------- faq/elastic-metal.mdx | 2 +- faq/instances.mdx | 6 +++--- faq/kubernetes.mdx | 4 ++-- faq/serverless-containers.mdx | 4 ++-- faq/serverless-functions.mdx | 2 +- .../additional-content/organization-quotas.mdx | 4 ++-- managed-databases/mongodb/concepts.mdx | 8 ++++++-- ...import-data-to-managed-postgresql-databases.mdx | 4 ++-- .../postgresql-and-mysql/concepts.mdx | 12 ++++++------ .../how-to/change-volume-type.mdx | 10 ++++------ .../how-to/clone-a-database-instance.mdx | 10 ++++------ .../how-to/create-a-database.mdx | 10 ++++------ .../how-to/enable-autobackup.mdx | 6 ++---- .../how-to/manage-manual-backups.mdx | 6 ++---- .../how-to/upgrade-a-database.mdx | 8 +++----- .../postgresql-and-mysql/quickstart.mdx | 6 +++--- .../import-data-to-serverless-sql-databases.mdx | 4 ++-- storage/block/api-cli/managing-a-volume.mdx | 2 +- storage/block/quickstart.mdx | 2 +- .../differences-between-5kiops-volumes.mdx | 3 +-- tutorials/configure-failover-proxmox/index.mdx | 4 ++-- tutorials/deploy-nextcloud-s3/index.mdx | 2 +- tutorials/glusterfs/index.mdx | 2 +- 38 files changed, 98 insertions(+), 113 deletions(-) diff --git a/compute/gpu/how-to/create-manage-gpu-instance.mdx b/compute/gpu/how-to/create-manage-gpu-instance.mdx index f5191eb217..0cc76a226c 100644 --- a/compute/gpu/how-to/create-manage-gpu-instance.mdx +++ b/compute/gpu/how-to/create-manage-gpu-instance.mdx @@ -35,7 +35,7 @@ When you have completed your calculations using the GPU Instance, [deletion can - **Availability Zone**: Choose the geographical region, represented by the Availability Zone, where your Instance will be deployed. - **Instance Type (GPU)**: Select the desired GPU Instance type, considering factors such as processing power, memory, storage options, and bandwidth. Refer to our guide on [choosing the right GPU Instance type](/compute/gpu/reference-content/choosing-gpu-instance-type/) for more information. - **Image**: Pick an operating system image suitable for your GPU Instance. For example, select **Ubuntu Jammy GPU OS 12**, which comes with preinstalled NVIDIA drivers and an NVIDIA Docker environment. You have the flexibility to customize your working environment using Docker with our provided Docker images or your own containers. - - **Volumes**: Optionally, add storage volumes for your Instance. You can adjust settings such as block and local storage volumes according to your requirements. + - **Volumes**: Optionally, add storage volumes for your Instance. You can adjust settings such as Block and Local Storage volumes according to your requirements. * The recommended minimum volume size for GPU OS images is 125 GB. * If your GPU Instance supports scratch storage, the scratch volume displays but can not be edited. [Learn more about scratch storage.](/compute/gpu/how-to/use-scratch-storage-h100-instances/) diff --git a/compute/gpu/how-to/use-gpu-with-docker.mdx b/compute/gpu/how-to/use-gpu-with-docker.mdx index f3a971f9bd..d41dbfd3aa 100644 --- a/compute/gpu/how-to/use-gpu-with-docker.mdx +++ b/compute/gpu/how-to/use-gpu-with-docker.mdx @@ -47,7 +47,7 @@ We recommend that you map volumes from your GPU Instance to your Docker containe ### How to map local volumes -You can map directories from your GPU Instance's local storage to your Docker container, using the `-v :` flag. See the example command below: +You can map directories from your GPU Instance's Local Storage to your Docker container, using the `-v :` flag. See the example command below: ``` docker run -it --rm -v /root/mydata/:/workspace nvidia/cuda:11.2.1-runtime-ubuntu20.04 @@ -101,7 +101,7 @@ Below is a list of the most common commands you use when dealing with Docker con | **docker push** | `docker push ` | This command is used to push a local image to a remote repository. | | **docker images** | `docker images` | This command is used to list all available Docker images on the local system. | | **docker rm** | `docker rm ` | This command is used to remove a stopped container from the local system. | -| **docker rmi** | `docker rmi ` | This command is used to delete an image from the local storage. | +| **docker rmi** | `docker rmi ` | This command is used to delete an image from the Local Storage. | | docker version| `docker --version` | This command is used to display information about the currently installed version of Docker. | For more information regarding the `docker run` command, refer to the [official documentation](https://docs.docker.com/engine/reference/run/). @@ -129,7 +129,7 @@ docker run --runtime=nvidia -it --rm nvidia/cuda:11.2.1-runtime-ubuntu20.04 nvid ``` - You can omit this option if using the “Ubuntu Focal GPU OS11” Operating System image with your GPU Instance (as this option is set by default in the Docker configuration files) + You can omit this option if using the “Ubuntu Focal GPU OS11” Operating System image with your GPU Instance, as this option is set by default in the Docker configuration files. If your Instance has several GPUs, you can specify which GPU(s) to use with the container via the Docker CLI using either the `--gpus` option (starting with Docker 19.03) or using the environment variable `NVIDIA_VISIBLE_DEVICES`. diff --git a/compute/gpu/how-to/use-scratch-storage-h100-instances.mdx b/compute/gpu/how-to/use-scratch-storage-h100-instances.mdx index 900981351a..da60da2bf8 100644 --- a/compute/gpu/how-to/use-scratch-storage-h100-instances.mdx +++ b/compute/gpu/how-to/use-scratch-storage-h100-instances.mdx @@ -13,7 +13,7 @@ categories: - compute --- -Scaleway H100 and L40S GPU Instances are equipped with additional scratch storage. This form of temporary local storage operates differently from our regular local storage. +Scaleway H100 and L40S GPU Instances are equipped with additional scratch storage. This form of temporary Local Storage operates differently from our regular Local Storage. Scratch storage temporarily accommodates data during computational or data processing tasks. It is commonly used for storing intermediate results, processing input data, or holding output data before that data is moved to more permanent storage. diff --git a/compute/gpu/quickstart.mdx b/compute/gpu/quickstart.mdx index c4b1605537..08c41e1088 100644 --- a/compute/gpu/quickstart.mdx +++ b/compute/gpu/quickstart.mdx @@ -27,7 +27,7 @@ In addition to this, GPU Instances have all the features of our regular Instance - **Availability Zone**: Choose the geographical region, represented by the Availability Zone, where your Instance will be deployed. - **Instance Type (GPU)**: Select the desired GPU Instance type, considering factors such as processing power, memory, storage options, and bandwidth. Refer to our guide on [choosing the right GPU Instance type](/compute/gpu/reference-content/choosing-gpu-instance-type/) for more information. - **Image**: Pick an operating system image suitable for your GPU Instance. For example, select **Ubuntu Jammy GPU OS 12**, which comes with preinstalled Nvidia drivers and an Nvidia Docker environment. You have the flexibility to customize your working environment using Docker with our provided Docker images or your own containers. - - **Volumes**: Optionally, add storage volumes for your Instance. You can adjust settings such as block and local storage volumes according to your requirements. + - **Volumes**: Optionally, add storage volumes for your Instance. You can adjust settings such as Block and Local Storage volumes according to your requirements. * The recommended minimum volume size for GPU OS images is 125 GB. * If your GPU Instance supports scratch storage, the scratch volume displays but can not be edited. [Learn more about scratch storage.](/compute/gpu/how-to/use-scratch-storage-h100-instances/) diff --git a/compute/instances/api-cli/migrating-instances.mdx b/compute/instances/api-cli/migrating-instances.mdx index 10e72a7848..596d18a5a9 100644 --- a/compute/instances/api-cli/migrating-instances.mdx +++ b/compute/instances/api-cli/migrating-instances.mdx @@ -43,7 +43,7 @@ To do so, you need the Instance’s ID and a valid API key. You can retrieve a list of all available Instance types using the command `scw instance server-type list`. - Ensure that local storage constraints are respected. For example, downgrading from a larger Instance type to a smaller one may not be possible if the smaller Instance type cannot support the existing local storage. Check the Scaleway documentation for specific constraints. + Ensure that Local Storage constraints are respected. For example, downgrading from a larger Instance type to a smaller one may not be possible if the smaller Instance type cannot support the existing Local Storage. Check the Scaleway documentation for specific constraints. 3. Power on the Instance. @@ -82,7 +82,7 @@ To do so, you need the Instance’s ID and a valid API key. curl -X PATCH -H "X-Auth-Token: $SCW_SECRET_KEY" -H "Content-Type: application/json" -d '{"commercial_type" : ""}' "https://api.scaleway.com/instance/v1/zones/{zone}/servers/{server_id}" ``` - Local storage constraints must be respected. For example, downgrading a DEV1-L Instance with 80 GB of local SSD storage to a DEV1-S Instance is not possible because the DEV1-S offer only supports a maximum of 20 GB. However, if the DEV1-L Instance is only using block storage (`b_ssd`) without relying on local SSD storage, the downgrade can be performed without any issues. + Local Storage constraints must be respected. For example, downgrading a DEV1-L Instance with 80 GB of local SSD storage to a DEV1-S Instance is not possible because the DEV1-S offer only supports a maximum of 20 GB. However, if the DEV1-L Instance is only using Block Storage (`b_ssd`) without relying on local SSD storage, the downgrade can be performed without any issues. Output: @@ -135,4 +135,4 @@ To do so, you need the Instance’s ID and a valid API key. For more information on using the API, refer to the complete [API documentation](https://www.scaleway.com/en/developers/api/instance/). - + \ No newline at end of file diff --git a/compute/instances/concepts.mdx b/compute/instances/concepts.mdx index 7d3984030b..7c2a65dbe6 100644 --- a/compute/instances/concepts.mdx +++ b/compute/instances/concepts.mdx @@ -161,7 +161,7 @@ An image is composed of snapshots of volumes. Snapshots can only be restored to ## Standby mode -Standby mode is a way to stop an Instance temporarily. When you [put an Instance in standby mode](/compute/instances/how-to/use-standby-mode/), the server is halted, but the Instance remains allocated to your account, and all data remains on the local storage of the Instance. +Standby mode is a way to stop an Instance temporarily. When you [put an Instance in standby mode](/compute/instances/how-to/use-standby-mode/), the server is halted, but the Instance remains allocated to your account, and all data remains on the Local Storage of the Instance. ## Stateful security groups diff --git a/compute/instances/how-to/create-a-snapshot.mdx b/compute/instances/how-to/create-a-snapshot.mdx index dfe5a11114..7a31c290f3 100644 --- a/compute/instances/how-to/create-a-snapshot.mdx +++ b/compute/instances/how-to/create-a-snapshot.mdx @@ -17,8 +17,8 @@ The snapshot feature allows you to create an image of a specific [volume](/compu Several options are available to create snapshots from your Instance: -* **LSSD (Local storage):** This snapshot type can be created from local volumes. LSSD snapshots can be converted to local volumes only. -* **BSSD (Block storage):** This snapshot type can be created from block volumes. BSSD snapshots can be converted to block volumes only. +* **LSSD (Local Storage):** This snapshot type can be created from local volumes. LSSD snapshots can be converted to local volumes only. +* **BSSD (Block Storage):** This snapshot type can be created from block volumes. BSSD snapshots can be converted to block volumes only. The snapshot feature creates backups of specific volumes only. If you wish to create a backup image that is a complete backup of your Instance including **all** of its volumes, check out our documentation on [how to create an image](/compute/instances/how-to/create-a-backup/). @@ -66,6 +66,4 @@ Follow the instructions for [creating an Instance](/compute/instances/how-to/cre -You can see the snapshotted volume in the Instance's volumes at **step 4** of the creation wizard. - - +You can see the snapshotted volume in the Instance's volumes at **step 4** of the creation wizard. \ No newline at end of file diff --git a/compute/instances/how-to/create-an-instance.mdx b/compute/instances/how-to/create-an-instance.mdx index c402b2780d..b7f321b9c4 100644 --- a/compute/instances/how-to/create-an-instance.mdx +++ b/compute/instances/how-to/create-an-instance.mdx @@ -153,7 +153,7 @@ Select a tab below for instructions on how to create an Instance via either our | commercial-type | The commercial Instance type to create (string) | Any valid ID of a Scaleway commercial Instance type, e.g. `"GP1-S"`, `"PRO2-M"`. Use the [List Instance Types](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types) endpoint to get a list of all valid Instance types and their IDs. | | image | The image to install on the Instance, e.g. a particular OS (string) | Any valid Scaleway image ID, e.g. `"544f0add-626b-4e4f-8a96-79fa4414d99a"` which is the ID for the `Ubuntu 22.04 Jammy Jellyfish` image. Use the [Marketplace API](https://www.scaleway.com/en/developers/api/marketplace/) endpoint to find available images and their IDs. | | enable_ipv6 | Whether to enable IPv6 on the Instance (boolean) | `true` or `false` | - | volumes | An object that specifies the storage volumes to attach to the Instance. Must respect the volume constraints of the `commercial_type` (i.e. for each type of Instance, a minimum amount of storage is required, and there is also a maximum that cannot be exceeded. Some Instance types support only Block Storage (`b_ssd`), others also support local storage (`l_ssd`) ). These constraints are available at the [List Instance Types](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types) endpoint, via the `volume_constraints` parameter for each type listed in the response | A (dictionary) object with a minimum of one key (`"0"`) whose value is another object containing the parameters `"name"` (a name for the volume), `"size"` (the size for the volume, in bytes), and `"volume_type"` (`"l_ssd"` or `"b_ssd"`). Additional keys for additional volumes should increment by 1 each time (the second volume would have a key of `1`.) Further parameters are available, and it is possible to attach existing volumes rather than creating a new one, or create a volume from a snapshot. For full details see [here](https://www.scaleway.com/en/developers/api/instance/#path-volumes). | + | volumes | An object that specifies the storage volumes to attach to the Instance. Must respect the volume constraints of the `commercial_type` (i.e. for each type of Instance, a minimum amount of storage is required, and there is also a maximum that cannot be exceeded. Some Instance types support only Block Storage (`b_ssd`), others also support Local Storage (`l_ssd`) ). These constraints are available at the [List Instance Types](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types) endpoint, via the `volume_constraints` parameter for each type listed in the response | A (dictionary) object with a minimum of one key (`"0"`) whose value is another object containing the parameters `"name"` (a name for the volume), `"size"` (the size for the volume, in bytes), and `"volume_type"` (`"l_ssd"` or `"b_ssd"`). Additional keys for additional volumes should increment by 1 each time (the second volume would have a key of `1`.) Further parameters are available, and it is possible to attach existing volumes rather than creating a new one, or create a volume from a snapshot. For full details see [here](https://www.scaleway.com/en/developers/api/instance/#path-volumes). | 3. Use the following curl command, replacing the payload with the one you specified in step 2, to create your Instance. @@ -224,5 +224,3 @@ Select a tab below for instructions on how to create an Instance via either our - - diff --git a/compute/instances/how-to/use-standby-mode.mdx b/compute/instances/how-to/use-standby-mode.mdx index c00404621f..dd5bd219fa 100644 --- a/compute/instances/how-to/use-standby-mode.mdx +++ b/compute/instances/how-to/use-standby-mode.mdx @@ -13,7 +13,7 @@ categories: - compute --- -[Standby mode](/compute/instances/concepts/#stand-by-mode) temporarily stops an Instance. The Instance remains allocated to your account and all data remains on the local storage of the Instance. +[Standby mode](/compute/instances/concepts/#stand-by-mode) temporarily stops an Instance. The Instance remains allocated to your account and all data remains on the Local Storage of the Instance. diff --git a/compute/instances/reference-content/choosing-instance-type.mdx b/compute/instances/reference-content/choosing-instance-type.mdx index 168f275878..a219b2fdbc 100644 --- a/compute/instances/reference-content/choosing-instance-type.mdx +++ b/compute/instances/reference-content/choosing-instance-type.mdx @@ -40,9 +40,9 @@ Instances are virtual machines: multiple Instances can run on one "real" physica * **Bandwidth**: Bandwidth refers to the volume of data that can be sent to/from an Instance in a given amount of time (usually **p**er **s**econd). -* **Storage**: Different Instance types may support **Local** and/or **Block** storage: +* **Storage**: Different Instance types may support **Local** and/or **Block** Storage: - **Local** storage is an all-SSD-based storage solution, hosted on the local hypervisor. - - **Block** storage is more flexible, network-attached storage that can be plugged in and out of Instances like virtual hard drives. Some Instances only support block storage, and boot themselves from their block storage. + - **Block** storage is more flexible, network-attached storage that can be plugged in and out of Instances like virtual hard drives. Some Instances only support Block Storage, and boot themselves from their Block Storage. Depending on the Instance type, you can attach additional storage volumes and increase their size according to your needs. @@ -55,7 +55,7 @@ Use this table to help identify the right Instance range for your use case and c | **Instance range** | [Learning](/compute/instances/reference-content/learning/) | [Cost-Optimized](/compute/instances/reference-content/cost-optimized/) | [Production-Optimized](/compute/instances/reference-content/production-optimized/) | [Workload-Optimized](/compute/instances/reference-content/workload-optimized/) | |-----------------------|----------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Use cases** | Discovering the Scaleway ecosystem
Hosting personal projects | Scaling your development and testing environment
Hosting CI/CD runners and containerized worker nodes | Hosting production workloads and business-critical applications
Ensuring predictable CPU performance in the face of high traffic | Hosting high-demanding analysis, in-memory calculation, big-data processing, high-performance or cache databases
Designed for high-performance web-serving, video encoding, machine learning, batch processing, CI/CD | -| **Supported storage** | Resilient Block Storage or local storage | Resilient Block Storage or local storage, OR Resilient Block Storage only (depending on Instance type) | Resilient Block Storage | Resilient Block Storage | +| **Supported storage** | Resilient Block Storage or Local Storage | Resilient Block Storage or Local Storage, OR Resilient Block Storage only (depending on Instance type) | Resilient Block Storage | Resilient Block Storage | | **vCPU** | 1 core | From 1 to 32 cores | From 2 to 96 cores | From 2 to 64 cores | | **Shared/Dedicated** | Shared vCPU | Shared vCPU | Dedicated vCPU | Dedicated vCPU | | **RAM** | 1 GiB | From 2 GiB to 128 GiB | From 8 GiB to 384 GiB | From 4 GiB to 512 GiB | diff --git a/compute/instances/reference-content/identify-devices.mdx b/compute/instances/reference-content/identify-devices.mdx index 1dc810fa08..b0645984ea 100644 --- a/compute/instances/reference-content/identify-devices.mdx +++ b/compute/instances/reference-content/identify-devices.mdx @@ -19,11 +19,11 @@ On a Linux host, devices are named by the kernel in the order they are discovere This guide aims to provide tips to help you identify devices in a stable manner on a Linux host. -# Identifying Instance block storage volumes (b_ssd) +# Identifying Instance Block Storage volumes (b_ssd) -Instance block storage (`b_ssd`) volumes are connected to the Instance as SCSI disks. They will therefore appear as devices handled by the sd driver in the dev filesystem, i.e. as `/dev/sd{a,b,c...}` devices. +Instance Block Storage (`b_ssd`) volumes are connected to the Instance as SCSI disks. They will therefore appear as devices handled by the sd driver in the dev filesystem, i.e. as `/dev/sd{a,b,c...}` devices. -SCSI disks have multiple attributes, such as vendor and product/model. They also have a serial. Instance block storage (`b_ssd`) volumes have the vendor name `SCW`, the model/product name `b_ssd`, and a serial set to `volume-` where `` is the ID of the volume. +SCSI disks have multiple attributes, such as vendor and product/model. They also have a serial. Instance Block Storage (`b_ssd`) volumes have the vendor name `SCW`, the model/product name `b_ssd`, and a serial set to `volume-` where `` is the ID of the volume. The `lsblk` can be used to list SCSI devices and will show these attributes: @@ -98,11 +98,11 @@ For more details on writing `udev` rules, please see `man 7 udev`. # Identifying Block Storage volumes (SBS) -Block Storage devices are similar to Instance block storage devices. They are also connected to the Instance as SCSI devices and thus all explanations from the above section are also valid. +Block Storage devices are similar to Instance Block Storage devices. They are also connected to the Instance as SCSI devices and thus all explanations from the above section are also valid. The only difference is the SCSI model attribute. Instead of being fixed to the value `b_ssd`, its value depends on the class of the Block Storage volume. -Two Block Storage volumes classes currently exist: `bssd`, and `sbs`. Block Storage volumes migrated from Instance block storage (`b_ssd`) volumes have class `bssd`. +Two Block Storage volumes classes currently exist: `bssd`, and `sbs`. Block Storage volumes migrated from Instance Block Storage (`b_ssd`) volumes have class `bssd`. Block Storage volumes with class `bssd` have a SCSI model of `b_ssd`, so migrated volumes won't change characteristics. Otherwise, Block Storage volumes have a SCSI model equal to the volume's class. @@ -115,7 +115,7 @@ sda 0:0:0:0 disk SCW sbs v42 volume-7831d52c-758f-4a94-a074-39bfa14b sdb 0:0:1:0 disk SCW b_ssd v42 volume-03e206f6-2a3b-4223-bb56-3d7f1495903f ``` -Here, the first volume has been created through the Block Storage API with class `sbs`. The second volume is an Instance block storage (`b_ssd`) volume which has been migrated to Block Storage, and is now a Block Storage volume with class `bssd`. +Here, the first volume has been created through the Block Storage API with class `sbs`. The second volume is an Instance Block Storage (`b_ssd`) volume which has been migrated to Block Storage, and is now a Block Storage volume with class `bssd`. # Identifying VPC Private Network interfaces @@ -210,4 +210,4 @@ SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="02:00:00:*", ENV ``` This rule would start the systemd service `my-vpc-service@` when a new interface with name `` is added and has a MAC address matching the VPC Private Network prefix. -The systemd service can then execute complex operations (retrieving the server's `private_nics` informations, the VPC Private Network information through the VPC API, applying custom logic, etc.) +The systemd service can then execute complex operations (retrieving the server's `private_nics` informations, the VPC Private Network information through the VPC API, applying custom logic, etc.). \ No newline at end of file diff --git a/containers/kubernetes/concepts.mdx b/containers/kubernetes/concepts.mdx index 8177682148..11e2e22cd0 100644 --- a/containers/kubernetes/concepts.mdx +++ b/containers/kubernetes/concepts.mdx @@ -36,11 +36,11 @@ A single-zone cluster has its control plane operating in one zone, managing work ### Multi-AZ clusters -A Multi-AZ cluster features a single control plane in one zone but has nodes running across multiple zones. In case of a control plane outage or during cluster upgrades, workloads continue to run. However, the cluster and its workloads cannot be configured until the control plane is restored. Multi-zonal clusters offer a balance between availability and cost for stable workloads. During a zonal outage, workloads in that zone are disrupted, but they remain available in other zones. Multi AZ clusters have [technical limitations](https://www.scaleway.com/en/docs/containers/kubernetes/reference-content/multi-az-clusters/#limitations). For maintaining high availability, consider using a regional cluster. +A Multi-AZ cluster features a single control plane in one zone but has nodes running across multiple zones. In case of a control plane outage or during cluster upgrades, workloads continue to run. However, the cluster and its workloads cannot be configured until the control plane is restored. Multi-zonal clusters offer a balance between availability and cost for stable workloads. During a zonal outage, workloads in that zone are disrupted, but they remain available in other zones. Multi AZ clusters have [technical limitations](/containers/kubernetes/reference-content/multi-az-clusters/#limitations). For maintaining high availability, consider using a regional cluster. ### Regional clusters -A regional cluster has multiple replicas of the control plane distributed across multiple zones within a single region. Such cluster is only available with HA Dedicated Control Planes. Nodes can also be spread across multiple zones or restricted to a single zone, based on configuration. By default, Scaleway does not replicate each node pool across all zones of the control plane's region. You can customize this by specifying the zones for the cluster's nodes. Regional clusters are ideal for running production workloads due to their higher availability compared to zonal clusters. Regional clusters still have [technical limitations](https://www.scaleway.com/en/docs/containers/kubernetes/reference-content/multi-az-clusters/#limitations). +A regional cluster has multiple replicas of the control plane distributed across multiple zones within a single region. Such cluster is only available with HA Dedicated Control Planes. Nodes can also be spread across multiple zones or restricted to a single zone, based on configuration. By default, Scaleway does not replicate each node pool across all zones of the control plane's region. You can customize this by specifying the zones for the cluster's nodes. Regional clusters are ideal for running production workloads due to their higher availability compared to zonal clusters. Regional clusters still have [technical limitations](/containers/kubernetes/reference-content/multi-az-clusters/#limitations). ## Container Network Interface (CNI) @@ -147,7 +147,7 @@ The system volume is a read-only volume that stores essential files for the Kube Depending on the type of node selected, we provide one or two types of volume. - - **Local storage:** your system is stored locally on the hypervisor of your node. + - **Local Storage:** your system is stored locally on the hypervisor of your node. - **Block Storage:** your system is remotely stored on a centralized and resilient cluster. -As a general guideline, your system volume disk should have a capacity of at least 20 GB to ensure enough space to store the necessary system files and configurations. +As a general guideline, your system volume disk should have a capacity of at least 20 GB to ensure enough space to store the necessary system files and configurations. \ No newline at end of file diff --git a/containers/kubernetes/reference-content/understanding-differences-kapsule-kosmos.mdx b/containers/kubernetes/reference-content/understanding-differences-kapsule-kosmos.mdx index fdaca9294e..21c15f7567 100644 --- a/containers/kubernetes/reference-content/understanding-differences-kapsule-kosmos.mdx +++ b/containers/kubernetes/reference-content/understanding-differences-kapsule-kosmos.mdx @@ -49,7 +49,7 @@ Kosmos is Scaleway's **multi-cloud Kubernetes solution**, designed to operate ac | Container Network Interface plugins | Cilium or Calico | Kilo | | Auto healing | ✔️ | Scaleway Instances only | | Auto scaling | ✔️ | Scaleway Instances only | -| Container Storage Interface | ✔️ Persistent volumes (Block storage) on Scaleway Instances | Scaleway Instances only | +| Container Storage Interface | ✔️ Persistent volumes (Block Storage) on Scaleway Instances | Scaleway Instances only | | Dedicated Control Plane options | ✔️ | ✔️ | | Scaleway VPC | ✔️ Controlled isolation or full isolation | ✘ No integration | | Scaleway Cockpit | ✔️ | ✔️ | diff --git a/faq/billing.mdx b/faq/billing.mdx index 4ba83b5c11..7b33da1c31 100644 --- a/faq/billing.mdx +++ b/faq/billing.mdx @@ -23,7 +23,7 @@ Your monthly invoice is calculated at the end of each month and based on your ho For example: The Stardust1-s indicated at €0,0025 excl/hour can be split up as follows: - €0.00198/hour for the IP -- €0.0004/hour for the 10 GB of local storage +- €0.0004/hour for the 10 GB of Local Storage - €0.00012/hour for the instance For more information, refer to our dedicated [pricing page](https://www.scaleway.com/en/pricing/). @@ -41,10 +41,10 @@ Below is a detailed list of what is considered start and stop billing events for | Compute Instances | The moment you click the **Power On** button (when your Instance is already powered off). | The moment the Instance is **Powered Off**. | The Instance is not billed during its shutdown process. A hard reboot will keep the ongoing resource running. | | Elastic Metal servers | The moment the server is **created**. | The moment the server is **deleted**. | When an Elastic Metal server is powered off, the physical machine remains allocated to the user's account, meaning the resource continues to be billed. | | Apple silicon | The moment the Mac mini is **created**. | The moment the Mac mini is **deleted**. | Due to license constraints, the minimum lease for Apple silicon-as-a-Service is 24 hours. As a result, **a Mac mini can only be deleted after a minimum allocation period of 24 hours**. When a Mac mini is powered off, the physical machine remains allocated to the user's account, meaning the resource continues to be billed. | - | Flexible IP Address | The moment you reserve an IP. | The moment you cancel a reservation. | This class of IP is billed as long as you keep the reservation open. You will be billed whether you are effectively using the IP or not. | - | Dynamic IP Address | When a dynamic IP is associated with a running Compute Instance. | When a dynamic IP is detached from a running Compute Instance which has just been shut down | | - | Volume Storage | Once a volume has been created. | Once a volume has been deleted. | | - | Snapshot Storage | Once a snapshot has been created. | Once a snapshot has been deleted. | | + | Flexible IP address | The moment you reserve an IP. | The moment you cancel a reservation. | This class of IP is billed as long as you keep the reservation open. You will be billed whether you are effectively using the IP or not. | + | Dynamic IP address | When a dynamic IP is associated with a running Compute Instance. | When a dynamic IP is detached from a running Compute Instance which has just been shut down | | + | Volume storage | Once a volume has been created. | Once a volume has been deleted. | | + | Snapshot storage | Once a snapshot has been created. | Once a snapshot has been deleted. | | ## What does pro-rata billing for Dedibox and Web Hosting services mean? @@ -185,4 +185,4 @@ Refer to the [Understanding Savings Plan](/console/billing/additional-content/un ## I deleted my account, but still received an invoice. Why? -Scaleway invoices are calculated at the end of each month, so you may receive a final invoice the month after closing your account. That corresponds to your outstanding consumption for your final month of activity. +Scaleway invoices are calculated at the end of each month, so you may receive a final invoice the month after closing your account. That corresponds to your outstanding consumption for your final month of activity. \ No newline at end of file diff --git a/faq/blockstorage.mdx b/faq/blockstorage.mdx index dcdf85e00b..42873b5aa2 100644 --- a/faq/blockstorage.mdx +++ b/faq/blockstorage.mdx @@ -1,7 +1,7 @@ --- meta: title: Block Storage FAQ - description: Explore Scaleway Block Storage with our comprehensive FAQ covering performance, persistence, and more. Learn how Block Storage compares to local storage and its compatibility with Scaleway resources. + description: Explore Scaleway Block Storage with our comprehensive FAQ covering performance, persistence, and more. Learn how Block Storage compares to Local Storage and its compatibility with Scaleway resources. content: h1: Block Storage hero: assets/blockstorage.webp @@ -10,13 +10,13 @@ dates: category: storage --- -## Why should I use Block Storage instead of local storage? +## Why should I use Block Storage instead of Local Storage? -The size of local storage depends on your Instance type. With today's configurations, the maximum local storage available is 600 GB. +The size of Local Storage depends on your Instance type. With today's configurations, the maximum Local Storage available is 600 GB. -Block storage allows you to create bigger volumes and those volumes are persistent which means that they can live without being attached to an Instance. +Block Storage allows you to create bigger volumes and those volumes are persistent which means that they can live without being attached to an Instance. -| | **Block Storage** | **Local storage** | +| | **Block Storage** | **Local Storage** | |--------------------|:---------------------------------:|:--------------------------------------------------------------------------------------------------------------:| | **Availability** | High | HV dependant (needs physical intervention to retrieve storage and data if HV dies) | | **Redundancy** | High (replica 3) | Low (RAID 5 - 5 disks) | @@ -52,6 +52,4 @@ The Block Storage billing scheme is not the same as for Object Storage. You are ## What other Scaleway resources are compatible with Block Storage? -Block Storage volumes are compatible with [Scaleway Instances](/compute/instances/), [Managed Dabatase for PostgreSQL and MySQL](/managed-databases/postgresql-and-mysql/), and [Kubernetes](/containers/kubernetes/) Kapsule clusters. - - +Block Storage volumes are compatible with [Scaleway Instances](/compute/instances/), [Managed Dabatase for PostgreSQL and MySQL](/managed-databases/postgresql-and-mysql/), and [Kubernetes](/containers/kubernetes/) Kapsule clusters. \ No newline at end of file diff --git a/faq/elastic-metal.mdx b/faq/elastic-metal.mdx index 0ab9e0940a..8d5a09e317 100644 --- a/faq/elastic-metal.mdx +++ b/faq/elastic-metal.mdx @@ -32,7 +32,7 @@ We provide several ranges of Elastic Metal servers, each designed to meet the re * **Aluminium**: Fully dedicated Elastic Metal servers with native cloud integration, at the best price. * **Beryllium**: Powerful, balanced, and reliable servers for production-grade applications. - * **Lithium**: Designed with huge local storage to store, back up, and protect your data. + * **Lithium**: Designed with huge Local Storage to store, back up, and protect your data. * **Iridium**: Powerful dedicated servers designed to handle high-workload applications. ### Which regions and Availability Zones offer Elastic Metal servers? diff --git a/faq/instances.mdx b/faq/instances.mdx index 347de7991d..22f43cb575 100644 --- a/faq/instances.mdx +++ b/faq/instances.mdx @@ -172,7 +172,7 @@ You can change the storage type and flexible IP after the Instance creation, whi | Product | All regions* | PAR3 | |-------------------|------------------------|-------------------| -| Local storage | €0.000044 GB/hour | Not available | +| Local Storage | €0.000044 GB/hour | Not available | | Local snapshot | €0.000044 GB/hour | Not available | | Block Storage | €0.000118 GB/hour | €0.000177 GB/hour | | Block snapshot | €0.000044 GB/hour | €0.000066 GB/hour | @@ -203,10 +203,10 @@ Dedicated Resources give you a more stable experience for compute-demanding work ### Which options are available to power off my Instance? You can choose between four options when powering off your Instance: -* **Hard reboot**: Your Instance performs an electrical reboot and its data is kept on the local storage. We recommend always rebooting your Instance from the OS to avoid data corruption. +* **Hard reboot**: Your Instance performs an electrical reboot and its data is kept on the Local Storage. We recommend always rebooting your Instance from the OS to avoid data corruption. * **Power off**: All local volume data is transferred to a volume store, and your physical node is released back to the pool of available machines. The process duration depends on the amount of data archived. * **Terminate**: Your Instance and its volumes are permanently deleted, but the attached flexible IP is preserved. -* **Standby**: Your Instance is stopped, but its data remains on the local storage. The Instance is still allocated to your account and can be restarted anytime. +* **Standby**: Your Instance is stopped, but its data remains in the Local Storage. The Instance is still allocated to your account and can be restarted anytime. The **standby mode** is charged as a running Instance. To avoid being billed for an unused Instance, power it off and ensure no IPs or allocated storage are left in use. diff --git a/faq/kubernetes.mdx b/faq/kubernetes.mdx index e4588fb471..2c41a32add 100644 --- a/faq/kubernetes.mdx +++ b/faq/kubernetes.mdx @@ -83,8 +83,8 @@ For more information, refer to the Kubernetes Kapsule product documentation on [ To ensure sufficient space for storing default system files and configurations, we recommend a system volume disk capacity of at least 20 GB. While this amount is generally sufficient for small workloads, it is advisable to have a capacity of 100 GB to comfortably store images and system logs in many cases. If you run out of space on your immutable system volume disk, you can create another pool and use the **Advanced Options** button to set your desired system volume type and size. Depending on the type of node selected for your pool, one or two types of volume are available: -* **Local storage**: Your system is stored locally on the hypervisor of your node. -* **Block storage**: A remote storage option where your system is stored on a centralized and resilient cluster. +* **Local Storage**: Your system is stored locally on the hypervisor of your node. +* **Block Storage**: A remote storage option where your system is stored on a centralized and resilient cluster. ### What is the service 'kapsule-agent' running on my nodes? diff --git a/faq/serverless-containers.mdx b/faq/serverless-containers.mdx index 832d1c131a..94e283cc74 100644 --- a/faq/serverless-containers.mdx +++ b/faq/serverless-containers.mdx @@ -149,11 +149,11 @@ To add network restrictions on your resource, consult the [list of prefixes used ## How can I attach Block Storage to a Serverless Container? -Scaleway Serverless Containers do not currently support attaching block storage. These containers are designed to be +Scaleway Serverless Containers do not currently support attaching Block Storage. These containers are designed to be stateless, meaning they do not retain data between invocations. For persistent storage, we recommend using external solutions like Scaleway Object Storage. ## Why does my container have an instance running after deployment, even with min-scale 0? Currently, a new container instance will always start after each deployment, even if there is no traffic and the minimum -scale is set to 0. This behavior is not configurable at this time. +scale is set to 0. This behavior is not configurable at this time. \ No newline at end of file diff --git a/faq/serverless-functions.mdx b/faq/serverless-functions.mdx index 708e500fe9..715a90b8e8 100644 --- a/faq/serverless-functions.mdx +++ b/faq/serverless-functions.mdx @@ -176,7 +176,7 @@ To add network restrictions on your resource, consult the [list of prefixes used ## How can I attach Block Storage to a Serverless Function? -Scaleway Serverless Functions do not currently support attaching block storage. These functions are designed to be +Scaleway Serverless Functions do not currently support attaching Block Storage. These functions are designed to be stateless, meaning they do not retain data between invocations. For persistent storage, we recommend using external solutions like Scaleway Object Storage. diff --git a/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas.mdx b/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas.mdx index 77e32a0c9c..8f8027dc66 100644 --- a/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas.mdx +++ b/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas.mdx @@ -306,13 +306,13 @@ Local and Block Storage options are available with our compute offers. Regardless of the quotas displayed below, be aware that: - A virtual Instance can bear up to 16 volumes, including the mandatory local volume. Therefore, the maximum number of block volumes that can be attached to an Instance is 15. - The maximum size of a block volume is 10 TB. - - The maximum local storage for a DEV Instance depends on the DEV Instance type. For example, for the DEV1-XL the maximum local storage is 120 GB. + - The maximum Local Storage for a DEV Instance depends on the DEV Instance type. For example, for the DEV1-XL the maximum Local Storage is 120 GB. | | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card ) | Payment method and [identity validated](/console/account/how-to/verify-identity/) | |------------------------------------------------|:------------------------------------------------------------------------------------------------------------:|:--------------------------------------------------------------------------------------:| | Block Storage total size in GB | 500 | 5 000 | -| Local storage total size in GB | 1 000 | 5 000 | +| Local Storage total size in GB | 1 000 | 5 000 | | Snapshots | 99 999 | 99 999 | | Images | 99 999 | 99 999 | | Volumes | 200 | 5 000 | diff --git a/managed-databases/mongodb/concepts.mdx b/managed-databases/mongodb/concepts.mdx index b9b4a1bac3..b9ecdadca4 100644 --- a/managed-databases/mongodb/concepts.mdx +++ b/managed-databases/mongodb/concepts.mdx @@ -14,9 +14,13 @@ categories: Managed MongoDB® is currently in private beta. Click [here](https://www.scaleway.com/en/managed-mongodb/) to join the waiting list. +## Block Storage Legacy + +Block Storage Legacy is a volume type that is decoupled from your compute resources. You can increase your storage space to up to 10 TB without changing your node type. + ## Block Storage Low Latency -Block Storage Low Latency is a storage type similar to [Basic Block Storage](#basic-block-storage) that provides lower latency and high resiliency through 5k IOPS. You can increase your volume size to up to 10 TB. +Block Storage Low Latency is a storage type similar to [Block Storage Legacy](#block-storage-legacy) that provides lower latency and high resiliency through 5k IOPS. You can increase your volume size to up to 10 TB. Refer to the [Block Storage Low Latency documentation section](/storage/block/concepts/) to learn more about this volume type. @@ -66,4 +70,4 @@ An Instance of MongoDB® that runs as a single server and does not provide redun ## Replica-set 3-nodes -A group of 3 MongoDB® servers (1 primary and 2 standby nodes) that maintain the same data set. Replica sets provide redundancy and high availability and are the basis for all production deployments. If the main node fails for any reason, one of the remaining standby nodes is assigned and can take over requests, reducing downtime. +A group of 3 MongoDB® servers (1 primary and 2 standby nodes) that maintain the same data set. Replica sets provide redundancy and high availability and are the basis for all production deployments. If the main node fails for any reason, one of the remaining standby nodes is assigned and can take over requests, reducing downtime. \ No newline at end of file diff --git a/managed-databases/postgresql-and-mysql/api-cli/import-data-to-managed-postgresql-databases.mdx b/managed-databases/postgresql-and-mysql/api-cli/import-data-to-managed-postgresql-databases.mdx index b2bfada9da..ac9969a035 100644 --- a/managed-databases/postgresql-and-mysql/api-cli/import-data-to-managed-postgresql-databases.mdx +++ b/managed-databases/postgresql-and-mysql/api-cli/import-data-to-managed-postgresql-databases.mdx @@ -13,7 +13,7 @@ dates: Managed Databases for PostgreSQL offers near-complete PostgreSQL compatibility, and allows you to import your data from any PostgreSQL-compatible database. -The methods listed below are best suited for database sizes below 100 GB (approx.). Above this size, we recommend you use dedicated tooling to import your data, as your local storage size and bandwidth will create bottlenecks, and the operation may last several hours. +The methods listed below are best suited for database sizes below 100 GB (approx.). Above this size, we recommend you use dedicated tooling to import your data, as your Local Storage size and bandwidth will create bottlenecks, and the operation may last several hours. @@ -160,7 +160,7 @@ To avoid any statement timeout errors with Managed Database for PostgreSQL (e.g. 5. Select **Detect Changes with Xmin System Column** as **Update Method** (other methods are not supported). -4. Click **Set up source**. +6. Click **Set up source**. #### Adding your new Managed Database for PostgreSQL as a destination diff --git a/managed-databases/postgresql-and-mysql/concepts.mdx b/managed-databases/postgresql-and-mysql/concepts.mdx index aaca340391..b36b043a3c 100644 --- a/managed-databases/postgresql-and-mysql/concepts.mdx +++ b/managed-databases/postgresql-and-mysql/concepts.mdx @@ -23,13 +23,13 @@ Access control is handled directly at network-level by Load Balancers, making th Database Instances have settings that allow you to tune the behavior of their database engine to better fit your needs. Available settings depend on the database engine and its version. Each Database Instance setting entry has a default value that the user can override. The deletion of a setting entry restores the setting to the entry's default value. Some default values can be different from the engine's default, as their configuration is optimized to work at full potential with the Scaleway ecosystem. -## Basic Block Storage +## Block Storage Legacy -Basic Block Storage is a volume type that is decoupled from your compute resources. You can increase your storage space to up to 10 TB without changing your node type. +Block Storage Legacy is a volume type that is decoupled from your compute resources. You can increase your storage space to up to 10 TB without changing your node type. ## Block Storage Low Latency -Block Storage Low Latency is a storage type similar to [Basic Block Storage](#basic-block-storage) that provides lower latency and high resiliency through 5k IOPS. You can increase your volume size to up to 10 TB. +Block Storage Low Latency is a storage type similar to [Block Storage Legacy](#block-storage-legacy) that provides lower latency and high resiliency through 5k IOPS. You can increase your volume size to up to 10 TB. Refer to the [Block Storage Low Latency documentation section](/storage/block/concepts/) to learn more about this volume type. @@ -92,12 +92,12 @@ The HA standby node is linked to the main node, using synchronous replication. S HA standby nodes are not accessible to users unless the main node becomes unavailable and the standby takes over. If you wish to run queries on a read-only node, you can use [Read Replicas](/managed-databases/postgresql-and-mysql/how-to/create-read-replica/). -## Local storage +## Local Storage With this type, your storage is fixed and tied to your compute resource. - Local storage is only available with first-generation node types. + Local Storage is only available with first-generation node types. ## Logs @@ -122,7 +122,7 @@ A database type that uses the relational model, which means that it stores and p ## Volume type -This is the type of storage used on your Database Instances. Three types are available: [Local](#local-storage), [Basic Block](#basic-block-storage), and [Block Low Latency](#block-storage-low-latency). +This is the type of storage used on your Database Instances. Three types are available: [Local Storage](#local-storage), [Block Storage Legacy](#block-storage-legacy), and [Block Storage Low Latency](#block-storage-low-latency). Block Low Latency volumes are only available with new-generation node types and only in the PAR and AMS regions. diff --git a/managed-databases/postgresql-and-mysql/how-to/change-volume-type.mdx b/managed-databases/postgresql-and-mysql/how-to/change-volume-type.mdx index 778be44b1d..6f06d6fd42 100644 --- a/managed-databases/postgresql-and-mysql/how-to/change-volume-type.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/change-volume-type.mdx @@ -20,7 +20,7 @@ It is possible to change your [volume type](/managed-databases/postgresql-and-my - A Scaleway account logged into the [console](https://console.scaleway.com) - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [PostgreSQL or MySQL Database Instance](/managed-databases/postgresql-and-mysql/quickstart/) with local storage +- A [PostgreSQL or MySQL Database Instance](/managed-databases/postgresql-and-mysql/quickstart/) with Local Storage 1. Click **PostgreSQL and MySQL** under **Managed Databases** on the side menu. A list of your Database Instances displays. 2. Click the name of the Database Instance you want to edit. The database's Overview page displays. @@ -38,8 +38,6 @@ It is possible to change your [volume type](/managed-databases/postgresql-and-my - When switching from a local volume to a block volume, and if [Autobackup](/managed-databases/postgresql-and-mysql/how-to/enable-autobackup/) is enabled, be aware that the snapshot type will change. Local volumes use logical backups, whereas Block Storage employs snapshots. Both types are priced at €0.03 per GB per month, but their distinct backup methods affect storage space differently, influencing the final monthly cost based on your usage. - - Disk size cannot be reduced, so when switching from local to Block, the volume size remains the same by default. - - When switching from a block to a local volume, make sure to select a node with a local storage with size equal or greater than your current Block Storage. If you choose a Database Instance type with a local volume larger than your current block volume, you will be billed for the full capacity of the Database Instance. - - - + - Disk size cannot be reduced, so when switching from Local to Block, the volume size remains the same by default. + - When switching from a block to a local volume, make sure to select a node with a Local Storage with size equal or greater than your current Block Storage. If you choose a Database Instance type with a local volume larger than your current block volume, you will be billed for the full capacity of the Database Instance. + \ No newline at end of file diff --git a/managed-databases/postgresql-and-mysql/how-to/clone-a-database-instance.mdx b/managed-databases/postgresql-and-mysql/how-to/clone-a-database-instance.mdx index 9c389ebd42..c5bec0ebfd 100644 --- a/managed-databases/postgresql-and-mysql/how-to/clone-a-database-instance.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/clone-a-database-instance.mdx @@ -35,15 +35,13 @@ The clone feature allows you to create a new Database Instance from an existing 5. Enter a name for your database or leave the default name suggested by the Scaleway console. 6. Select a node type. You can keep the same node type, or upgrade to a bigger one. - If you have a new-generation Database Instance using a local volume node type and want to upgrade to an Instance that uses Block volumes node type, you must [change the volume type](/managed-databases/postgresql-and-mysql/how-to/change-volume-type/) to Block storage first.

+ If you have a new-generation Database Instance using a local volume node type and want to upgrade to an Instance that uses Block volumes node type, you must [change the volume type](/managed-databases/postgresql-and-mysql/how-to/change-volume-type/) to Block Storage first.

- Similarly, if you have a new-generation Database Instance using a [Low Latency Block volume](/managed-databases/postgresql-and-mysql/concepts/#block-storage-low-latency) and want to create a clone on a first-generation Instance, you must first change the volume type to [Basic Block Storage](/managed-databases/postgresql-and-mysql/concepts/#basic-block-storage). + Similarly, if you have a new-generation Database Instance using a [Low Latency Block volume](/managed-databases/postgresql-and-mysql/concepts/#block-storage-low-latency) and want to create a clone on a first-generation Instance, you must first change the volume type to [Block Storage Legacy](/managed-databases/postgresql-and-mysql/concepts/#block-storage-legacy). 7. Click **Clone Database Instance**. The source Database Instance remains available during the cloning process in **Backing up mode**. Some actions are not available during this time.

- The time it takes to clone a Database Instance with local storage depends on the size of the database. For Database Instances with Block Storage the cloning process is slightly faster. - - - + The time it takes to clone a Database Instance with Local Storage depends on the size of the database. For Database Instances with Block Storage the cloning process is slightly faster. + \ No newline at end of file diff --git a/managed-databases/postgresql-and-mysql/how-to/create-a-database.mdx b/managed-databases/postgresql-and-mysql/how-to/create-a-database.mdx index 4603f5536c..92efbde203 100644 --- a/managed-databases/postgresql-and-mysql/how-to/create-a-database.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/create-a-database.mdx @@ -48,13 +48,13 @@ Compared to traditional database management, which requires customers to provide - Select a node type. - Choose your storage type and capacity. Two types of storage are available: - - **Basic Block Storage** - With this type, your storage is decoupled from your compute resources. You can increase your storage space without changing your node type. You can define your storage capacity by entering the desired amount in the box. The volume can be increased up to 10 TB. + - **Block Storage Legacy** - With this type, your storage is decoupled from your compute resources. You can increase your storage space without changing your node type. You can define your storage capacity by entering the desired amount in the box. The volume can be increased up to 10 TB. - - **Block Storage Low Latency**: This storage type works like the [Basic Block Storage](#basic-block-storage), while providing lower latency and high resiliency through 5k IOPS. You can increase your volume to up to 10 TB. + - **Block Storage Low Latency**: This storage type works like the [Block Storage Legacy](/managed-databases/postgresql-and-mysql/concepts/#block-storage-legacy), while providing lower latency and high resiliency through 5k IOPS. You can increase your volume to up to 10 TB. - **Local SSD Storage** - Your storage is fixed and tied to your compute resource. - The local storage option is only available with the first generation node types. + The Local Storage option is only available with the first generation node types. - Select the snapshot configuration. You can either leave the default **Automatic** option to enable [autobackups](/managed-databases/postgresql-and-mysql/how-to/enable-autobackup/), or select [Manual snapshots](/managed-databases/postgresql-and-mysql/how-to/manage-snapshots/). - Add a name and set a password for your user. @@ -68,6 +68,4 @@ Compared to traditional database management, which requires customers to provide - one number - Enter a name for your Instance. -4. Click **Create Database Instance** to confirm your choices and launch creation. - - +4. Click **Create Database Instance** to confirm your choices and launch creation. \ No newline at end of file diff --git a/managed-databases/postgresql-and-mysql/how-to/enable-autobackup.mdx b/managed-databases/postgresql-and-mysql/how-to/enable-autobackup.mdx index d3a6776602..fca1a1706d 100644 --- a/managed-databases/postgresql-and-mysql/how-to/enable-autobackup.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/enable-autobackup.mdx @@ -18,7 +18,7 @@ With the autobackup feature, the creation and management of your Database Instan Two types of autobackups are available at Scaleway: [backups](/managed-databases/postgresql-and-mysql/concepts/#database-backup) and [snapshots](/managed-databases/postgresql-and-mysql/concepts/#database-snapshot). -Backups are used when your Database Instance's storage option is a local volume. Snapshots are available for Database Instances that use [Basic](/managed-databases/postgresql-and-mysql/concepts/#basic-block-storage) and [Low Latency](/managed-databases/postgresql-and-mysql/concepts/#block-storage-low-latency) Block Storage volumes. +Backups are used when your Database Instance's storage option is a local volume. Snapshots are available for Database Instances that use [Legacy](/managed-databases/postgresql-and-mysql/concepts/#block-storage-legacy) and [Low Latency](/managed-databases/postgresql-and-mysql/concepts/#block-storage-low-latency) Block Storage volumes. Although they bear the same feature name, automated snapshots and automated backups are different in their design. If you have a Database Instance using Block Storage, it is only possible to use automated snapshots as autobackup. @@ -49,6 +49,4 @@ Backups are used when your Database Instance's storage option is a local volume. You can follow our documentation to [restore](/managed-databases/postgresql-and-mysql/how-to/manage-manual-backups/#how-to-restore-backups) and [export](/managed-databases/postgresql-and-mysql/how-to/manage-manual-backups/#how-to-export-backups) your backups. -For snapshots, you can follow the [how to restore snapshots](/managed-databases/postgresql-and-mysql/how-to/manage-snapshots/#how-to-create-a-database-instance-from-a-snapshot) procedure to create a Database Instance from a snapshot. - - +For snapshots, you can follow the [how to restore snapshots](/managed-databases/postgresql-and-mysql/how-to/manage-snapshots/#how-to-create-a-database-instance-from-a-snapshot) procedure to create a Database Instance from a snapshot. \ No newline at end of file diff --git a/managed-databases/postgresql-and-mysql/how-to/manage-manual-backups.mdx b/managed-databases/postgresql-and-mysql/how-to/manage-manual-backups.mdx index bc3eeea13c..935151913c 100644 --- a/managed-databases/postgresql-and-mysql/how-to/manage-manual-backups.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/manage-manual-backups.mdx @@ -14,7 +14,7 @@ categories: - postgresql-and-mysql --- -Manual backups are useful in cases when you need to have a backup of a specific state of the Database Instance. They can be created for all Database Instances with local storage. +Manual backups are useful in cases when you need to have a backup of a specific state of the Database Instance. They can be created for all Database Instances with Local Storage. You can create manual backups for Database Instances with Block Storage if the Database Instance storage is **inferior or equal to 585 GB**. @@ -62,6 +62,4 @@ Automatic backups can be manually deleted or will be purged after the retention 1. Click the **Backups** tab on your selected Database Instance's information page. 2. Select the backup you wish to delete. 3. Click >**Delete** -4. Click **Delete backup** to confirm. - - +4. Click **Delete backup** to confirm. \ No newline at end of file diff --git a/managed-databases/postgresql-and-mysql/how-to/upgrade-a-database.mdx b/managed-databases/postgresql-and-mysql/how-to/upgrade-a-database.mdx index eaac87b9be..b9d3a900cc 100644 --- a/managed-databases/postgresql-and-mysql/how-to/upgrade-a-database.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/upgrade-a-database.mdx @@ -37,9 +37,9 @@ You can upgrade your Database Instances in two ways: by increasing its Block Sto ## How to change the node type - If you have a Database Instance that uses a local volume, and you want to upgrade to a node type that uses Block volumes, you must [change the volume type](/managed-databases/postgresql-and-mysql/how-to/change-volume-type/) to Block storage first.

+ If you have a Database Instance that uses a local volume, and you want to upgrade to a node type that uses Block volumes, you must [change the volume type](/managed-databases/postgresql-and-mysql/how-to/change-volume-type/) to Block Storage first.

- Similarly, if you have a new-generation Database Instance using a [Low Latency Block volume](/managed-databases/postgresql-and-mysql/concepts/#block-storage-low-latency) node type and want to switch to a first-generation node type, you must first change the volume type to [Basic Block Storage](/managed-databases/postgresql-and-mysql/concepts/#basic-block-storage). + Similarly, if you have a new-generation Database Instance using a [Low Latency Block volume](/managed-databases/postgresql-and-mysql/concepts/#block-storage-low-latency) node type and want to switch to a first-generation node type, you must first change the volume type to [Block Storage Legacy](/managed-databases/postgresql-and-mysql/concepts/#block-storage-legacy). 1. Click **PostgreSQL and MySQL** under **Managed Databases** on the side menu. A list of your Database Instances displays. @@ -51,6 +51,4 @@ You can upgrade your Database Instances in two ways: by increasing its Block Sto Make sure that the Database Instance you choose provides sufficient disk space for your database. Otherwise, an error message will be displayed, and the database will not be upgraded. -The action of changing the node type will perform a rolling upgrade of your Database Instance. During this process, the Database Instance will be unavailable for several tens of seconds. - - +The action of changing the node type will perform a rolling upgrade of your Database Instance. During this process, the Database Instance will be unavailable for several tens of seconds. \ No newline at end of file diff --git a/managed-databases/postgresql-and-mysql/quickstart.mdx b/managed-databases/postgresql-and-mysql/quickstart.mdx index f46e307a64..9d357f09d9 100644 --- a/managed-databases/postgresql-and-mysql/quickstart.mdx +++ b/managed-databases/postgresql-and-mysql/quickstart.mdx @@ -37,13 +37,13 @@ Compared to traditional database management, which requires customers to provide - **Standalone**: creates a standalone database provisioned on a single node. - Select a node type. - Choose your storage type and capacity. Two types of storage are available: - - **Basic Block Storage**: With this type, your storage is decoupled from your compute resources. You can increase your storage space without changing your node type. You can define your storage capacity by entering the desired amount in the box. The volume can be increased up to 10 TB. + - **Block Storage Legacy**: With this type, your storage is decoupled from your compute resources. You can increase your storage space without changing your node type. You can define your storage capacity by entering the desired amount in the box. The volume can be increased up to 10 TB. - - **Block Storage Low Latency**: This storage type works like [Basic Block Storage](#basic-block-storage), while providing lower latency and high resiliency through 5k IOPS. You can increase your volume to up to 10 TB. + - **Block Storage Low Latency**: This storage type works like Block Storage Legacy, while providing lower latency and high resiliency through 5k IOPS. You can increase your volume to up to 10 TB. - **Local SSD Storage**: Your storage is fixed and tied to your compute resource. - The local storage option is only available with the first-generation node types. + The local Storage option is only available with the first-generation node types. - Select the snapshot configuration. You can either leave the default **Automatic** option to enable [autobackups](/managed-databases/postgresql-and-mysql/how-to/enable-autobackup/) or select [Manual snapshots](/managed-databases/postgresql-and-mysql/how-to/manage-snapshots/). - Add a name and set a password for your user. diff --git a/serverless/sql-databases/api-cli/import-data-to-serverless-sql-databases.mdx b/serverless/sql-databases/api-cli/import-data-to-serverless-sql-databases.mdx index d27cf53f5a..c381e1bb9e 100644 --- a/serverless/sql-databases/api-cli/import-data-to-serverless-sql-databases.mdx +++ b/serverless/sql-databases/api-cli/import-data-to-serverless-sql-databases.mdx @@ -13,7 +13,7 @@ dates: Serverless SQL Databases offers near-complete PostgreSQL compatibility, and allows you to import your data from any PostgreSQL-compatible database. -The methods listed below are best suited for database sizes below 100 GB (approx.). Above this size, we recommend you use dedicated tooling to import your data, as your local storage size and bandwidth will create bottlenecks, and the operation may last several hours. +The methods listed below are best suited for database sizes below 100 GB (approx.). Above this size, we recommend you use dedicated tooling to import your data, as your Local Storage size and bandwidth will create bottlenecks, and the operation may last several hours. @@ -202,4 +202,4 @@ You can create a `.csv` file from an existing PostgreSQL table with the [psql \c The PostgreSQL [COPY command](https://www.postgresql.org/docs/current/sql-copy.html) cannot be used directly, as it requires the source file to be available on the PostgreSQL instance itself. -5. When finished, make sure your data is stored in your new database by [connecting to it](/serverless/sql-databases/how-to/connect-to-a-database/), and performing a query. +5. When finished, make sure your data is stored in your new database by [connecting to it](/serverless/sql-databases/how-to/connect-to-a-database/), and performing a query. \ No newline at end of file diff --git a/storage/block/api-cli/managing-a-volume.mdx b/storage/block/api-cli/managing-a-volume.mdx index fb93fe0cf0..642e5adbce 100644 --- a/storage/block/api-cli/managing-a-volume.mdx +++ b/storage/block/api-cli/managing-a-volume.mdx @@ -211,7 +211,7 @@ The file is now transferred. You can connect to your Instance again, and use the └─sdb1 8:17 0 18.6G 0 part ``` -3. Use `growpart` to increase the partition size of your block storage volume (here `sdb1`): +3. Use `growpart` to increase the partition size of your Block Storage volume (here `sdb1`): ``` # Replace /dev/sdX 1 with the name of your partition growpart /dev/sdX 1 diff --git a/storage/block/quickstart.mdx b/storage/block/quickstart.mdx index 7bb0939d5c..bbfdd7ea03 100644 --- a/storage/block/quickstart.mdx +++ b/storage/block/quickstart.mdx @@ -14,7 +14,7 @@ categories: - storage --- -Scaleway [Block Storage](/storage/block/concepts/#block-device) provides network-attached storage that can be plugged in and out of [Instances](/compute/instances/concepts/#instance) like a virtual hard-drive. Block Storage devices are independent of the local storage of Instances, and the fact that they are accessed over a network connection makes it easy to move them between Instances in the same [Availability Zone](/compute/instances/concepts/#availability-zone). +Scaleway [Block Storage](/storage/block/concepts/#block-device) provides network-attached storage that can be plugged in and out of [Instances](/compute/instances/concepts/#instance) like a virtual hard-drive. Block Storage devices are independent of the Local Storage of Instances, and the fact that they are accessed over a network connection makes it easy to move them between Instances in the same [Availability Zone](/compute/instances/concepts/#availability-zone). From the user's point of view, once [mounted](/storage/block/api-cli/managing-a-volume/#mounting-and-using-a-volume), the block device behaves like a regular disk. diff --git a/storage/block/reference-content/differences-between-5kiops-volumes.mdx b/storage/block/reference-content/differences-between-5kiops-volumes.mdx index 2a56367c23..574ce9cf98 100644 --- a/storage/block/reference-content/differences-between-5kiops-volumes.mdx +++ b/storage/block/reference-content/differences-between-5kiops-volumes.mdx @@ -17,8 +17,7 @@ When creating volumes from the Scaleway console, you are prompted to choose betw This page provides information about the differences between Block Storage and Block Storage Low Latency 5K [IOPS](/storage/block/concepts/#iops) volumes. -Refer to the [dedicated documentation](/compute/instances/concepts/#volumes) to learn about the differences between Block Storage and local storage volumes. - +Refer to the [dedicated documentation](/compute/instances/concepts/#volumes) to learn about the differences between Block Storage and Local Storage volumes. ## Underlying hardware diff --git a/tutorials/configure-failover-proxmox/index.mdx b/tutorials/configure-failover-proxmox/index.mdx index 015d3a4317..92cf0e1de0 100644 --- a/tutorials/configure-failover-proxmox/index.mdx +++ b/tutorials/configure-failover-proxmox/index.mdx @@ -42,7 +42,7 @@ The software provides an intuitive web interface as well as a complete REST-API LXC uses pre-built containers. Proxmox provides a selection of the most common containers for download directly from their servers. Before creating a container, an image needs to be downloaded onto the Proxmox host. -1. Click **Storage** > **local** to enter the local storage. +1. Click **Storage** > **Local** to enter the Local Storage. 2. Click **Templates** to download an image from Proxmox: 3. Choose the image to download and click **Download**: @@ -53,7 +53,7 @@ LXC uses pre-built containers. Proxmox provides a selection of the most common c KVM uses a virtual CD-ROM drive to boot the OS installation system from an ISO file. ISO files are archive files that contain identical copies of the data found on optical discs. To create a KVM virtual machine, an installation media has to be uploaded first. -1. Click **Storage** > **local** to enter the local storage. +1. Click **Storage** > **Local** to enter the Local Storage. 2. Click **Upload** to upload an ISO file from your local computer: 3. Choose a local file and upload it to the Proxmox server: diff --git a/tutorials/deploy-nextcloud-s3/index.mdx b/tutorials/deploy-nextcloud-s3/index.mdx index ed32715dc8..7165afd13f 100644 --- a/tutorials/deploy-nextcloud-s3/index.mdx +++ b/tutorials/deploy-nextcloud-s3/index.mdx @@ -207,7 +207,7 @@ NextCloud can use Object Storage as primary storage. This gives you the possibil ### Configuring Object Storage as external storage in NextCloud -You can use NextCloud as a client for Object Storage while using the local storage as primary storage. This can be useful for the migration of an existing NextCloud instance to Object Storage. +You can use NextCloud as a client for Object Storage while using the Local Storage as primary storage. This can be useful for the migration of an existing NextCloud instance to Object Storage. 1. Log into your NextCloud to configure the Object Storage bucket. 2. From the NextCloud interface, click **Apps** in the drop-down menu to access the list of available apps: diff --git a/tutorials/glusterfs/index.mdx b/tutorials/glusterfs/index.mdx index bb7bb85689..a4d94169b5 100644 --- a/tutorials/glusterfs/index.mdx +++ b/tutorials/glusterfs/index.mdx @@ -106,7 +106,7 @@ Before installing GlusterFS, ensure each Instance can resolve the others via the 1. Create and attach Scaleway Block Storage to each Instance: - From the Scaleway Console, [create a new Block Storage volume](/storage/block/how-to/create-a-volume/) for each GlusterFS server. - Attach each volume to the respective Instance. - - Once attached, log into each Instance and check if the block storage is recognized: + - Once attached, log into each Instance and check if the Block Storage is recognized: ``` lsblk ```