From cb09bc087ff456aab9750965b3cfa4c4c4a9a7b9 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Mon, 13 Jan 2025 17:14:44 +0100 Subject: [PATCH 1/7] feat(ins): add information for eol api --- .../how-to/migrate-volumes-snapshots-to-sbs.mdx | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx b/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx index 516228a992..b30b247d1b 100644 --- a/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx +++ b/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx @@ -28,6 +28,18 @@ This guide offers step-by-step instructions to migrate your volumes and snapshot - If you encounter an error about quota limitations during the migration process, [contact our support team](https://console.scaleway.com/support/tickets/create) for assistance. + + To ensure continued access to managing your volumes, you must [convert](/faq/blockstorage/#how-can-i-convert-a-block-storage-legacy-volume-into-a-block-storage-low-latency-volume) your **unified volumes and snapshots** into either **local** or **Block volumes** before the **end-of-life date of June 2nd, 2024**. After this date, unified volumes and snapshots will no longer be supported by any API. + + ### Key migration deadlines: + - **April 30th:** + - Creation of new unified volumes via the Instance API will be disabled. + - Unified volumes will no longer be supported by the Block Storage API. + - **June 2nd:** + - Unified volumes and snapshots can no longer be managed via any API. Existing unified resources must be converted by this date to avoid loss of manageability. + + + - A Scaleway account logged into the [console](https://console.scaleway.com) @@ -223,4 +235,4 @@ This guide offers step-by-step instructions to migrate your volumes and snapshot To learn more about managing your migrated Block Storage volumes and snapshots from the Scaleway console, refer to the [Block Storage Quickstart Guide](/storage/block/quickstart/). Additionally, you can explore advanced features using the [Scaleway Block Storage API](https://www.scaleway.com/en/developers/api/block/). -If you encounter any issues during migration, contact [Scaleway's support team](https://console.scaleway.com/support/tickets) for assistance. \ No newline at end of file +If you encounter any issues during migration, contact [Scaleway's support team](https://console.scaleway.com/support/tickets) for assistance. From 0a0356ee6cf16b81cc4381d9b2c10c67de2296b2 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Tue, 14 Jan 2025 10:15:39 +0100 Subject: [PATCH 2/7] feat(ins): added migration method --- .../migrate-volumes-snapshots-to-sbs.mdx | 64 ++++++++++++++----- 1 file changed, 48 insertions(+), 16 deletions(-) diff --git a/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx b/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx index b30b247d1b..6232c68e77 100644 --- a/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx +++ b/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx @@ -7,7 +7,7 @@ content: paragraph: This guide provides step-by-step instructions to help you migrate your existing Block Storage volumes and snapshots to Scaleway's new Block Storage management system. tags: instance snapshot volume b_ssd sbs dates: - validation: 2024-11-15 + validation: 2025-01-14 posted: 2024-08-07 categories: - compute @@ -15,37 +15,57 @@ categories: To enhance performance and reliability, Scaleway is transitioning the management of Block Storage volumes and snapshots from Compute to Storage. -The migration process ensures that the characteristics of your volumes and snapshots remain unchanged, even for volumes attached to running Instances. +To facilitate the transition to Scaleway's new Block Storage management, two main approaches for migrating your volumes exist, each with its unique benefits and drawbacks: -After migration, these resources will be managed under [Storage](/storage/block/quickstart/) instead of Compute. +- [Using the Instance API/CLI migration endpoint (Plan and Apply)](#migrating-using-the-migration-endpoint-of-the-instances-api-cli): + - **Advantage:** Migration can occur without service interruption, as the volume remains attached to the running Instance and fully accessible. + - **Drawback:** Only the volume's representation is migrated to the SBS API; the data itself doesn't move. This means the migrated volume will not benefit from low latency or higher IOPS, as it retains the original `b_ssd` characteristics. + +- [Using the snapshot export/import features](#migrating-using-the-snapshot-exportimport-features): + - **Advantage:** The migrated volume will fully support low latency, and it is possible to modify the IOPS up to 15k. All existing data of the old volume will be copied to the new Block Storage Low Latency volume. + - **Drawback:** A snapshot must be manually created, exported, and then imported and attached to the Instance which may require downtime. + +Each method caters to different needs, balancing uninterrupted service against achieving maximum performance benefits. After migration, these resources will be managed under [Storage](/storage/block/quickstart/) instead of Compute. + +## Comparison of migration methods + +| Migration Method | Advantage | Drawback | +|--------------------------------|-----------------------------------------------|---------------------------------------------| +| Instance API/CLI migration | No service interruption, volume remains accessible | Data characteristics remain the same; no performance boost | +| Snapshot export/import | Full support for low latency and customizable IOPS | Requires downtime; manual snapshot handling | -During migration, unified snapshots will be converted into [Block Storage Low Latency](/storage/block/) snapshots and removed from Compute. If a unified snapshot is part of an image, it will be replaced by the corresponding Block Storage Low Latency snapshot. This guide offers step-by-step instructions to migrate your volumes and snapshots using either the [Scaleway Command Line Interface (CLI)](/developer-tools/scaleway-cli/quickstart/) tool (recommended) or the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-volumes-migrate-a-volume-andor-snapshots-to-sbs-scaleway-block-storage). +Alternatively, you can use the [snapshot export/import feature](/compute/instances/api-cli/snapshot-import-export-feature/) to migrate your unified volumes and snapshots to Block Storage Low Latency volumes. - - - The easiest way to migrate your Block Storage volumes and snapshots is by using the [Scaleway Command Line Interface (CLI)](/developer-tools/scaleway-cli/quickstart/) tool + + +- A Scaleway account logged into the [console](https://console.scaleway.com) +- An [Instance](/compute/instances/how-to/create-an-instance/) using [Block Storage volumes](/storage/block/how-to/create-a-volume/) + + + - The easiest way to migrate your Block Storage volumes and snapshots is by using the [Scaleway Command Line Interface (CLI)](/developer-tools/scaleway-cli/quickstart/) tool. - If you encounter an error about quota limitations during the migration process, [contact our support team](https://console.scaleway.com/support/tickets/create) for assistance. - To ensure continued access to managing your volumes, you must [convert](/faq/blockstorage/#how-can-i-convert-a-block-storage-legacy-volume-into-a-block-storage-low-latency-volume) your **unified volumes and snapshots** into either **local** or **Block volumes** before the **end-of-life date of June 2nd, 2024**. After this date, unified volumes and snapshots will no longer be supported by any API. + To ensure continued access to managing your volumes, you must convert your **unified volumes and snapshots** into either **local** or **Block volumes** before the **end-of-life date of June 2nd, 2025**. After this date, unified volumes and snapshots will no longer be supported by any API. - ### Key migration deadlines: - - **April 30th:** + #### Key migration deadlines: + - April 30th, 2025: - Creation of new unified volumes via the Instance API will be disabled. - Unified volumes will no longer be supported by the Block Storage API. - - **June 2nd:** + - June 2nd, 2025: - Unified volumes and snapshots can no longer be managed via any API. Existing unified resources must be converted by this date to avoid loss of manageability. +## Migrating using the Instance API/CLI migration endpoint (Plan and Apply): - - -- A Scaleway account logged into the [console](https://console.scaleway.com) -- An [Instance](/compute/instances/how-to/create-an-instance/) using [Block Storage volumes](/storage/block/how-to/create-a-volume/) + + During migration, unified snapshots will be converted into [Block Storage](/storage/block/) snapshots and removed from Compute. If a unified snapshot is part of an image, it will be replaced by the corresponding Block Storage snapshot. + -## Migrating an existing Block Storage volume to Scaleway Block Storage management +### Migrating an existing Block Storage volume to Scaleway Block Storage management This process applies only to Block SSD (`b_ssd`) volumes. @@ -138,7 +158,7 @@ This guide offers step-by-step instructions to migrate your volumes and snapshot -## Migrating an existing Block Storage snapshot to Scaleway Block Storage management +### Migrating an existing Block Storage snapshot to Scaleway Block Storage management This process applies to Block SSD (`b_ssd`) or Unified (`unified`) snapshots. @@ -231,6 +251,18 @@ This guide offers step-by-step instructions to migrate your volumes and snapshot +## Migrating using the snapshot import/export features + +To convert your unified volumes and snapshots you can use the snapshot export/import feature as an alternative solution to transition a Block Storage legacy volume into a Block Storage Low Latency volume. + + + The process below requires manual intervention and **does not preserve the original volume’s ID**. While this approach allows you to transition to a Block Storage Low Latency volume, it is only a workaround. + + + Steps: + 1. [Export a snapshot of your unified volume](https://www.scaleway.com/en/docs/compute/instances/api-cli/snapshot-import-export-feature/#exporting-snapshots). + 2. [Import the snapshot into a new local or Block volume](https://www.scaleway.com/en/docs/compute/instances/api-cli/snapshot-import-export-feature/#importing-snapshots). + ## Going further To learn more about managing your migrated Block Storage volumes and snapshots from the Scaleway console, refer to the [Block Storage Quickstart Guide](/storage/block/quickstart/). Additionally, you can explore advanced features using the [Scaleway Block Storage API](https://www.scaleway.com/en/developers/api/block/). From a2820ae07b397d9b201e020b2004833aa6257cf6 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Tue, 14 Jan 2025 10:36:15 +0100 Subject: [PATCH 3/7] Apply suggestions from code review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Pierre Muller <46796678+pierre-muller@users.noreply.github.com> Co-authored-by: Néda <87707325+nerda-codes@users.noreply.github.com> --- .../instances/how-to/migrate-volumes-snapshots-to-sbs.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx b/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx index 8fec1cb8db..ea120e77d9 100644 --- a/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx +++ b/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx @@ -56,7 +56,7 @@ Alternatively, you can use the [snapshot export/import feature](/compute/instanc #### Key migration deadlines: - April 30th, 2025: - Creation of new unified volumes via the Instance API will be disabled. - - Unified volumes will no longer be supported by the Block Storage API. + - Unified volumes will no longer be supported by the Instance API. - June 2nd, 2025: - Unified volumes and snapshots can no longer be managed via any API. Existing unified resources must be converted by this date to avoid loss of manageability. @@ -262,8 +262,8 @@ To convert your unified volumes and snapshots you can use the snapshot export/im Steps: - 1. [Export a snapshot of your unified volume](https://www.scaleway.com/en/docs/compute/instances/api-cli/snapshot-import-export-feature/#exporting-snapshots). - 2. [Import the snapshot into a new local or Block volume](https://www.scaleway.com/en/docs/compute/instances/api-cli/snapshot-import-export-feature/#importing-snapshots). + 1. [Export a snapshot of your unified volume](/compute/instances/api-cli/snapshot-import-export-feature/#exporting-snapshots). + 2. [Import the snapshot into a new local or Block volume](/compute/instances/api-cli/snapshot-import-export-feature/#importing-snapshots). ## Going further From 80dda56b202d18e68ff77242d39a92f05f583a08 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Tue, 14 Jan 2025 10:40:29 +0100 Subject: [PATCH 4/7] feat(ins): fix anchor --- compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx b/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx index ea120e77d9..8a3ad9a12f 100644 --- a/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx +++ b/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx @@ -17,7 +17,7 @@ To enhance performance and reliability, Scaleway is transitioning the management To facilitate the transition to Scaleway's new Block Storage management, two main approaches for migrating your volumes exist, each with its unique benefits and drawbacks: -- [Using the Instance API/CLI migration endpoint (Plan and Apply)](#migrating-using-the-migration-endpoint-of-the-instances-api-cli): +- [Using the Instance API/CLI migration endpoint (Plan and Apply)](#migrating-using-the-instance-apicli-migration-endpoint-plan-and-apply): - **Advantage:** Migration can occur without service interruption, as the volume remains attached to the running Instance and fully accessible. - **Drawback:** Only the volume's representation is migrated to the SBS API; the data itself doesn't move. This means the migrated volume will not benefit from low latency or higher IOPS, as it retains the original `b_ssd` characteristics. @@ -253,7 +253,7 @@ Alternatively, you can use the [snapshot export/import feature](/compute/instanc -## Migrating using the snapshot import/export features +## Migrating using the snapshot export/import features To convert your unified volumes and snapshots you can use the snapshot export/import feature as an alternative solution to transition a Block Storage legacy volume into a Block Storage Low Latency volume. From f39c6cb4e55cfbaeda9f005a8c8ff72ec34d5423 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Tue, 14 Jan 2025 14:02:32 +0100 Subject: [PATCH 5/7] fix(ins): fix sbs docs --- .../instances/how-to/migrate-volumes-snapshots-to-sbs.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx b/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx index 8a3ad9a12f..a8b66710f1 100644 --- a/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx +++ b/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx @@ -19,12 +19,12 @@ To facilitate the transition to Scaleway's new Block Storage management, two mai - [Using the Instance API/CLI migration endpoint (Plan and Apply)](#migrating-using-the-instance-apicli-migration-endpoint-plan-and-apply): - **Advantage:** Migration can occur without service interruption, as the volume remains attached to the running Instance and fully accessible. - - **Drawback:** Only the volume's representation is migrated to the SBS API; the data itself doesn't move. This means the migrated volume will not benefit from low latency or higher IOPS, as it retains the original `b_ssd` characteristics. + - **Drawback:** Only the volume's representation is migrated to the SBS API; the data itself does not move. This means the migrated volume will not benefit from low latency or higher IOPS, as it retains the original `b_ssd` characteristics. - [Using the snapshot export/import features](#migrating-using-the-snapshot-exportimport-features): - **Advantage:** The migrated volume will fully support low latency, and it is possible to modify the IOPS up to 15k. All existing data of the old volume will be copied to the new Block Storage Low Latency volume. - - **Drawback:** A snapshot must be manually created, exported, and then imported and attached to the Instance which may require downtime. - + - **Drawback:** A snapshot must be manually created, exported, and imported. After importing, the snapshot must be converted into a volume, which then needs to be attached to the instance. This process may require downtime. + Each method caters to different needs, balancing uninterrupted service against achieving maximum performance benefits. After migration, these resources will be managed under [Storage](/storage/block/quickstart/) instead of Compute. ## Comparison of migration methods @@ -263,7 +263,7 @@ To convert your unified volumes and snapshots you can use the snapshot export/im Steps: 1. [Export a snapshot of your unified volume](/compute/instances/api-cli/snapshot-import-export-feature/#exporting-snapshots). - 2. [Import the snapshot into a new local or Block volume](/compute/instances/api-cli/snapshot-import-export-feature/#importing-snapshots). + 2. [Import the snapshot into a new local or Block volume](https://www.scaleway.com/en/developers/api/block/#path-snapshot-import-a-snapshot-from-a-scaleway-object-storage-bucket). ## Going further From 3789f75567a72ea4eb975013f05c1749f6891e65 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Tue, 14 Jan 2025 14:14:47 +0100 Subject: [PATCH 6/7] feat(ins): update link to doc --- faq/blockstorage.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/faq/blockstorage.mdx b/faq/blockstorage.mdx index 2e68b7bc00..075a68e9f1 100644 --- a/faq/blockstorage.mdx +++ b/faq/blockstorage.mdx @@ -66,7 +66,7 @@ However, you can use the snapshot export/import feature as a temporary solution 1. [Export a snapshot of your Block Storage volume](/compute/instances/api-cli/snapshot-import-export-feature/#exporting-snapshots). -2. [Import the snapshot into a new Low Latency volume](/compute/instances/api-cli/snapshot-import-export-feature/#importing-snapshots). +2. [Import the snapshot into a new Low Latency volume](https://www.scaleway.com/en/developers/api/block/#path-snapshot-import-a-snapshot-from-a-scaleway-object-storage-bucket). Find out how to [migrate your Block Storage volumes and snapshots](/compute/instances/how-to/migrate-volumes-snapshots-to-sbs/) from the Instance API to the Block Storage API. From 96c66877508365050b7e78f569f76a3a9e26d278 Mon Sep 17 00:00:00 2001 From: Benedikt Rollik Date: Tue, 14 Jan 2025 14:17:04 +0100 Subject: [PATCH 7/7] Apply suggestions from code review --- compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx b/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx index a8b66710f1..2755860e4c 100644 --- a/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx +++ b/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx @@ -23,7 +23,7 @@ To facilitate the transition to Scaleway's new Block Storage management, two mai - [Using the snapshot export/import features](#migrating-using-the-snapshot-exportimport-features): - **Advantage:** The migrated volume will fully support low latency, and it is possible to modify the IOPS up to 15k. All existing data of the old volume will be copied to the new Block Storage Low Latency volume. - - **Drawback:** A snapshot must be manually created, exported, and imported. After importing, the snapshot must be converted into a volume, which then needs to be attached to the instance. This process may require downtime. + - **Drawback:** A snapshot must be manually created, exported, and imported. After importing, the snapshot must be converted into a volume, which must then be attached to the Instance. This process may require downtime. Each method caters to different needs, balancing uninterrupted service against achieving maximum performance benefits. After migration, these resources will be managed under [Storage](/storage/block/quickstart/) instead of Compute.