Skip to content

Commit 3f85956

Browse files
committed
docs(bls): feedback
1 parent f74aa09 commit 3f85956

File tree

4 files changed

+44
-33
lines changed

4 files changed

+44
-33
lines changed

faq/blockstorage.mdx

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -56,16 +56,18 @@ Block Storage volumes are compatible with [Scaleway Instances](/compute/instance
5656

5757
## How can I convert a Block Storage legacy volume into a Block Storage Low Latency volume?
5858

59-
For better performance, you can convert your Block Storage legacy volumes into Block Storage Low Latency volumes.
59+
Currently, there is no direct way to change the storage class of a volume while preserving its ID.
6060

61-
To convert your volume you need to:
61+
However, you can use the snapshot export/import feature as a temporary solution to transition a Block Storage legacy volume into a Block Storage Low Latency volume.
6262

63-
- Export the data: copy or back up the data from the Block storage legacy volume to an external location or intermediary storage (e.g., another temporary volume).
63+
<Message type="important">
64+
The process below requires manual intervention and **does not preserve the original volume's ID**.
65+
While this approach allows you to transition to a Block Storage Low Latency volume, it is only a workaround.
66+
</Message>
6467

65-
- Create a Block Storage Low Latency volume
66-
67-
- Import the data: restore or transfer the data from the backup or intermediary storage into the newly created volume.
68+
1. [Export a snapshot of your Block Storage legacy volume](/compute/instances/api-cli/snapshot-import-export-feature/#exporting-snapshots).
69+
2. [Import the snapshot into a new Low Latency volume](/compute/instances/api-cli/snapshot-import-export-feature/#importing-snapshots).
6870

6971
Find out how to [migrate your Block Storage legacy volumes and snapshots](/compute/instances/how-to/migrate-volumes-snapshots-to-sbs/) from the Instance API to the Block Storage API.
7072

71-
Find out about the [advantages of migrating the management of your volumes and snapshots](advantages-migrating-to-sbs) from the Instance API to the Block Storage API.
73+
Find out about the [advantages of migrating the management of your volumes and snapshots](/storage/block/reference-content/advantages-migrating-to-sbs) from the Instance API to the Block Storage API.

storage/block/api-cli/identifying-volume-snapshot-api.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -257,7 +257,7 @@ An output similar to the following should display:
257257
```bash
258258
scw instance volume list
259259
```
260-
An output similar to the following whould display:
260+
An output similar to the following should display:
261261
```
262262
ID STATE SERVER ID
263263
b582c548-6dc0-4e77-bb93-9615b9baa380 available a4138186-f362-41b2-adc2-c46a2e1a46b7

storage/block/how-to/identify-volume-snapshot-type.mdx

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -41,5 +41,4 @@ This page shows you how to identify the API that manages your volumes and snapsh
4141
3. Leave the **Block Storage API** filter in the drop-down or select **Instance API** to display either your snapshots managed by the Block Storage API, or the Instance API.
4242
4. Click the **Snapshot type** drop-down and select the snapshot type(s) to filter for.
4343
5. Optionally, click the <Icon name="more" /> icon next to a specific snapshot to display its information page, and verify the type next to the **Type** field.
44-
6. Click **Clear filters** once you are done.
45-
44+
6. Click **Clear filters** once you are done.

storage/block/reference-content/advantages-migrating-to-sbs.mdx

Lines changed: 33 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -15,49 +15,59 @@ categories:
1515

1616
## Transitioning from the Instance API to the Block Storage API for volume and snapshot management
1717

18-
Scaleway is transitioning the management of all Block Storage legacy volumes and snapshots from the [Instance API](https://www.scaleway.com/en/developers/api/instance/) to the [Block Storage API](https://www.scaleway.com/en/developers/api/block/). All Block Storage volumes and snapshots created via the [Scaleway console](https://console.scaleway.com) will no longer be available from the [Compute section](https://console.scaleway.com/instance/), but from the [Storage section](https://console.scaleway.com/block-storage).
18+
Scaleway is transitioning the management of all Block Storage legacy volumes and snapshots from the [Instance API](https://www.scaleway.com/en/developers/api/instance/) to the [Block Storage API](https://www.scaleway.com/en/developers/api/block/). All Block Storage volumes and snapshots created via the [Scaleway console](https://console.scaleway.com) will no longer be available from the [Compute section](https://console.scaleway.com/instance/) but from the [Storage section](https://console.scaleway.com/block-storage).
1919

20-
This change provides you with enhanced performance and advanced storage capabilities. If you have created volumes and snapshots via the Instance API, we **strongly recommend migrating them to the Block Storage API** to benefit from these improvements.
20+
This change streamlines how storage resources are managed by consolidating them under the Block Storage API, providing enhanced management features and clearer storage class distinctions. If you have created volumes and snapshots via the Instance API, we **strongly recommend transitioning to the Block Storage API** to align with the latest management practices.
2121

2222
Local volumes will remain exclusively supported by the Instance API.
2323

24-
## Key advantages of using the Block Storage API
24+
## Differences between the Instance API and the Block Storage API
2525

26-
By migrating your Block Storage volumes and snapshots to the Block Storage API, you take advantage of the following benefits:
26+
The key differences between the Instance API and the Block Storage API lie in the storage classes they manage, rather than just the APIs themselves. This distinction influences the underlying hardware and performance characteristics of the volumes.
2727

28-
- **Low latency**: volumes managed by the Block Storage API leverage modern hardware, ensuring faster access times and smoother performance.
29-
- **Higher IOPS performance**: benefit from up to 5K IOPS (input/output operations per second) with Block Storage Low Latency volumes and 15K IOPS with higher-tier offerings. These performance improvements are ideal for applications requiring rapid data access and high-speed operations.
28+
### Storage classes
3029

31-
## Differences between volumes managed by the Instance API and the Block Storage API
30+
The Instance API handles only **BSSD (Basic SSD)** volumes.
31+
The Block Storage API supports a broader range of storage classes, including:
3232

33-
Volumes created with the Instance API differ from those created with the Block Storage API in both hardware and performance characteristics:
33+
- **BSSD volumes**
34+
- **Scaleway Block Storage (SBS) 5K IOPS volumes**
35+
- **Scaleway Block Storage (SBS) 15K IOPS volumes**
3436

3537
### Underlying hardware
3638

37-
Instance API volumes are built on **older-generation SSDs**, resulting in **slower performance and have a higher latency**, which may impact the responsiveness of applications.
39+
**BSSD volumes** (managed by both APIs) are built on **older-generation SSDs**, offering reliable performance but with limitations in speed and latency.
3840

39-
Block Storage API volumes are powered by **modern NVMe (Non-Volatile Memory Express) disks**, which are optimized for **high-speed operations**. They also have **advanced hardware** which ensures faster data access and lower latency.
41+
**Scaleway Block Storage 5K and 15K volumes** (managed only by the Block Storage API) are powered by **modern NVMe (Non-Volatile Memory Express) disks**. They are optimized for **low-latency and high-speed operations**.
4042

41-
### Performance
43+
### Performance and latency
4244

43-
Instance API volumes have a **limited performance** due to older SSD technology. They also have a **lower IOPS and slower data processing speed**.
45+
**BSSD volumes**:
4446

45-
Block Storage API volumes benefit from e**nhanced performance with up to 15K IOPS**.
47+
- **Performance**: Limited IOPS and slower data processing speed due to older SSD technology.
48+
- **Latency**: Higher latency, less suitable for applications requiring rapid data retrieval.
4649

47-
### Latency
50+
**Scaleway Block Storage 5K and 15K volumes**:
4851

49-
Instance API volumes have a **higher latency**, making them less suitable for applications requiring quick data retrieval.
52+
- **Performance**: Enhanced performance with up to 5K IOPS (SBS 5K) and 15K IOPS (SBS 15K).
53+
- **Latency**: Lower latency, ideal for workloads demanding rapid and reliable data access.
5054

51-
Block Storage API volumes have a **reduced latency** which ensures faster application response times. They are ideal for workloads requiring rapid and reliable data access.
55+
## Why transition to the Block Storage API?
5256

53-
## Why you should migrate your volumes and snapshot
57+
By transitioning to the Block Storage API, you align with Scaleway's consolidated storage management approach and gain access to advanced storage features and flexibility. While migrating to the Block Storage API does not inherently change the performance of BSSD volumes, you benefit from:
5458

55-
Currently, two APIs manage Block Storage volumes on Scaleway: the Instance API and the Scaleway Block Storage API. Maintaining both APIs for the same product is not sustainable.
59+
- **Unified management**: Simplified volume and snapshot management through a dedicated API.
60+
- **Access to advanced storage classes**: You can create new Scaleway Block Storage 5K or 15K volumes for workloads needing higher performance and lower latency.
61+
- **Ongoing support**: Enhanced support and updates tailored for Block Storage API-managed resources.
5662

57-
Migrating your volumes to the Block Storage API ensures you benefit from:
63+
## Impact on volume names in virtual machines
5864

59-
- The latest in storage technology with NVMe-powered performance
60-
- Improved reliability and scalability for your applications
61-
- Ongoing support and updates tailored for volumes and snapshots managed with the Block Storage API
65+
When transitioning to the Block Storage API, you may notice changes in how volumes are identified in your virtual machines (VMs). For more details on how devices are named and identified, please refer to [this documentation](/compute/instances/reference-content/identify-devices/).
6266

63-
Find out [how to migrate](/compute/instances/how-to/migrate-volumes-snapshots-to-sbs/) your Block Storage legacy volumes to Block Storage Low Latency volumes.
67+
## How to transition
68+
69+
For a step-by-step guide to transitioning your Block Storage legacy volumes to the Block Storage API, refer to [our migration documentation](/compute/instances/how-to/migrate-volumes-snapshots-to-sbs/).
70+
71+
---
72+
73+
This transition ensures Scaleway can continue to provide robust, scalable, and high-performance storage solutions tailored to your needs. If you have questions or need assistance, [contact our support team](https://console.scaleway.com/support/tickets/create).

0 commit comments

Comments
 (0)