docs(ins): update content

Author: bene2k1

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=<generated>]                         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=<generated>]                         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)
   ```
 </Message>
 

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-<uuid>` where `<uuid>` 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-<uuid>` where `<uuid>` 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.