feat(block-storage): migration documentation #4131
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nerda-codes
added
the
do not merge
| ```bash | ||
| scw instance volume list | ||
| ``` | ||
| An output similar to the following whould display: |
There was a problem hiding this comment.
Suggested change
| An output similar to the following whould display: | |
| An output similar to the following should display: |
| 4. Click the **Snapshot type** drop-down and select the snapshot type(s) to filter for. | ||
| 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. | ||
| 6. Click **Clear filters** once you are done. | ||
|
|
|
|
||
| ### Underlying hardware | ||
|
|
||
| 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. |
There was a problem hiding this comment.
Suggested change
| 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. | |
| Instance API volumes are built on **older-generation SSDs**, resulting in **slower performance and a higher latency**, which may impact the responsiveness of applications. |
|
|
||
| Instance API volumes have a **limited performance** due to older SSD technology. They also have a **lower IOPS and slower data processing speed**. | ||
|
|
||
| Block Storage API volumes benefit from e**nhanced performance with up to 15K IOPS**. |
There was a problem hiding this comment.
Suggested change
| Block Storage API volumes benefit from e**nhanced performance with up to 15K IOPS**. | |
| Block Storage API volumes benefit from **enhanced performance with up to 15K IOPS**. |
jcirinosclwy
approved these changes
Dec 20, 2024
TC5027
reviewed
Dec 23, 2024
|
|
||
| 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). | ||
|
|
||
| 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. |
There was a problem hiding this comment.
There won't be perf update when migrating API
|
|
||
| By migrating your Block Storage volumes and snapshots to the Block Storage API, you take advantage of the following benefits: | ||
|
|
||
| - **Low latency**: volumes managed by the Block Storage API leverage modern hardware, ensuring faster access times and smoother performance. |
There was a problem hiding this comment.
Instance API handles bssd volumes which will still be bssd volumes behind the SBS/block API
| By migrating your Block Storage volumes and snapshots to the Block Storage API, you take advantage of the following benefits: | ||
|
|
||
| - **Low latency**: volumes managed by the Block Storage API leverage modern hardware, ensuring faster access times and smoother performance. | ||
| - **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. |
There was a problem hiding this comment.
bssd volumes won't be sbs5k or sbs15k volumes when migrating API
|
|
||
| ## Differences between volumes managed by the Instance API and the Block Storage API | ||
|
|
||
| Volumes created with the Instance API differ from those created with the Block Storage API in both hardware and performance characteristics: |
There was a problem hiding this comment.
It's more a storage class diff then an APi diff that explains hw/perf diff
Instance API handles only bssd volumes whereas SBS/block API handles bssd+sbs5k+sbs15k volume
| - Create a Block Storage Low Latency volume | ||
|
|
||
| - Import the data: restore or transfer the data from the backup or intermediary storage into the newly created volume. |
There was a problem hiding this comment.
I find it weird to split the create and import in 2 steps whereas it is actually a single call performing both
Also should we not say this is a temporary/not ideal solution before being effectively able to change the storage class of a volume while preserving its id ?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Documentation to prepare Block Storage migration from v1 to v2 volumes/snapshots