From 3a716bd565600fefd5cb8a80a02ba4a4665638a0 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Wed, 24 Sep 2025 17:15:02 +0200 Subject: [PATCH 01/10] docs(ins): remove references to b_ssd volumes --- menu/navigation.json | 16 -- .../instances/api-cli/attaching-a-volume.mdx | 138 ------------------ pages/instances/api-cli/creating-a-volume.mdx | 51 ------- .../instances/api-cli/detaching-a-volume.mdx | 32 ---- .../api-cli/increasing-volume-size.mdx | 55 ------- pages/instances/api-cli/using-routed-ips.mdx | 12 +- pages/instances/how-to/create-an-instance.mdx | 2 +- .../how-to/create-image-from-snapshot.mdx | 4 +- .../migrate-volumes-snapshots-to-sbs.mdx | 2 +- .../reference-content/identify-devices.mdx | 42 +++--- 10 files changed, 31 insertions(+), 323 deletions(-) delete mode 100644 pages/instances/api-cli/attaching-a-volume.mdx delete mode 100644 pages/instances/api-cli/creating-a-volume.mdx delete mode 100644 pages/instances/api-cli/detaching-a-volume.mdx delete mode 100644 pages/instances/api-cli/increasing-volume-size.mdx diff --git a/menu/navigation.json b/menu/navigation.json index e1c23b76aa..67a128bb77 100644 --- a/menu/navigation.json +++ b/menu/navigation.json @@ -1548,22 +1548,6 @@ "label": "Creating and Managing Instances", "slug": "creating-managing-instances-with-cliv2" }, - { - "label": "Creating a volume via the Instance API", - "slug": "creating-a-volume" - }, - { - "label": "Attaching a volume via the Instance API", - "slug": "attaching-a-volume" - }, - { - "label": "Increasing volumes via the Instance API", - "slug": "increasing-volume-size" - }, - { - "label": "Detaching a volume via the Instance API", - "slug": "detaching-a-volume" - }, { "label": "Creating backups", "slug": "creating-backups" diff --git a/pages/instances/api-cli/attaching-a-volume.mdx b/pages/instances/api-cli/attaching-a-volume.mdx deleted file mode 100644 index ec4907ac60..0000000000 --- a/pages/instances/api-cli/attaching-a-volume.mdx +++ /dev/null @@ -1,138 +0,0 @@ ---- -title: Attaching a Block Storage volume via the Block Storage API -description: This page explains how to attach a Block Storage volume using the Scaleway API. -tags: attach-storage storage volume block api -dates: - validation: 2025-07-16 - posted: 2020-01-10 ---- -import Requirements from '@macros/iam/requirements.mdx' - - - - -- A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/iam/how-to/create-api-keys/) -- A [Block Storage volume](/block-storage/how-to/create-a-volume/) - - -1. Query the current volumes of the Instance. - ```sh - curl -X GET \ - -H "X-Auth-Token: $SCW_SECRET_KEY" \ - "https://api.scaleway.com/instance/v1/zones/{zone}/servers/{server_id}" - ``` - - The output displays as follows: - ```json - { - "server": { - "id": "de0f4d6a-3289-4716-97a8-d24b2a58dcd9", - "name": "scw-priceless-diffie", - "arch": "x86_64", - ... - }, - "volumes": { - "0": { - "boot": false, - "volume_type": "sbs_volume", - "id": "1469d160-bfb2-4fdd-bb5d-f8d7c1d0439d", - "zone": "pl-waw-2" - } - }, - ... - } - ``` - - As displayed, our current volumes are only constituted of the root volume. -2. Hot-plug the volume created earlier: - ```json - curl -q \ - -H "X-Auth-Token: $SCW_SECRET_KEY" \ - -H 'Content-Type: application/json' \ - -X PATCH \ - -d '{ - "volumes": { - "0": { - "id": "7fe25caf-0a68-46a7-aeb9-63a278d33e2b", - "volume_type": "l_ssd" - }, - "1": { - "id": "b3a42fb1-e85c-46e9-b0a6-9adb62278295", - "volume_type": "sbs_volume" - } - } - }' \ - https://api.scaleway.com/instance/v1/zones/{zone}/servers/{server_id} - ``` - The output looks like the following example: - ```json - { - "server": { - "id": "1de0f4d6a-3289-4716-97a8-d24b2a58dcd9", - "name": "scw-priceless-diffie", - "arch": "x86_64", - ... - }, - "volumes": { - "0": { - "boot": false, - "volume_type": "sbs_volume", - "id": "7fe25caf-0a68-46a7-aeb9-63a278d33e2b", - "zone": "pl-waw-2" - }, - "1": { - "boot": false, - "volume_type": "sbs_volume", - "id": "b3a42fb1-e85c-46e9-b0a6-9adb62278295", - "zone": "pl-waw-2" - } - }, - ... - } - ``` -3. Use [SSH](/instances/how-to/connect-to-instance/) to log into your server and verify that the new disk exists: - ```bash - lsblk - NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT - sda 8:0 0 953.7M 0 disk - vda 252:0 0 18.6G 0 disk - ├─vda1 252:1 0 18.5G 0 part / - └─vda15 252:15 0 100M 0 part /boot/efi - ``` - - The block volume is presented inside your Instance as `/dev/sdX`, to help you - automate things, a symlink is also present in `/dev/disk/by-id/` with the `id` - of the volume in it: - - ```sh - ls /dev/disk/by-id/ - scsi-0SCW_b_ssd_volume-b3a42fb1-e85c-46e9-b0a6-9adb62278295 - ``` - - If you query information about the block volume from the API, the `server_id` - on which it is plugged in is displayed: - - ```json - curl -q \ - -H "X-Auth-Token: $SCW_SECRET_KEY" \ - -H 'Content-Type: application/json' \ - https://api.scaleway.com/instance/v1/zones/fr-par-1/volumes/b3a42fb1-e85c-46e9-b0a6-9adb62278295 - { - "volume": { - "size": 10000000000, - "state": "available", - "name": "block-volume101", - ... - "id": "b3a42fb1-e85c-46e9-b0a6-9adb62278295", - "volume_type": "sbs_volume", - "server": { - "id": "be3c50af-e8f3-4ff4-90fe-66972f06670d", - "name": "scw-blissful-engelbart" - } - } - } - ``` - - diff --git a/pages/instances/api-cli/creating-a-volume.mdx b/pages/instances/api-cli/creating-a-volume.mdx deleted file mode 100644 index bd39deb6e7..0000000000 --- a/pages/instances/api-cli/creating-a-volume.mdx +++ /dev/null @@ -1,51 +0,0 @@ ---- -title: Creating a Block Storage volume via the Instance API -description: This page explains how to create a Block Storage volume using the Scaleway API. -tags: block-storage block volume create storage -dates: - validation: 2025-06-02 - posted: 2020-01-10 ---- -import Requirements from '@macros/iam/requirements.mdx' - - - - Creating Block Storage volumes via the Instances API is deprected and the information below is proposed for informative purposes only. [Learn how to create a volume using the Block Storage API.](https://www.scaleway.com/en/developers/api/block/#path-volume-create-a-volume) - - - - -- A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/iam/how-to/create-api-keys/) - - -1. Create a block volume from the API by launching the following command: - ``` - curl -q \ - -H "X-Auth-Token: $SCW_SECRET_KEY" \ - -H 'Content-Type: application/json' \ - -X POST \ - -d '{"name": "block-volume-101", "organization": "'$SCW_ORGANIZATION'", "size": 10000000000, "volume_type": "b_ssd"}' \ - https://api.scaleway.com/instance/v1/zones/fr-par-1/volumes - ``` -2. To retrieve the current status of the block volume, query the volume endpoint. - ``` - curl -q \ - -H "X-Auth-Token: $SCW_SECRET_KEY" \ - -H 'Content-Type: application/json' \ - https://api.scaleway.com/instance/v1/zones/fr-par-1/volumes/b3a42fb1-e85c-46e9-b0a6-9adb62278295 - { - "volume": { - "size": 10000000000, - "state": "available", - "name": "block-volume101", - "modification_date": "2019-09-03T09:57:53.742130+00:00", - ... - "id": "b3a42fb1-e85c-46e9-b0a6-9adb62278295", - "volume_type": "b_ssd", - "server": null - } - } - ``` - diff --git a/pages/instances/api-cli/detaching-a-volume.mdx b/pages/instances/api-cli/detaching-a-volume.mdx deleted file mode 100644 index 4979a6fcf6..0000000000 --- a/pages/instances/api-cli/detaching-a-volume.mdx +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Detaching a Block Storage volume via the Instance API -description: This page explains how to detach a Block Storage volume from an Instance using the Scaleway API. -tags: detach volume block storage unlink unplug api -dates: - validation: 2025-06-02 - posted: 2020-01-10 ---- -import Requirements from '@macros/iam/requirements.mdx' - - - - -- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - - -To detach a block volume from a running Instance, relaunch the API call and omit the volume you want to hot unplug. Like so: - -``` -curl -q \ - -H "X-Auth-Token: $SCW_SECRET_KEY" \ - -H 'Content-Type: application/json' \ - -X PATCH \ - -d '{ - "volumes": { - "0": "7fe25caf-0a68-46a7-aeb9-63a278d33e2b", - } - }' \ - https://api.scaleway.com/instance/v1/zones/{zone}/servers/{server_id} -``` - - diff --git a/pages/instances/api-cli/increasing-volume-size.mdx b/pages/instances/api-cli/increasing-volume-size.mdx deleted file mode 100644 index bf572e057f..0000000000 --- a/pages/instances/api-cli/increasing-volume-size.mdx +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: Increasing Block Storage volumes via the Instance API -description: This page explains how to increase a Block Storage volume using the Scaleway API. -tags: increase expand increment raise storage volume block -dates: - validation: 2025-06-02 - posted: 2020-01-10 ---- -import Requirements from '@macros/iam/requirements.mdx' - - - - Management of Block Storage volumes via the Instances API is deprecated. We recommend migrating existing volumes to the Block Storage API for continued support and improved functionality. For step-by-step instructions on migrating your volumes, refer to our [How to migrate existing volumes and snapshots to Scaleway's new Block Storage management](/instances/how-to/migrate-volumes-snapshots-to-sbs/). - - -The Instances API allows you to interact with Block Storage volumes programmatically through API calls. To increase the size of a volume using the Block Storage API, refer to the [dedicated documentation](/block-storage/api-cli/increasing-volume-size/). - - - -- A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/iam/how-to/create-api-keys/) -- A [Block Storage volume](/instances/api-cli/creating-a-volume/) attached to an Instance - - -1. Inspect the volume and verify its name, size, and if the type is `b_ssd` by running the following request. - ``` - curl -q -H "X-Auth-Token: $SCW_SECRET_KEY" -X GET https://api.scaleway.com/instance/v1/zones//volumes/ - ``` - - - Replace `REGION` with the geographical region of the Instance. This value can either be `fr-par-1`, `fr-par-2`, or `fr-par-3` for Instances located in Paris, `nl-ams-1`, `nl-ams-2` or `nl-ams-3` for Instances located in Amsterdam, or `pl-waw-1`, `pl-waw-2`, or `pl-waw-3` for Instances located in Warsaw. Replace `VOLUME_ID` with the unique identifier of the volume, which can be found on the Scaleway console under **CPU & GPU Instances** > **Volumes** > **More info** (for the selected volume). - - - The following response should appear as an output: - - ``` - {"volume": {"creation_date": "2020-06-02T08:04:50.094118+00:00", "server": null, "id": "", "size": 25000000000, "name": "myAwesomeVolume", "zone": "", "export_uri": null, "volume_type": "b_ssd", "modification_date": "2020-06-02T08:04:50.094118+00:00", "state": "available", "organization": ""}} - ``` -2. To modify the volume size, run the request below: - ``` - curl https://api.scaleway.com/instance/v1/zones/REGION/volumes/VOLUME_ID -H "X-Auth-Token: $SCW_SECRET_KEY" -X PATCH -H 'Content-Type: application/json;charset=utf-8' --data '{ "name":"new_name", "size":26000000000 }' - ``` - Replace `REGION` and `VOLUME_ID` following the guidelines mentioned previously and replace the existing size value with the new one. - - - You can use the same request to change the name of your volume by replacing `new_name` with another of your choice. If you do not wish to change the volume name, erase `"name":"new_name",` from the request before running it. - - - A response appears confirming the changes: - ``` - {"volume": {"creation_date": "2020-06-02T08:04:50.094118+00:00", "server": null, "id": "VOLUME_ID", "size": 26000000000, "name": "new_name", "zone": "REGION", "export_uri": null, "volume_type": "b_ssd", "modification_date": "2020-06-02T08:08:27.385208+00:00", "state": "resizing", "organization": "ORGANIZATION_ID"}} - ``` - - diff --git a/pages/instances/api-cli/using-routed-ips.mdx b/pages/instances/api-cli/using-routed-ips.mdx index cba8fbbad1..f568da39f9 100644 --- a/pages/instances/api-cli/using-routed-ips.mdx +++ b/pages/instances/api-cli/using-routed-ips.mdx @@ -203,7 +203,7 @@ Run the following command to create an Instance with the previously created IP a "id": "ccc917ca-8250-4b7b-89a9-614f08b17826", "name": "Ubuntu 22.04 Jammy Jellyfish", "size": 10000000000, - "volume_type": "b_ssd" + "volume_type": "sbs_5k" }, "state": "available", "tags": [], @@ -384,7 +384,7 @@ And now we create the Instance. "id": "ccc917ca-8250-4b7b-89a9-614f08b17826", "name": "Ubuntu 22.04 Jammy Jellyfish", "size": 10000000000, - "volume_type": "b_ssd" + "volume_type": "sbs_5k" }, "state": "available", "tags": [], @@ -537,7 +537,7 @@ Then you can create a new Instance using those IPs through the `public_ips` fiel "id": "ccc917ca-8250-4b7b-89a9-614f08b17826", "name": "Ubuntu 22.04 Jammy Jellyfish", "size": 10000000000, - "volume_type": "b_ssd" + "volume_type": "sbs_5k" }, "state": "available", "tags": [], @@ -781,7 +781,7 @@ You can verify if your Instance is enabled for routed IPs through the `/servers` "id": "72d9e5b6-60c6-499b-be03-03c9fb07daa3", "name": "Ubuntu 22.04 Jammy Jellyfish", "size": 10000000000, - "volume_type": "b_ssd" + "volume_type": "sbs_5k" }, "state": "available", "tags": [], @@ -850,7 +850,7 @@ You can verify if your Instance is enabled for routed IPs through the `/servers` "size": 10000000000, "state": "available", "tags": [], - "volume_type": "b_ssd", + "volume_type": "sbs_5k", "zone": "pl-waw-2" } }, @@ -910,7 +910,7 @@ You can verify if your Instance is enabled for routed IPs through the `/servers` "id": "93dbf1e9-cd13-4f60-b427-6fa6b2ad5f99", "name": "Ubuntu 22.04 Jammy Jellyfish", "size": 10000000000, - "volume_type": "b_ssd" + "volume_type": "sbs_5k" }, "state": "available", "tags": [], diff --git a/pages/instances/how-to/create-an-instance.mdx b/pages/instances/how-to/create-an-instance.mdx index 073f308ca1..981a1ce53a 100644 --- a/pages/instances/how-to/create-an-instance.mdx +++ b/pages/instances/how-to/create-an-instance.mdx @@ -177,7 +177,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 label, e.g. `ubuntu_noble` which is the label for the Ubuntu 24.04 Noble Numbat image. | | 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 (`sbs_5k` or `sbs_10k`), 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"`, `sbs_5k`, or `"sbs_15k"`). 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). | 4. Use the following curl command, replacing the payload with the one you specified in step 2, to create your Instance. diff --git a/pages/instances/how-to/create-image-from-snapshot.mdx b/pages/instances/how-to/create-image-from-snapshot.mdx index 48ae2b7f60..1e22235364 100644 --- a/pages/instances/how-to/create-image-from-snapshot.mdx +++ b/pages/instances/how-to/create-image-from-snapshot.mdx @@ -55,7 +55,7 @@ scw instance image create snapshot-id="$SCW_VOLUME_ID_1" additional-volumes.0.id [additional-volumes.{index}.id] UUID of the snapshot to add [additional-volumes.{index}.name] Name of the additional snapshot [additional-volumes.{index}.size] Size of the additional snapshot - [additional-volumes.{index}.volume-type] Underlying volume type of the additional snapshot (l_ssd | b_ssd | unified | scratch | sbs_volume | sbs_snapshot) + [additional-volumes.{index}.volume-type] Underlying volume type of the additional snapshot (l_ssd | sbs_5k | unified | scratch | sbs_volume | sbs_snapshot) [additional-volumes.{index}.project-id] Project ID that own the additional snapshot [project-id] Project ID to use. If none is passed the default project ID will be used [tags.{index}] Tags of the image @@ -93,6 +93,6 @@ curl --location "https://api.scaleway.com/instance/v1/zones/$SCW_AVAILABILITY_ZO Supported volume IDs include: - Local Storage volumes (`l_ssd`) - Block Storage Low Latency volumes (`sbs`) - - Block Storage legacy (`b_ssd`) volumes (deprecated). + - Block Storage legacy (`sbs_5k`) volumes (deprecated). diff --git a/pages/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx b/pages/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx index 336e80687c..232a6c5db9 100644 --- a/pages/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx +++ b/pages/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx @@ -1,7 +1,7 @@ --- title: How to migrate existing volumes and snapshots to Scaleway's new Block Storage management description: Learn how to migrate your existing Block Storage volumes and snapshots to Scaleway's Block Storage management. -tags: instance snapshot volume b_ssd sbs +tags: instance snapshot volume sbs_5k sbs_15k sbs dates: validation: 2025-07-21 posted: 2024-08-07 diff --git a/pages/instances/reference-content/identify-devices.mdx b/pages/instances/reference-content/identify-devices.mdx index 8c15c9d511..beabd498ee 100644 --- a/pages/instances/reference-content/identify-devices.mdx +++ b/pages/instances/reference-content/identify-devices.mdx @@ -13,18 +13,18 @@ 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 stably identify devices on a Linux host. -## Identifying Instance Block Storage volumes (b_ssd) +## Identifying Instance Block Storage volumes (sbs_5k) -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 file system, i.e. as `/dev/sd{a,b,c...}` devices. +Instance Block Storage (`sbs_5k` or `sbs_15k`) volumes are connected to the Instance as SCSI disks. They will therefore appear as devices handled by the sd driver in the dev file system, 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 (`sbs_5k`) volumes have the vendor name `SCW`, the model/product name (e.g., `sbs_5k`), 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: ```sh root@test-instance:~# lsblk --scsi -NAME HCTL TYPE VENDOR MODEL REV SERIAL TRAN -sda 2:0:0:0 disk SCW b_ssd v42 volume-f7a6f113-aaf6-4540-ac5a-9e18d7f61478 +NAME HCTL TYPE VENDOR MODEL REV SERIAL TRAN +sda 0:0:1:0 disk SCW sbs v42 volume-a5fb1cc7-70d3-457f-b4 ``` Through `udev` and the sets of configured `udev` rules, these attributes will be retrieved and symlinks will be automatically created for the `/dev/sdX` devices. As the attributes are stable, these symlinks provide a stable path to the devices, as long as the udev rule does not change. @@ -46,12 +46,12 @@ root@test-instance:~# /lib/udev/scsi_id --export --whitelisted -d /dev/sda ID_SCSI=1 ID_VENDOR=SCW ID_VENDOR_ENC=SCW\x20\x20\x20\x20\x20 -ID_MODEL=b_ssd -ID_MODEL_ENC=b_ssd\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20 +ID_MODEL=sbs +ID_MODEL_ENC=sbs\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20 ID_REVISION=v42 ID_TYPE=disk -ID_SERIAL=0SCW_b_ssd_volume-f7a6f113-aaf6-4540-ac5a-9e18d7f61478 -ID_SERIAL_SHORT=volume-f7a6f113-aaf6-4540-ac5a-9e18d7f61478 +ID_SERIAL=0SCW_sbs_volume-a5fb1cc7-70d3-457f-b4e0-a757997a4b33 +ID_SERIAL_SHORT=volume-a5fb1cc7-70d3-457f-b4e0-a757997a4b33 ``` The third and fourth rules create the symlinks properly, using these attributes. This will result in the following symlinks being created: @@ -59,10 +59,11 @@ The third and fourth rules create the symlinks properly, using these attributes. ```sh root@test-instance:~# ls -l /dev/disk/by-id/ total 0 -lrwxrwxrwx 1 root root 9 Mar 7 16:13 scsi-0SCW_b_ssd_volume-f7a6f113-aaf6-4540-ac5a-9e18d7f61478 -> ../../sda -lrwxrwxrwx 1 root root 10 Mar 7 16:13 scsi-0SCW_b_ssd_volume-f7a6f113-aaf6-4540-ac5a-9e18d7f61478-part1 -> ../../sda1 -lrwxrwxrwx 1 root root 11 Mar 7 16:13 scsi-0SCW_b_ssd_volume-f7a6f113-aaf6-4540-ac5a-9e18d7f61478-part14 -> ../../sda14 -lrwxrwxrwx 1 root root 11 Mar 7 16:13 scsi-0SCW_b_ssd_volume-f7a6f113-aaf6-4540-ac5a-9e18d7f61478-part15 -> ../../sda15 +lrwxrwxrwx 1 root root 9 Sep 19 09:14 scsi-0SCW_sbs_volume-a5fb1cc7-70d3-457f-b4e0-a757997a4b33 -> ../../sda +lrwxrwxrwx 1 root root 10 Sep 19 09:14 scsi-0SCW_sbs_volume-a5fb1cc7-70d3-457f-b4e0-a757997a4b33-part1 -> ../../sda1 +lrwxrwxrwx 1 root root 11 Sep 19 09:14 scsi-0SCW_sbs_volume-a5fb1cc7-70d3-457f-b4e0-a757997a4b33-part14 -> ../../sda14 +lrwxrwxrwx 1 root root 11 Sep 19 09:14 scsi-0SCW_sbs_volume-a5fb1cc7-70d3-457f-b4e0-a757997a4b33-part15 -> ../../sda15 +lrwxrwxrwx 1 root root 11 Sep 19 09:14 scsi-0SCW_sbs_volume-a5fb1cc7-70d3-457f-b4e0-a757997a4b33-part16 -> ../../sda16 ``` In this setup, we can see an entry named after the `f7a6f113-aaf6-4540-ac5a-9e18d7f61478` volume, pointing to the `/dev/sda` device node, along with three entries also created automatically which point to the individual partitions on the volume. @@ -83,7 +84,7 @@ This rule will create a symlink `/dev/disk/scw/volume-` (where `uuid` is t ```sh root@test-instance:~# ls -l /dev/disk/scw/ total 0 -lrwxrwxrwx 1 root root 9 Mar 7 16:18 volume-f7a6f113-aaf6-4540-ac5a-9e18d7f61478 -> ../../sda +lrwxrwxrwx 1 root root 9 Mar 7 16:18 volume-a5fb1cc7-70d3-457f-b4e0-a757997a4b33 -> ../../sda ``` Note that this rule relies on `ID_VENDOR` and `ID_SERIAL_SHORT` being in the environment, and thus relies on the execution of `scsi_id` and the importing of its output. @@ -94,22 +95,21 @@ For more details on writing `udev` rules, please see `man 7 udev`. 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. +The only difference is the SCSI model attribute. Instead of being fixed to the value `sbs_5k`, its value depends on the class of the Block Storage volume. -Two Block Storage volume classes currently exist: `bssd`, and `sbs`. Block Storage volumes migrated from Instance Block Storage (`b_ssd`) volumes have class `bssd`. +Two Block Storage volume classes currently exist: `bssd`, and `sbs`. Block Storage volumes migrated from Instance Block Storage (`sbs_5k`) 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. +Block Storage volumes with class `bssd` have a SCSI model of `sbs_5k`, so migrated volumes won't change characteristics. Otherwise, Block Storage volumes have a SCSI model equal to the volume's class. For example: ```sh root@test-instance:~# lsblk --scsi -NAME HCTL TYPE VENDOR MODEL REV SERIAL TRAN -sda 0:0:0:0 disk SCW sbs v42 volume-7831d52c-758f-4a94-a074-39bfa14b66d8 -sdb 0:0:1:0 disk SCW b_ssd v42 volume-03e206f6-2a3b-4223-bb56-3d7f1495903f + HCTL TYPE VENDOR MODEL REV SERIAL TRAN +sda 0:0:1:0 disk SCW sbs v42 volume-a5fb1cc7-70d3-457f-b4e0-a757997a4b33 ``` -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 (`sbs_5k`) volume which has been migrated to Block Storage, and is now a Block Storage volume with class `bssd`. ## Identifying VPC Private Network interfaces From 69e165e45e45f0f8b9bf774e1ba9df7da00127b5 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Wed, 24 Sep 2025 17:27:05 +0200 Subject: [PATCH 02/10] docs(ins): update content --- .../how-to/create-image-from-snapshot.mdx | 26 +++++++++---------- .../reference-content/identify-devices.mdx | 24 ++--------------- 2 files changed, 15 insertions(+), 35 deletions(-) diff --git a/pages/instances/how-to/create-image-from-snapshot.mdx b/pages/instances/how-to/create-image-from-snapshot.mdx index 1e22235364..0223fb1341 100644 --- a/pages/instances/how-to/create-image-from-snapshot.mdx +++ b/pages/instances/how-to/create-image-from-snapshot.mdx @@ -49,19 +49,19 @@ scw instance image create snapshot-id="$SCW_VOLUME_ID_1" additional-volumes.0.id Supported arguments for the image create commmand include: ``` ARGS: - [name=] Name of the image - snapshot-id UUID of the snapshot that will be used as root volume in the image - arch Architecture of the image (unknown_arch | x86_64 | arm | arm64) - [additional-volumes.{index}.id] UUID of the snapshot to add - [additional-volumes.{index}.name] Name of the additional snapshot - [additional-volumes.{index}.size] Size of the additional snapshot - [additional-volumes.{index}.volume-type] Underlying volume type of the additional snapshot (l_ssd | sbs_5k | unified | scratch | sbs_volume | sbs_snapshot) - [additional-volumes.{index}.project-id] Project ID that own the additional snapshot - [project-id] Project ID to use. If none is passed the default project ID will be used - [tags.{index}] Tags of the image - [public] True to create a public image - [organization-id] Organization ID to use. If none is passed the default organization ID will be used - [zone=fr-par-1] Zone to target. If none is passed will use default zone from the config (fr-par-1 | fr-par-2 | fr-par-3 | nl-ams-1 | nl-ams-2 | nl-ams-3 | pl-waw-1 | pl-waw-2 | pl-waw-3) + [name=] Name of the image + snapshot-id UUID of the snapshot that will be used as root volume in the image + arch Architecture of the image (unknown_arch | x86_64 | arm | arm64) + [additional-volumes.{index}.id] UUID of the snapshot to add + [additional-volumes.{index}.name] Name of the additional snapshot + [additional-volumes.{index}.size] Size of the additional snapshot + [additional-volumes.{index}.volume-type] Underlying volume type of the additional snapshot (l_ssd | unified | scratch | sbs_volume | sbs_snapshot) + [additional-volumes.{index}.project-id] Project ID that own the additional snapshot + [project-id] Project ID to use. If none is passed the default project ID will be used + [tags.{index}] Tags of the image + [public] True to create a public image + [organization-id] Organization ID to use. If none is passed the default organization ID will be used + [zone=fr-par-1] Zone to target. If none is passed will use default zone from the config (fr-par-1 | fr-par-2 | fr-par-3 | nl-ams-1 | nl-ams-2 | nl-ams-3 | pl-waw-1 | pl-waw-2 | pl-waw-3) ``` diff --git a/pages/instances/reference-content/identify-devices.mdx b/pages/instances/reference-content/identify-devices.mdx index beabd498ee..006fb5ce6c 100644 --- a/pages/instances/reference-content/identify-devices.mdx +++ b/pages/instances/reference-content/identify-devices.mdx @@ -13,11 +13,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 stably identify devices on a Linux host. -## Identifying Instance Block Storage volumes (sbs_5k) +## Identifying Instance Block Storage volumes (sbs) Instance Block Storage (`sbs_5k` or `sbs_15k`) volumes are connected to the Instance as SCSI disks. They will therefore appear as devices handled by the sd driver in the dev file system, 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 (`sbs_5k`) volumes have the vendor name `SCW`, the model/product name (e.g., `sbs_5k`), 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 (`sbs_5k`) volumes have the vendor name `SCW`, the model/product name `sbs`, 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: @@ -91,26 +91,6 @@ Note that this rule relies on `ID_VENDOR` and `ID_SERIAL_SHORT` being in the env 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. - -The only difference is the SCSI model attribute. Instead of being fixed to the value `sbs_5k`, its value depends on the class of the Block Storage volume. - -Two Block Storage volume classes currently exist: `bssd`, and `sbs`. Block Storage volumes migrated from Instance Block Storage (`sbs_5k`) volumes have class `bssd`. - -Block Storage volumes with class `bssd` have a SCSI model of `sbs_5k`, so migrated volumes won't change characteristics. Otherwise, Block Storage volumes have a SCSI model equal to the volume's class. - -For example: - -```sh -root@test-instance:~# lsblk --scsi - HCTL TYPE VENDOR MODEL REV SERIAL TRAN -sda 0:0:1:0 disk SCW sbs v42 volume-a5fb1cc7-70d3-457f-b4e0-a757997a4b33 -``` - -Here, the first volume has been created through the Block Storage API with class `sbs`. The second volume is an Instance Block Storage (`sbs_5k`) volume which has been migrated to Block Storage, and is now a Block Storage volume with class `bssd`. - ## Identifying VPC Private Network interfaces VPC Private Networks to which the Instance is connected will appear as virtio PCI network devices, handled by the `virtio-net` driver. From 3afd6837b177d0572b5b7e6cbe5d855fb9ce914d Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Thu, 25 Sep 2025 15:39:54 +0200 Subject: [PATCH 03/10] docs(ins): update content --- .../creating-managing-instances-with-cliv2.mdx | 2 +- pages/instances/api-cli/using-routed-ips.mdx | 12 ++++++------ 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/pages/instances/api-cli/creating-managing-instances-with-cliv2.mdx b/pages/instances/api-cli/creating-managing-instances-with-cliv2.mdx index 018a28d751..2393dc25d1 100644 --- a/pages/instances/api-cli/creating-managing-instances-with-cliv2.mdx +++ b/pages/instances/api-cli/creating-managing-instances-with-cliv2.mdx @@ -189,7 +189,7 @@ Scaleway Instances provide you with resources to develop, test code and deploy y 1. Run the following command to create a [block volume](/instances/concepts/#block-volumes): - `scw instance volume create size=10GB volume-type=b_ssd` + `scw instance volume create size=10GB volume-type=sbs_volume` Your block volume has been created: ``` diff --git a/pages/instances/api-cli/using-routed-ips.mdx b/pages/instances/api-cli/using-routed-ips.mdx index f568da39f9..6e4a3df0a8 100644 --- a/pages/instances/api-cli/using-routed-ips.mdx +++ b/pages/instances/api-cli/using-routed-ips.mdx @@ -203,7 +203,7 @@ Run the following command to create an Instance with the previously created IP a "id": "ccc917ca-8250-4b7b-89a9-614f08b17826", "name": "Ubuntu 22.04 Jammy Jellyfish", "size": 10000000000, - "volume_type": "sbs_5k" + "volume_type": "sbs_volume" }, "state": "available", "tags": [], @@ -384,7 +384,7 @@ And now we create the Instance. "id": "ccc917ca-8250-4b7b-89a9-614f08b17826", "name": "Ubuntu 22.04 Jammy Jellyfish", "size": 10000000000, - "volume_type": "sbs_5k" + "volume_type": "sbs_volume" }, "state": "available", "tags": [], @@ -537,7 +537,7 @@ Then you can create a new Instance using those IPs through the `public_ips` fiel "id": "ccc917ca-8250-4b7b-89a9-614f08b17826", "name": "Ubuntu 22.04 Jammy Jellyfish", "size": 10000000000, - "volume_type": "sbs_5k" + "volume_type": "sbs_volume" }, "state": "available", "tags": [], @@ -781,7 +781,7 @@ You can verify if your Instance is enabled for routed IPs through the `/servers` "id": "72d9e5b6-60c6-499b-be03-03c9fb07daa3", "name": "Ubuntu 22.04 Jammy Jellyfish", "size": 10000000000, - "volume_type": "sbs_5k" + "volume_type": "sbs_volume" }, "state": "available", "tags": [], @@ -850,7 +850,7 @@ You can verify if your Instance is enabled for routed IPs through the `/servers` "size": 10000000000, "state": "available", "tags": [], - "volume_type": "sbs_5k", + "volume_type": "sbs_volume", "zone": "pl-waw-2" } }, @@ -910,7 +910,7 @@ You can verify if your Instance is enabled for routed IPs through the `/servers` "id": "93dbf1e9-cd13-4f60-b427-6fa6b2ad5f99", "name": "Ubuntu 22.04 Jammy Jellyfish", "size": 10000000000, - "volume_type": "sbs_5k" + "volume_type": "sbs_volume" }, "state": "available", "tags": [], From 048cd5a08daf9dbafc75869c53ad7d6c72e49602 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Thu, 25 Sep 2025 16:33:03 +0200 Subject: [PATCH 04/10] docs(ins): update content --- ...creating-managing-instances-with-cliv2.mdx | 156 +++++++++++------- .../instances/api-cli/migrating-instances.mdx | 4 +- .../snapshot-import-export-feature.mdx | 2 +- pages/instances/how-to/create-an-instance.mdx | 2 +- .../how-to/create-image-from-snapshot.mdx | 2 +- .../migrate-volumes-snapshots-to-sbs.mdx | 2 +- .../reference-content/identify-devices.mdx | 4 +- ...ving-instances-between-az-and-projects.mdx | 2 +- 8 files changed, 104 insertions(+), 70 deletions(-) diff --git a/pages/instances/api-cli/creating-managing-instances-with-cliv2.mdx b/pages/instances/api-cli/creating-managing-instances-with-cliv2.mdx index 2393dc25d1..72ff3a39c8 100644 --- a/pages/instances/api-cli/creating-managing-instances-with-cliv2.mdx +++ b/pages/instances/api-cli/creating-managing-instances-with-cliv2.mdx @@ -189,82 +189,114 @@ Scaleway Instances provide you with resources to develop, test code and deploy y 1. Run the following command to create a [block volume](/instances/concepts/#block-volumes): - `scw instance volume create size=10GB volume-type=sbs_volume` + `scw block volume create name=my-volume from-empty.size=10G perf-iops=5000` Your block volume has been created: ``` - ID 12345678-1234-1234-4321-123456789123 - Name cli-vol-albattani - ExportURI - - Size 10 GB - VolumeType b_ssd - CreationDate 1 second from now - ModificationDate 1 second from now - Organization 12345678-1234-1234-4321-123456789123 - Project 12345678-1234-1234-4321-123456789123 - State available + ID 12345678-1234-1234-4321-123456789123 + Name my-volume + Type sbs_volume + Size 10 GB + ProjectID 12345678-1234-1234-4321-123456789123 + CreatedAt now + UpdatedAt now + Status creating + Zone fr-par-1 + Specs.PerfIops 5000 + Specs.Class sbs ``` 2. Write down your block volume's ID. You will need it in the next steps. -3. Type the following command in your terminal to attach your block volume to your Instance. Make sure you replace `n4m3-0f-y0Ur-s3rv3r-id` with your server ID and `n4m3-0f-y0Ur-volume-id` with your volume ID. +3. Type the following command in your terminal to attach your block volume to your Instance. Make sure you replace `` with your server ID and `` with your volume ID. - `scw instance server attach-volume server-id=n4m3-0f-y0Ur-s3rv3r-id volume-id=n4m3-0f-y0Ur-volume-id` + `scw instance server attach-volume server-id= volume-id=` You will see an output similar to the following: ``` - Server.ID 12345678-1234-1234-4321-123456789123 - Server.Name scw-sleepy-mestorf - Server.Organization 12345678-1234-1234-4321-123456789123 - Server.Project 12345678-1234-1234-4321-123456789123 - Server.CommercialType GP1-S - Server.CreationDate 4 days ago - Server.DynamicIPRequired false - Server.EnableIPv6 true - Server.Hostname scw-sleepy-mestorf - Server.Image.ID 12345678-1234-1234-4321-123456789123 - Server.Image.Name Ubuntu 20.04 Focal Fossa - Server.Image.Arch x86_64 - Server.Image.CreationDate 4 months ago - Server.Image.ModificationDate 4 months ago - Server.Image.ExtraVolumes 0 - Server.Image.FromServer - - Server.Image.Organization 12345678-1234-1234-4321-123456789123 - Server.Image.Public true - Server.Image.RootVolume 12345678-1234-1234-4321-123456789123 - Server.Image.State available - Server.Image.Project 12345678-1234-1234-4321-123456789123 - Server.Image.Zone fr-par-1 - Server.Protected false - Server.PrivateIP 10.194.79.129 - Server.PublicIP.ID 12345678-1234-1234-4321-123456789123 - Server.PublicIP.Address 12.345.678.123 - Server.PublicIP.Dynamic false - Server.ModificationDate 4 days ago - Server.State running - Server.Location fr-par-1 - Server.IPv6.Address 2001:bc8:610:6300::1 - Server.IPv6.Gateway 2001:bc8:610:6300:: - Server.IPv6.Netmask 64 - Server.Bootscript x86_64 mainline 4.4.230 rev1 - Server.BootType local - Server.Volumes 2 - Server.SecurityGroup.ID 12345678-1234-1234-4321-123456789123 - Server.SecurityGroup.Name Default security group - Server.StateDetail booted - Server.Arch x86_64 - Server.Zone fr-par-1 + Server.ID 12345678-1234-1234-4321-123456789123 + Server.Name scw-keen-fermi + Server.Organization 12345678-1234-1234-4321-123456789123 + Server.Project 12345678-1234-1234-4321-123456789123 + Server.CommercialType DEV1-S + Server.CreationDate 40 seconds ago + Server.DynamicIPRequired false + Server.RoutedIPEnabled true + Server.EnableIPv6 false + Server.Hostname scw-keen-fermi + Server.Image.ID 12345678-1234-1234-4321-123456789123 + Server.Image.Name Ubuntu 24.04 Noble Numbat + Server.Image.Arch x86_64 + Server.Image.CreationDate 1 week ago + Server.Image.ModificationDate 1 week ago + Server.Image.ExtraVolumes 0 + Server.Image.FromServer - + Server.Image.Organization 12345678-1234-1234-4321-123456789123 + Server.Image.Public true + Server.Image.RootVolume 12345678-1234-1234-4321-123456789123 + Server.Image.State available + Server.Image.Project 12345678-1234-1234-4321-123456789123 + Server.Image.Zone fr-par-1 + Server.Protected false + Server.PublicIP.ID 12345678-1234-1234-4321-123456789123 + Server.PublicIP.Address 51.158.x.y + Server.PublicIP.Gateway 62.210.0.1 + Server.PublicIP.Netmask 32 + Server.PublicIP.Family inet + Server.PublicIP.Dynamic false + Server.PublicIP.ProvisioningMode dhcp + Server.PublicIP.IpamID 12345678-1234-1234-4321-123456789123 + Server.PublicIP.State attached + Server.PublicIPs.0.ID 12345678-1234-1234-4321-123456789123 + Server.PublicIPs.0.Address 51.158.x.y + Server.PublicIPs.0.Gateway 62.210.0.1 + Server.PublicIPs.0.Netmask 32 + Server.PublicIPs.0.Family inet + Server.PublicIPs.0.Dynamic false + Server.PublicIPs.0.ProvisioningMode dhcp + Server.PublicIPs.0.IpamID 12345678-1234-1234-4321-123456789123 + Server.PublicIPs.0.State attached + Server.PublicIPs.1.ID 12345678-1234-1234-4321-123456789123 + Server.PublicIPs.1.Address 2001:bc8::1 + Server.PublicIPs.1.Gateway fe80::dc00:ff:feca:57bc + Server.PublicIPs.1.Netmask 64 + Server.PublicIPs.1.Family inet6 + Server.PublicIPs.1.Dynamic false + Server.PublicIPs.1.ProvisioningMode slaac + Server.PublicIPs.1.IpamID 12345678-1234-1234-4321-123456789123 + Server.PublicIPs.1.State attached + Server.MacAddress de:00:00:ca:57:bb + Server.ModificationDate 35 seconds ago + Server.State running + Server.Location fr-par-1 + Server.BootType local + Server.Volumes.0.ID 12345678-1234-1234-4321-123456789123 + Server.Volumes.0.VolumeType sbs_volume + Server.Volumes.0.State available + Server.Volumes.0.Boot false + Server.Volumes.0.Zone fr-par-1 + Server.Volumes.1.ID 12345678-1234-1234-4321-123456789123 + Server.Volumes.1.VolumeType sbs_volume + Server.Volumes.1.State attaching + Server.Volumes.1.Boot false + Server.Volumes.1.Zone fr-par-1 + Server.SecurityGroup.ID 12345678-1234-1234-4321-123456789123 + Server.SecurityGroup.Name Base group + Server.StateDetail booting kernel + Server.Arch x86_64 + Server.Zone fr-par-1 + Server.EndOfService false ``` ## Powering off an Instance -Type the following command in your terminal and replace "your-server" with the ID of your server. +Type the following command in your terminal and replace `` with the ID of your server. -`scw instance server stop your-server` +`scw instance server stop ` You will see the following output: ``` -Poweroff successful for the server. +✅ Poweroff successfully started for the server. ``` Your Instance has been powered off. @@ -275,14 +307,16 @@ Your Instance has been powered off. This action will delete all your volumes and data located on your Instance. To avoid losing data, it is recommended to perform regular snapshots. -Ensure your Instance is powered off and then run the following command, replacing "your-server" with the ID of your server. +Ensure your Instance is powered off and then run the following command, replacing `` with the ID of your server. -`scw instance server delete your-server` +`scw instance server delete ` -You will see the following output: +You will see an output similar to the following example: ``` -successfully deleted volume ubuntu_20.04_focal_fossa:volume-0 (20 GB l_ssd) +successfully deleted volume (- sbs_volume) +successfully deleted volume (- sbs_volume) +✅ Success. ``` diff --git a/pages/instances/api-cli/migrating-instances.mdx b/pages/instances/api-cli/migrating-instances.mdx index 114eac3c6d..a3f120ea72 100644 --- a/pages/instances/api-cli/migrating-instances.mdx +++ b/pages/instances/api-cli/migrating-instances.mdx @@ -90,7 +90,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 (`sbs_volume`) without relying on local SSD storage, the downgrade can be performed without any issues. Output: @@ -113,7 +113,7 @@ To do so, you need the Instance’s ID and a valid API key. "root_volume":{ "id":"30e9c843-1cdb-4bd4-96f7-cac26051eeaf", "name":"Ubuntu 22.04 Jammy Jellyfish", - "volume_type":"b_ssd", + "volume_type":"sbs_volume", "size":10000000000 }, [...] diff --git a/pages/instances/api-cli/snapshot-import-export-feature.mdx b/pages/instances/api-cli/snapshot-import-export-feature.mdx index 11d9a180e1..c8dec84288 100644 --- a/pages/instances/api-cli/snapshot-import-export-feature.mdx +++ b/pages/instances/api-cli/snapshot-import-export-feature.mdx @@ -60,7 +60,7 @@ More information on the QCOW2 file format, and how to use it can be found in the "parent_volume": { "id": "9e17baf7-1316-490b-964f-dd76ac7f5e93", "name": "", - "type": "sbs_5k", + "type": "sbs_volume", "status": "in_use" }, "size": 10000000000, diff --git a/pages/instances/how-to/create-an-instance.mdx b/pages/instances/how-to/create-an-instance.mdx index 981a1ce53a..23d07cfe25 100644 --- a/pages/instances/how-to/create-an-instance.mdx +++ b/pages/instances/how-to/create-an-instance.mdx @@ -177,7 +177,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 label, e.g. `ubuntu_noble` which is the label for the Ubuntu 24.04 Noble Numbat image. | | 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 (`sbs_5k` or `sbs_10k`), 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"`, `sbs_5k`, or `"sbs_15k"`). 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 (`sbs_volume` or `sbs_10k`), 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"`, `sbs_volume`, or `"sbs_15k"`). 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). | 4. Use the following curl command, replacing the payload with the one you specified in step 2, to create your Instance. diff --git a/pages/instances/how-to/create-image-from-snapshot.mdx b/pages/instances/how-to/create-image-from-snapshot.mdx index 0223fb1341..4217df327d 100644 --- a/pages/instances/how-to/create-image-from-snapshot.mdx +++ b/pages/instances/how-to/create-image-from-snapshot.mdx @@ -93,6 +93,6 @@ curl --location "https://api.scaleway.com/instance/v1/zones/$SCW_AVAILABILITY_ZO Supported volume IDs include: - Local Storage volumes (`l_ssd`) - Block Storage Low Latency volumes (`sbs`) - - Block Storage legacy (`sbs_5k`) volumes (deprecated). + - Block Storage legacy (`sbs_volume`) volumes (deprecated). diff --git a/pages/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx b/pages/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx index 232a6c5db9..f2782a41f7 100644 --- a/pages/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx +++ b/pages/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx @@ -1,7 +1,7 @@ --- title: How to migrate existing volumes and snapshots to Scaleway's new Block Storage management description: Learn how to migrate your existing Block Storage volumes and snapshots to Scaleway's Block Storage management. -tags: instance snapshot volume sbs_5k sbs_15k sbs +tags: instance snapshot volume sbs_volume sbs_15k sbs dates: validation: 2025-07-21 posted: 2024-08-07 diff --git a/pages/instances/reference-content/identify-devices.mdx b/pages/instances/reference-content/identify-devices.mdx index 006fb5ce6c..5f1f8a503d 100644 --- a/pages/instances/reference-content/identify-devices.mdx +++ b/pages/instances/reference-content/identify-devices.mdx @@ -15,9 +15,9 @@ This guide aims to provide tips to help you stably identify devices on a Linux h ## Identifying Instance Block Storage volumes (sbs) -Instance Block Storage (`sbs_5k` or `sbs_15k`) volumes are connected to the Instance as SCSI disks. They will therefore appear as devices handled by the sd driver in the dev file system, i.e. as `/dev/sd{a,b,c...}` devices. +Instance Block Storage volumes are connected to the Instance as SCSI disks. They will therefore appear as devices handled by the sd driver in the dev file system, 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 (`sbs_5k`) volumes have the vendor name `SCW`, the model/product name `sbs`, 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 (`sbs_volume`) volumes have the vendor name `SCW`, the model/product name `sbs`, 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: diff --git a/pages/instances/reference-content/moving-instances-between-az-and-projects.mdx b/pages/instances/reference-content/moving-instances-between-az-and-projects.mdx index c16248a863..a58d5a2c19 100644 --- a/pages/instances/reference-content/moving-instances-between-az-and-projects.mdx +++ b/pages/instances/reference-content/moving-instances-between-az-and-projects.mdx @@ -111,7 +111,7 @@ scw instance server create image=none root-volume=block: type= zone= From 259ba95adb46c56e6dbd6a8b58c354cb82f70c62 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Thu, 25 Sep 2025 16:39:56 +0200 Subject: [PATCH 05/10] docs(ins): update content --- ...creating-managing-instances-with-cliv2.mdx | 130 ++++++++++-------- .../reference-content/identify-devices.mdx | 2 +- 2 files changed, 71 insertions(+), 61 deletions(-) diff --git a/pages/instances/api-cli/creating-managing-instances-with-cliv2.mdx b/pages/instances/api-cli/creating-managing-instances-with-cliv2.mdx index 72ff3a39c8..1a51ae3023 100644 --- a/pages/instances/api-cli/creating-managing-instances-with-cliv2.mdx +++ b/pages/instances/api-cli/creating-managing-instances-with-cliv2.mdx @@ -3,7 +3,7 @@ title: Creating and managing an Instance with CLI (v2) description: This page explains how to create and manage a Scaleway Instance with CLI (v2) tags: instance create manage cli cli-v2 scw dates: - validation: 2025-09-11 + validation: 2025-09-25 posted: 2021-08-05 --- import Requirements from '@macros/iam/requirements.mdx' @@ -86,79 +86,89 @@ Scaleway Instances provide you with resources to develop, test code and deploy y 1. Type the following command in your terminal to obtain a local-image UUID: - `scw marketplace image get label=ubuntu_focal` + `scw marketplace image get label=ubuntu_noble` - A list of local-images UUIDs from marketplace images displays: + Details of the image as well as its ID are displayed: ``` Image: - Label ubuntu_focal - Name Ubuntu 20.04 Focal Fossa - ModificationDate 3 months ago - CreationDate 2 years ago - Description Ubuntu is the ideal distribution for scale-out computing, Ubuntu Server helps you make the most of your infrastructure. - - Local Images: - ID ZONE ARCH - 401a8e7b-f215-49b5-af8d-e39d9efff24c fr-par-2 x86_64 - 42e3c57b-f907-4685-8a6a-f016445d867a pl-waw-1 x86_64 - 9a40a4cd-87bb-410a-86a2-39af87d12667 fr-par-2 x86_64 - 91edfd06-3eb7-44ad-a903-be54363135a7 pl-waw-1 x86_64 - 70c3e86b-918d-42bd-af7d-e6be485d3f8b fr-par-1 x86_64 - 223b6d78-1aa4-4234-b8ce-e5d39e762ef3 nl-ams-1 x86_64 - 87b79530-0bf4-46da-beeb-f6dc950ab225 fr-par-3 x86_64 - dcd8d994-b859-4e9e-aa91-2ceca41663fb nl-ams-1 x86_64 - ff48b73a-097d-4685-b996-d3ebe50636ea fr-par-1 x86_64 + ID 607b12c2-685d-45f7-905f-57bc23863834 + Label ubuntu_noble + Name Ubuntu 24.04 Noble Numbat + UpdatedAt 1 week ago + CreatedAt 1 year ago + Description Ubuntu is the ideal distribution for scale-out computing, Ubuntu Server helps you make the most of your infrastructure. ``` 2. Run the following command to create an Instance: - `scw instance server create zone=xx-xxx-x image=ubuntu_focal` + `scw instance server create zone=fr-par-1 image=ubuntu_noble type=DEV1-S` - Replace `xx-xxx-x` with the Availability Zone you want to create your Instance in. If you want your Availability Zone to be France, Paris 1, for example, use `fr-par-1`. Refer to our [documentation](/instances/concepts/#availability-zone) for more information about Availability Zones. + Replace `fr-par-1` with the Availability Zone you want to create your Instance in. If you want your Availability Zone to be France, Paris 1, for example, use `fr-par-1`. Refer to our [documentation](/instances/concepts/#availability-zone) for more information about Availability Zones. An output similar to the following should display: ``` - ID 12345678-1234-1234-4321-123456789123 - Name cli-srv-naughty-stonebraker - Organization 12345678-1234-1234-4321-123456789123 - Project 12345678-1234-1234-4321-123456789123 - AllowedActions.0 poweron - AllowedActions.1 backup - CommercialType DEV1-S - CreationDate now - DynamicIPRequired false - EnableIPv6 false - Hostname cli-srv-naughty-stonebraker - Image.ID 12345678-1234-1234-4321-123456789123 - Image.Name Ubuntu 20.04 Focal Fossa - Image.Arch x86_64 - Image.CreationDate 4 months ago - Image.ModificationDate 4 months ago - Image.ExtraVolumes 0 - Image.FromServer - - Image.Organization 12345678-1234-1234-4321-123456789123 - Image.Public true - Image.RootVolume 12345678-1234-1234-4321-123456789123 - Image.State available - Image.Project 12345678-1234-1234-4321-123456789123 - Image.Zone fr-par-2 - Protected false - PublicIP.ID 12345678-1234-1234-4321-123456789123 - PublicIP.Address 51.159.163.11 - PublicIP.Dynamic false - ModificationDate now - State archived - Bootscript x86_64 mainline 4.4.230 rev1 - BootType local - Volumes 1 - SecurityGroup.ID 12345678-1234-1234-4321-123456789123 - SecurityGroup.Name Default security group - StateDetail - - Arch x86_64 - Zone fr-par-2 + ID 12345678-1234-1234-4321-123456789123 + Name cli-srv-romantic-einstein + Organization 12345678-1234-1234-4321-123456789123 + Project 12345678-1234-1234-4321-123456789123 + AllowedActions.0 poweron + AllowedActions.1 backup + CommercialType DEV1-S + CreationDate 1 second ago + DynamicIPRequired true + RoutedIPEnabled true + EnableIPv6 false + Hostname cli-srv-romantic-einstein + Image.ID 12345678-1234-1234-4321-123456789123 + Image.Name Ubuntu 24.04 Noble Numbat + Image.Arch x86_64 + Image.CreationDate 1 week ago + Image.ModificationDate 1 week ago + Image.ExtraVolumes 0 + Image.FromServer - + Image.Organization 12345678-1234-1234-4321-123456789123 + Image.Public true + Image.RootVolume 12345678-1234-1234-4321-123456789123 + Image.State available + Image.Project 12345678-1234-1234-4321-123456789123 + Image.Zone fr-par-1 + Protected false + PublicIP.ID 12345678-1234-1234-4321-123456789123 + PublicIP.Address 51.158.x.y + PublicIP.Gateway 62.210.0.1 + PublicIP.Netmask 32 + PublicIP.Family inet + PublicIP.Dynamic false + PublicIP.ProvisioningMode dhcp + PublicIP.IpamID 12345678-1234-1234-4321-123456789123 + PublicIP.State attached + PublicIPs.0.ID 12345678-1234-1234-4321-123456789123 + PublicIPs.0.Address 51.158.x.y + PublicIPs.0.Gateway 62.210.0.1 + PublicIPs.0.Netmask 32 + PublicIPs.0.Family inet + PublicIPs.0.Dynamic false + PublicIPs.0.ProvisioningMode dhcp + PublicIPs.0.IpamID 12345678-1234-1234-4321-123456789123 + PublicIPs.0.State attached + MacAddress de:00:00:ca:58:55 + ModificationDate 1 second ago + State archived + BootType local + Volumes.0.ID 12345678-1234-1234-4321-123456789123 + Volumes.0.VolumeType sbs_volume + Volumes.0.State available + Volumes.0.Boot false + Volumes.0.Zone fr-par-1 + SecurityGroup.ID 12345678-1234-1234-4321-123456789123 + SecurityGroup.Name Base group + StateDetail - + Arch x86_64 + Zone fr-par-1 + EndOfService false ``` ## Creating an Instance local volume diff --git a/pages/instances/reference-content/identify-devices.mdx b/pages/instances/reference-content/identify-devices.mdx index 5f1f8a503d..606edf3849 100644 --- a/pages/instances/reference-content/identify-devices.mdx +++ b/pages/instances/reference-content/identify-devices.mdx @@ -3,7 +3,7 @@ title: Identifiying devices of a Scaleway Instance description: This page explains how to identify devices on a Scaleway Instance tags: instance dates: - validation: 2025-03-25 + validation: 2025-09-25 posted: 2024-03-15 --- From 7244ecc082181d980927bc0ae438b31bf27e2eaa Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Thu, 25 Sep 2025 16:43:51 +0200 Subject: [PATCH 06/10] docs(ins): update docs --- pages/instances/how-to/create-an-instance.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/instances/how-to/create-an-instance.mdx b/pages/instances/how-to/create-an-instance.mdx index 23d07cfe25..3f1f3efdb6 100644 --- a/pages/instances/how-to/create-an-instance.mdx +++ b/pages/instances/how-to/create-an-instance.mdx @@ -177,7 +177,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 label, e.g. `ubuntu_noble` which is the label for the Ubuntu 24.04 Noble Numbat image. | | 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 (`sbs_volume` or `sbs_10k`), 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"`, `sbs_volume`, or `"sbs_15k"`). 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 (`sbs_volume`), 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"`, `sbs_volume`, or `"sbs_15k"`). 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). | 4. Use the following curl command, replacing the payload with the one you specified in step 2, to create your Instance. From a98985a2cc879988fcbbd059b1058e5df3115c7b Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Thu, 25 Sep 2025 16:48:19 +0200 Subject: [PATCH 07/10] docs(ins): fix typo --- pages/instances/how-to/create-an-instance.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/instances/how-to/create-an-instance.mdx b/pages/instances/how-to/create-an-instance.mdx index 3f1f3efdb6..84b89d021b 100644 --- a/pages/instances/how-to/create-an-instance.mdx +++ b/pages/instances/how-to/create-an-instance.mdx @@ -177,7 +177,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 label, e.g. `ubuntu_noble` which is the label for the Ubuntu 24.04 Noble Numbat image. | | 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 (`sbs_volume`), 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"`, `sbs_volume`, or `"sbs_15k"`). 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 (`sbs_volume`), 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 `sbs_volume`). 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). | 4. Use the following curl command, replacing the payload with the one you specified in step 2, to create your Instance. From df4dbfc0ab9d55a9eeeb3911ddf17309d915b446 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Thu, 25 Sep 2025 17:21:53 +0200 Subject: [PATCH 08/10] docs(ins): update docs --- menu/navigation.json | 4 ---- .../how-to/migrate-volumes-snapshots-to-sbs.mdx | 12 ------------ 2 files changed, 16 deletions(-) delete mode 100644 pages/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx diff --git a/menu/navigation.json b/menu/navigation.json index 67a128bb77..8330f31604 100644 --- a/menu/navigation.json +++ b/menu/navigation.json @@ -1494,10 +1494,6 @@ "label": "Create an image from a snapshot", "slug": "create-image-from-snapshot" }, - { - "label": "Migrate volumes and snapshots to Scaleway SBS", - "slug": "migrate-volumes-snapshots-to-sbs" - }, { "label": "Resize Instances", "slug": "resize-instances" diff --git a/pages/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx b/pages/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx deleted file mode 100644 index f2782a41f7..0000000000 --- a/pages/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: How to migrate existing volumes and snapshots to Scaleway's new Block Storage management -description: Learn how to migrate your existing Block Storage volumes and snapshots to Scaleway's Block Storage management. -tags: instance snapshot volume sbs_volume sbs_15k sbs -dates: - validation: 2025-07-21 - posted: 2024-08-07 ---- -import HowToMigrateToSbs from '@macros/compute/how-to-migrate-to-sbs.mdx' - - - \ No newline at end of file From f7d3fe93084bea71aaf0b0140c212c1edee4233b Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Thu, 25 Sep 2025 17:33:13 +0200 Subject: [PATCH 09/10] Update pages/instances/how-to/create-an-instance.mdx Co-authored-by: Jessica <113192637+jcirinosclwy@users.noreply.github.com> --- pages/instances/how-to/create-an-instance.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/instances/how-to/create-an-instance.mdx b/pages/instances/how-to/create-an-instance.mdx index 84b89d021b..20c245cd55 100644 --- a/pages/instances/how-to/create-an-instance.mdx +++ b/pages/instances/how-to/create-an-instance.mdx @@ -177,7 +177,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 label, e.g. `ubuntu_noble` which is the label for the Ubuntu 24.04 Noble Numbat image. | | 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 (`sbs_volume`), 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 `sbs_volume`). 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 (`sbs_volume`), 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 `sbs_volume`). 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). | 4. Use the following curl command, replacing the payload with the one you specified in step 2, to create your Instance. From 81305a4f51dadf669b8ba0308e9c9660286dfbfe Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Fri, 26 Sep 2025 16:50:36 +0200 Subject: [PATCH 10/10] Apply suggestions from code review Co-authored-by: cgilb-scaleway --- pages/instances/how-to/create-image-from-snapshot.mdx | 3 +-- pages/instances/reference-content/identify-devices.mdx | 6 +++--- 2 files changed, 4 insertions(+), 5 deletions(-) diff --git a/pages/instances/how-to/create-image-from-snapshot.mdx b/pages/instances/how-to/create-image-from-snapshot.mdx index 4217df327d..7e40d683f0 100644 --- a/pages/instances/how-to/create-image-from-snapshot.mdx +++ b/pages/instances/how-to/create-image-from-snapshot.mdx @@ -92,7 +92,6 @@ curl --location "https://api.scaleway.com/instance/v1/zones/$SCW_AVAILABILITY_ZO Supported volume IDs include: - Local Storage volumes (`l_ssd`) - - Block Storage Low Latency volumes (`sbs`) - - Block Storage legacy (`sbs_volume`) volumes (deprecated). + - Block Storage Low Latency volumes (`sbs_volume`) diff --git a/pages/instances/reference-content/identify-devices.mdx b/pages/instances/reference-content/identify-devices.mdx index 606edf3849..8a6db13d12 100644 --- a/pages/instances/reference-content/identify-devices.mdx +++ b/pages/instances/reference-content/identify-devices.mdx @@ -13,11 +13,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 stably identify devices on a Linux host. -## Identifying Instance Block Storage volumes (sbs) +## Identifying Block Storage volumes (sbs) -Instance Block Storage volumes are connected to the Instance as SCSI disks. They will therefore appear as devices handled by the sd driver in the dev file system, i.e. as `/dev/sd{a,b,c...}` devices. +Block Storage volumes (`sbs_volume`) are connected to the Instance as SCSI disks. They will therefore appear as devices handled by the sd driver in the dev file system, 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 (`sbs_volume`) volumes have the vendor name `SCW`, the model/product name `sbs`, 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. Block Storage (`sbs_volume`) volumes have the vendor name `SCW`, the model/product name `sbs`, 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: