diff --git a/faq/billing.mdx b/faq/billing.mdx index e0cc142e05..5ae056ec56 100644 --- a/faq/billing.mdx +++ b/faq/billing.mdx @@ -23,7 +23,7 @@ Your monthly invoice is calculated at the end of each month and based on your ho For example: The Stardust1-s indicated at €0,0025 excl/hour can be split up as follows: - €0.00198/hour for the IP -- €0.0004/hour for the 10 GB of Local Storage +- €0.0004/hour for the 10 GB of Local NVMe storage - €0.00012/hour for the instance For more information, refer to our dedicated [pricing page](https://www.scaleway.com/en/pricing/). diff --git a/faq/blockstorage.mdx b/faq/blockstorage.mdx index 1d2ad53fe4..a07df79578 100644 --- a/faq/blockstorage.mdx +++ b/faq/blockstorage.mdx @@ -1,7 +1,7 @@ --- meta: title: Block Storage FAQ - description: Explore Scaleway Block Storage with our comprehensive FAQ covering performance, persistence, and more. Learn how Block Storage compares to Local Storage and its compatibility with Scaleway resources. + description: Explore Scaleway Block Storage with our comprehensive FAQ covering performance, persistence, and more. Learn how Block Storage compares to Local NVMe storage and its compatibility with Scaleway resources. content: h1: Block Storage dates: @@ -10,13 +10,13 @@ category: storage productIcon: BlockStorageProductIcon --- -## Why should I use Block Storage instead of Local Storage? +## Why should I use Block Storage instead of Local NVMe storage? -The size of Local Storage depends on your Instance type. With today's configurations, the maximum Local Storage available is 600 GB. +The size of Local NVMe storage depends on your Instance type. With today's configurations, the maximum Local NVMe storage available is 600 GB. Block Storage allows you to create bigger volumes and those volumes are persistent which means that they can live without being attached to an Instance. -| | **Block Storage** | **Local Storage** | +| | **Block Storage** | **Local NVMe storage** | |--------------------|:---------------------------------:|:--------------------------------------------------------------------------------------------------------------:| | **Availability** | High | HV dependant (needs physical intervention to retrieve storage and data if HV dies) | | **Redundancy** | High (replica 3) | Low (RAID 5 - 5 disks) | diff --git a/faq/instances.mdx b/faq/instances.mdx index 1c88aa53be..1977f8af11 100644 --- a/faq/instances.mdx +++ b/faq/instances.mdx @@ -172,7 +172,7 @@ You can change the storage type and flexible IP after the Instance creation, whi | Product | All regions* | PAR3 | |-------------------|------------------------|-------------------| -| Local Storage | €0.000044 GB/hour | Not available | +| Local NVMe storage | €0.000044 GB/hour | Not available | | Local snapshot | €0.000044 GB/hour | Not available | | Block Storage | €0.000118 GB/hour | €0.000177 GB/hour | | Block snapshot | €0.000044 GB/hour | €0.000066 GB/hour | @@ -203,10 +203,10 @@ Dedicated Resources give you a more stable experience for compute-demanding work ### Which options are available to power off my Instance? You can choose between four options when powering off your Instance: -* **Hard reboot**: Your Instance performs an electrical reboot and its data is kept on the Local Storage. We recommend always rebooting your Instance from the OS to avoid data corruption. +* **Hard reboot**: Your Instance performs an electrical reboot and its data is kept on the Local NVMe storage. We recommend always rebooting your Instance from the OS to avoid data corruption. * **Power off**: All local volume data is transferred to a volume store, and your physical node is released back to the pool of available machines. The process duration depends on the amount of data archived. * **Terminate**: Your Instance and its volumes are permanently deleted, but the attached flexible IP is preserved. -* **Standby**: Your Instance is stopped, but its data remains in the Local Storage. The Instance is still allocated to your account and can be restarted anytime. +* **Standby**: Your Instance is stopped, but its data remains in the Local NVMe storage. The Instance is still allocated to your account and can be restarted anytime. The **standby mode** is charged as a running Instance. To avoid being billed for an unused Instance, power it off and ensure no IPs or allocated storage are left in use. diff --git a/faq/kubernetes.mdx b/faq/kubernetes.mdx index d487230db6..6a657b709c 100644 --- a/faq/kubernetes.mdx +++ b/faq/kubernetes.mdx @@ -83,7 +83,7 @@ For more information, refer to the Kubernetes Kapsule product documentation on [ To ensure sufficient space for storing default system files and configurations, we recommend a system volume disk capacity of at least 20 GB. While this amount is generally sufficient for small workloads, it is advisable to have a capacity of 100 GB to comfortably store images and system logs in many cases. If you run out of space on your immutable system volume disk, you can create another pool and use the **Advanced Options** button to set your desired system volume type and size. Depending on the type of node selected for your pool, one or two types of volume are available: -* **Local Storage**: Your system is stored locally on the hypervisor of your node. +* **Local NVMe storage**: Your system is stored locally on the hypervisor of your node. * **Block Storage**: A remote storage option where your system is stored on a centralized and resilient cluster. ### What is the service 'kapsule-agent' running on my nodes? diff --git a/pages/block-storage/quickstart.mdx b/pages/block-storage/quickstart.mdx index 534647fff7..7c75b4bde2 100644 --- a/pages/block-storage/quickstart.mdx +++ b/pages/block-storage/quickstart.mdx @@ -14,7 +14,7 @@ categories: - storage --- -Scaleway [Block Storage](/block-storage/concepts/#block-device) provides network-attached storage that can be plugged in and out of [Instances](/instances/concepts/#instance) like a virtual hard-drive. Block Storage devices are independent of the Local Storage of Instances, and the fact that they are accessed over a network connection makes it easy to move them between Instances in the same [Availability Zone](/instances/concepts/#availability-zone). +Scaleway [Block Storage](/block-storage/concepts/#block-device) provides network-attached storage that can be plugged in and out of [Instances](/instances/concepts/#instance) like a virtual hard-drive. Block Storage devices are independent of the Local NVMe storage of Instances, and the fact that they are accessed over a network connection makes it easy to move them between Instances in the same [Availability Zone](/instances/concepts/#availability-zone). From the user's point of view, once [mounted](/block-storage/api-cli/managing-a-volume/#mounting-and-using-a-block-storage-volume), the block device behaves like a regular disk. diff --git a/pages/block-storage/reference-content/differences-between-5kiops-volumes.mdx b/pages/block-storage/reference-content/differences-between-5kiops-volumes.mdx index 44779b2043..edd73ff628 100644 --- a/pages/block-storage/reference-content/differences-between-5kiops-volumes.mdx +++ b/pages/block-storage/reference-content/differences-between-5kiops-volumes.mdx @@ -13,11 +13,11 @@ categories: - storage --- -When creating volumes from the Scaleway console, you are prompted to choose between [Block Storage Low Latency](/block-storage/) volumes, [block volumes (Block Storage)](/instances/concepts/#block-volumes), and [local volumes (Local Storage)](/instances/concepts/#volumes). +When creating volumes from the Scaleway console, you are prompted to choose between [Block Storage Low Latency](/block-storage/) volumes, [block volumes (Block Storage)](/instances/concepts/#block-volumes), and [local volumes (Local NVMe storage)](/instances/concepts/#volumes). This page provides information about the differences between Block Storage and Block Storage Low Latency 5K [IOPS](/block-storage/concepts/#iops) volumes. -Refer to the [dedicated documentation](/instances/concepts/#volumes) to learn about the differences between Block Storage and Local Storage volumes. +Refer to the [dedicated documentation](/instances/concepts/#volumes) to learn about the differences between Block Storage and Local NVMe storage volumes. ## Underlying hardware diff --git a/pages/components/docs.mdx b/pages/components/docs.mdx index cd9aebd952..a21ab6711c 100644 --- a/pages/components/docs.mdx +++ b/pages/components/docs.mdx @@ -750,7 +750,7 @@ The above text come from a macro! - Choose an **Instance type**. Different Instance types have different prices, processing power, memory, storage options and bandwidth. - Add **Volumes**. Volumes are storage spaces used by your Instances. - - For **GP1 Instances** you can leave the default settings of a maximum local storage, or choose how much [local](/instances/concepts#local-volumes) and/or [block](/instances/concepts#block-volumes) storage you want. Your **system volume** is the volume on which your Instance will boot. The system volume can be either a local or a block volume. + - For **GP1 Instances** you can leave the default settings of a maximum Local NVMe storage, or choose how much [local](/instances/concepts#local-volumes) and/or [block](/instances/concepts#block-volumes) storage you want. Your **system volume** is the volume on which your Instance will boot. The system volume can be either a local or a block volume. - **PRO2** and **Enterprise** Instances boot directly [on block volumes](/instances/concepts/#boot-on-block). You can add several block volumes and define how much storage you want for each. Please note that: diff --git a/pages/gpu/how-to/create-manage-gpu-instance.mdx b/pages/gpu/how-to/create-manage-gpu-instance.mdx index 3229a74809..b0ce41231a 100644 --- a/pages/gpu/how-to/create-manage-gpu-instance.mdx +++ b/pages/gpu/how-to/create-manage-gpu-instance.mdx @@ -35,7 +35,7 @@ When you have completed your calculations using the GPU Instance, [deletion can - **Availability Zone**: Choose the geographical region, represented by the Availability Zone, where your Instance will be deployed. - **Instance Type (GPU)**: Select the desired GPU Instance type, considering factors such as processing power, memory, storage options, and bandwidth. Refer to our guide on [choosing the right GPU Instance type](/gpu/reference-content/choosing-gpu-instance-type/) for more information. - **Image**: Pick an operating system image suitable for your GPU Instance. For example, select **Ubuntu Jammy GPU OS 12**, which comes with preinstalled NVIDIA drivers and an NVIDIA Docker environment. You have the flexibility to customize your working environment using Docker with our provided Docker images or your own containers. - - **Volumes**: Optionally, add storage volumes for your Instance. You can adjust settings such as Block and Local Storage volumes according to your requirements. + - **Volumes**: Optionally, add storage volumes for your Instance. You can adjust settings such as Block and Local NVMe storage volumes according to your requirements. * The recommended minimum volume size for GPU OS images is 125 GB. * If your GPU Instance supports scratch storage, the scratch volume displays but can not be edited. [Learn more about scratch storage.](/gpu/how-to/use-scratch-storage-h100-instances/) diff --git a/pages/gpu/how-to/use-gpu-with-docker.mdx b/pages/gpu/how-to/use-gpu-with-docker.mdx index 9e955c14ec..b22d4a0cc7 100644 --- a/pages/gpu/how-to/use-gpu-with-docker.mdx +++ b/pages/gpu/how-to/use-gpu-with-docker.mdx @@ -47,7 +47,7 @@ We recommend that you map volumes from your GPU Instance to your Docker containe ### How to map local volumes -You can map directories from your GPU Instance's Local Storage to your Docker container, using the `-v :` flag. See the example command below: +You can map directories from your GPU Instance's Local NVMe storage to your Docker container, using the `-v :` flag. See the example command below: ```bash docker run -it --rm -v /root/mydata/:/workspace nvidia/cuda:11.2.1-runtime-ubuntu20.04 @@ -101,7 +101,7 @@ Below is a list of the most common commands you use when dealing with Docker con | **docker push** | `docker push ` | This command is used to push a local image to a remote repository. | | **docker images** | `docker images` | This command is used to list all available Docker images on the local system. | | **docker rm** | `docker rm ` | This command is used to remove a stopped container from the local system. | -| **docker rmi** | `docker rmi ` | This command is used to delete an image from the Local Storage. | +| **docker rmi** | `docker rmi ` | This command is used to delete an image from the Local NVMe storage. | | docker version| `docker --version` | This command is used to display information about the currently installed version of Docker. | For more information regarding the `docker run` command, refer to the [official documentation](https://docs.docker.com/engine/reference/run/). diff --git a/pages/gpu/how-to/use-scratch-storage-h100-instances.mdx b/pages/gpu/how-to/use-scratch-storage-h100-instances.mdx index 9331a36838..f6f88dcc90 100644 --- a/pages/gpu/how-to/use-scratch-storage-h100-instances.mdx +++ b/pages/gpu/how-to/use-scratch-storage-h100-instances.mdx @@ -13,7 +13,7 @@ categories: - compute --- -Scaleway H100 and L40S GPU Instances are equipped with additional scratch storage. This form of temporary Local Storage operates differently from our regular Local Storage. +Scaleway H100 and L40S GPU Instances are equipped with additional scratch storage. This form of temporary Local NVMe storage operates differently from our regular Local NVMe storage. Scratch storage temporarily accommodates data during computational or data processing tasks. It is commonly used for storing intermediate results, processing input data, or holding output data before that data is moved to more permanent storage. diff --git a/pages/gpu/quickstart.mdx b/pages/gpu/quickstart.mdx index e23b7ece7d..72315eed55 100644 --- a/pages/gpu/quickstart.mdx +++ b/pages/gpu/quickstart.mdx @@ -27,7 +27,7 @@ In addition to this, GPU Instances have all the features of our regular Instance - **Availability Zone**: Choose the geographical region, represented by the Availability Zone, where your Instance will be deployed. - **Instance Type (GPU)**: Select the desired GPU Instance type, considering factors such as processing power, memory, storage options, and bandwidth. Refer to our guide on [choosing the right GPU Instance type](/gpu/reference-content/choosing-gpu-instance-type/) for more information. - **Image**: Pick an operating system image suitable for your GPU Instance. For example, select **Ubuntu Jammy GPU OS 12**, which comes with preinstalled Nvidia drivers and an Nvidia Docker environment. You can customize your working environment using Docker with our provided Docker images or your own containers. - - **Volumes**: Optionally, add storage volumes for your Instance. You can adjust settings such as Block and Local Storage volumes according to your requirements. + - **Volumes**: Optionally, add storage volumes for your Instance. You can adjust settings such as Block and Local NVMe storage volumes according to your requirements. * The recommended minimum volume size for GPU OS images is 125 GB. * If your GPU Instance supports scratch storage, the scratch volume displays but can not be edited. [Learn more about scratch storage.](/gpu/how-to/use-scratch-storage-h100-instances/) diff --git a/pages/instances/api-cli/migrating-instances.mdx b/pages/instances/api-cli/migrating-instances.mdx index 739d14c23e..49141364c6 100644 --- a/pages/instances/api-cli/migrating-instances.mdx +++ b/pages/instances/api-cli/migrating-instances.mdx @@ -47,7 +47,7 @@ To do so, you need the Instance’s ID and a valid API key. You can retrieve a list of all available Instance types using the command `scw instance server-type list`. - Ensure that Local Storage constraints are respected. For example, downgrading from a larger Instance type to a smaller one may not be possible if the smaller Instance type cannot support the existing Local Storage. Check the Scaleway documentation for specific constraints. + Ensure that Local NVMe storage constraints are respected. For example, downgrading from a larger Instance type to a smaller one may not be possible if the smaller Instance type cannot support the existing Local NVMe storage. Check the Scaleway documentation for specific constraints. 3. Power on the Instance. @@ -86,7 +86,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 NVMe 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. Output: diff --git a/pages/instances/concepts.mdx b/pages/instances/concepts.mdx index b3a9647a69..bee52e3284 100644 --- a/pages/instances/concepts.mdx +++ b/pages/instances/concepts.mdx @@ -1,11 +1,11 @@ --- meta: title: Instances - Concepts - description: This page explains all the concepts related to Scaleway Instances + description: This page explains all the concepts related to Scaleway Instances. content: h1: Instances - Concepts - paragraph: This page explains all the concepts related to Scaleway Instances -tags: region traffic availability-zone block-volume boot-on-block cloud-init dynamic-ip flexible-ip reverse-dns stardust + paragraph: This page explains all the concepts related to Scaleway Instances. +tags: region, traffic, availability-zone, block-volume, boot-on-block, cloud-init, dynamic-ip, flexible-ip, reverse-dns, stardust dates: validation: 2025-02-24 categories: @@ -14,172 +14,121 @@ categories: ## Availability Zone -An Availability Zone refers to an isolated location within a specific region. Each Availability Zone provides its own services and infrastructure. For example, `fr-par-1`, `fr-par-2`, and `fr-par-3` are Availability Zones within the Paris region. +An Availability Zone is an isolated location within a specific region, providing dedicated infrastructure and services. For example, `fr-par-1`, `fr-par-2`, and `fr-par-3` are Availability Zones within the Paris region. -For an extensive list of which regions and AZ a resource is available in, refer to our [Product availability guide](/account/reference-content/products-availability/) +For a comprehensive list of regions and their corresponding Availability Zones, refer to our [Product Availability Guide](/account/reference-content/products-availability/). ## Block volumes -Block volumes provide network-attached storage you can plug in/out of Instances like a virtual hard drive. From a user's point of view, block volumes behave like regular disks and can be used to increase the storage of an Instance. +Block volumes offer network-attached storage that can be attached or detached from Instances like a virtual hard drive. They behave like traditional disks and can expand the storage capacity of an Instance. -## Boot-on-block +## Boot-on-Block -## Carrier-grade NAT (CGNAT) +## Carrier-Grade NAT (CGNAT) -Scaleway used a 1:1 carrier-grade (CGNAT) setup for legacy Instance types. With this architecture, each Instance was assigned a unique NAT IP that directly mapped to a unique public IP, unlike standard CGNAT, where multiple users share a single public IP. -This setup ensured that all outbound and inbound traffic for an Instance was translated between these two addresses, preserving the exclusivity of IP addresses and avoiding certain connectivity issues related to a shared IP setup. -All recent Instance types support routed IPs through [IP mobility](#ip-mobility). +Scaleway used a 1:1 carrier-grade NAT (CGNAT) setup for legacy Instance types. Unlike standard CGNAT, where multiple users share a single public IP, this setup ensured that each Instance had a unique NAT IP mapped to a unique public IP. This preserved IP exclusivity and prevented connectivity issues. + +All recent Instance types support routed IPs through [IP Mobility](#ip-mobility). ## Cloud-init -Cloud-init is a multi-distribution package that [provides boot time customization for cloud servers](/instances/how-to/use-boot-modes/#how-to-use-cloud-init). It enables an automatic Instance configuration as it boots into the cloud, turning a generic Ubuntu image into a configured server in a few seconds. +Cloud-init is a multi-distribution package that [enables boot-time customization for cloud servers](/instances/how-to/use-boot-modes/#how-to-use-cloud-init). It allows automatic Instance configuration upon boot, transforming a generic Ubuntu image into a fully configured server within seconds. ## Cost-Optimized Instances -[Cost-Optimized Instances](https://www.scaleway.com/en/cost-optimized-instances/) are production-grade [Instances](#instance) designed for scalable infrastructures. Cost-Optimized Instances support the boot-on-block feature and allow you to launch high-performance services with high-end CPUs. +[Cost-Optimized Instances](https://www.scaleway.com/en/cost-optimized-instances/) are production-grade Instances designed for scalable infrastructures. They support the boot-on-block feature and allow high-performance services with high-end CPUs. -## Development Instance +## Development Instances -[Development Instances](https://www.scaleway.com/en/cost-optimized-instances/) are reliable and flexible Instances tuned to host your websites, applications, and development environments. +[Development Instances](https://www.scaleway.com/en/cost-optimized-instances/) are reliable and flexible Instances designed for hosting websites, applications, and development environments. ## Dynamic IP -A dynamic IP is an alternative type of public IP address for your Instance. This type of IP address is detached and released back into the general public pool of IP addresses whenever you stop your Instance. This means when you next power on your Instance, it may get a different dynamic IP address. In this respect, dynamic IPs are different from [flexible IPs](#flexible-ip), which remain associated with your Instance even when the Instance is stopped and are held in your account and can be moved between different Instances if you wish. +A dynamic IP is a public IP address that is released back into the general pool when an Instance is stopped. When the Instance is restarted, it may receive a different dynamic IP. -You can choose to give your Instance a dynamic IP address when creating or updating your Instance via the [Scaleway API](https://www.scaleway.com/en/developers/api/instance/) only. Read our [billing FAQ](/faq/billing/#when-does-the-billing-of-an-instance-start-and-stop) for more information about the billing of dynamic and flexible IPs. +This differs from [Flexible IPs](#flexible-ip), which remain associated with an Instance even when it is stopped. Dynamic IPs can only be assigned via the [Scaleway API](https://www.scaleway.com/en/developers/api/instance/). Learn more in our [Billing FAQ](/faq/billing/#when-does-the-billing-of-an-instance-start-and-stop). ## Flexible IP -Flexible IP addresses are public IP addresses that you can hold independently of any Instance. When you create a Scaleway Instance, by default, its public IP address is also a flexible IP address. Flexible IP addresses can be attached to and detached from any Instances you wish. You can keep a number of flexible IP addresses in your account at any given time. When you delete a flexible IP address, it is disassociated from your account to be used by other users. Find out more with our dedicated documentation on [how to use flexible IP addresses](/instances/how-to/use-flexips/). See also [Dynamic IPs](#dynamic-ip). +Flexible IPs are public IP addresses that can be held independently of any Instance. By default, Scaleway Instances are assigned a Flexible IP. These IPs can be detached and reassigned to different Instances as needed. + +For more details, see our guide on [Using Flexible IP Addresses](/instances/how-to/use-flexips/). -## GPU Instance +## GPU Instances -[GPU Instances](https://www.scaleway.com/en/gpu-instances/) are powerful Instances equipped with dedicated high-end Nvidia graphics processing units. See our [dedicated GPU documentation](/gpu/) for more details. +[GPU Instances](https://www.scaleway.com/en/gpu-instances/) are powerful Instances equipped with high-end Nvidia GPUs. See our [dedicated GPU documentation](/gpu/) for details. ## Image -An image is a complete backup of your Instance. One image contains all the [volumes](#volumes) of your Instance and can be used to restore your Instance and its data. You can also use it to create a series of Instances with a predefined configuration. If you wish to copy only a specific volume of an Instance, you can use the [snapshot](#snapshot) feature instead. +An image is a complete backup of an Instance, containing all its [volumes](#volumes). It can be used to restore an Instance or create multiple Instances with the same configuration. For backing up a single volume, use the [snapshot](#snapshot) feature instead. ## Instance -An Instance is a virtual computing unit that offers resources for running applications. It functions as a self-contained entity with its own operating system, RAM, and storage. Each type of Instance has unique specifications. You can choose the type that best meets your requirements. Refer to our [Instance types documentation](/instances/reference-content/choosing-instance-type/) for further details on the various Scaleway Instance options. +An Instance is a virtual computing unit with dedicated resources such as CPU, RAM, and storage. Different Instance types cater to various workloads. See our [Instance Types Documentation](/instances/reference-content/choosing-instance-type/) for details. ## InstantApp -An InstantApp is an image with a preinstalled application. By choosing an InstantApp when prompted to select an image during the [creation of your Instance](/instances/how-to/create-an-instance/), you choose to install the specified application on your Instance. You can then start using the application immediately. +An InstantApp is a pre-installed application image. Choosing an InstantApp during [Instance creation](/instances/how-to/create-an-instance/) enables immediate use of the application. -## IP mobility +## IP Mobility -The legacy public network is provided through carrier-grade NAT infrastructure. -When an Instance starts, it is assigned a NAT IP address that is associated with the underlying node hosting the Instance. -The carrier-grade NAT establishes a one-to-one mapping between the public IP and the NAT IP assigned to the Instance during provisioning. Consequently, if the underlying node changes, the NAT IP address will also change. - -With IP mobility, there are no NAT IPs anymore. The public IP is entirely routed to the Instance. The main benefit is that your underlying IP no longer changes when you stop and start your Instance or if it gets provisioned on another hypervisor. But this also means that if you do not attach a public IP address to your Instance, then it will not have any network access. +IP Mobility eliminates the need for NAT IPs. Instead, the public IP is routed directly to the Instance, ensuring the IP remains unchanged during stop/start operations or migration to a different hypervisor. - Your IP address will only be retained during stop/start operations if you have linked a flexible public IP address to your Instance. If you use a dynamic IP address, the behavior remains consistent, whether your Instance has a routed IP enabled or is a legacy one. + Your IP address remains the same only if you use a Flexible IP. Instances with Dynamic IPs will still receive a new IP upon restart. -## Learning Instance +## Learning Instances -[Learning Instances](https://www.scaleway.com/en/stardust-instances/) are the perfect Instances for small workloads and simple applications. You can create up to one Instance per Availability Zone (available in FR-PAR-1 and NL-AMS-1). +[Learning Instances](https://www.scaleway.com/en/stardust-instances/) are ideal for small workloads and simple applications. You can create one Instance per Availability Zone (available in `fr-par-1` and `nl-ams-1`). ## Local volumes -The local volume of an Instance is an all-SSD-based storage solution, using a RAID array for redundancy and performance, hosted on the local hypervisor. On Scaleway Instances, the size of the local volume is fixed and depends on the Instance type. Some Instance types do not use local volumes and [boot directly on block volumes](#boot-on-block). In any case, it is always possible to increase the storage of an Instance by adding additional block volumes. +Local volumes are SSD-based storage solutions hosted on the local hypervisor. Their size is fixed and depends on the Instance type. Some Instances do not use local volumes and instead [boot directly on block volumes](#boot-on-block). ## Placement groups -Placement groups allow you to run multiple Compute Instances, each on a different physical hypervisor. Placement groups have two operating modes. The first one is called `max_availability`. It ensures that all the Compute Instances that belong to the same cluster will not run on the same underlying hardware. The second one is called `low_latency` and does the opposite, bringing Compute Instances closer together to achieve higher network throughput. [Learn how to use placement groups](/instances/how-to/use-placement-groups/). +Placement groups distribute Compute Instances across different physical hypervisors to optimize availability (`max_availability`) or reduce network latency (`low_latency`). [Learn more](/instances/how-to/use-placement-groups/). ## Production-Optimized Instances -[Production-Optimized Instances](https://www.scaleway.com/en/production-optimized-instances/) (aka POP2) are compute resources with dedicated resources (RAM and vCPUs). Designed for demanding applications, high-traffic databases, and production workloads. - -Three variants of POP2 Instances are available: -* **POP2**: Production-Optimized Instances with Block Storage. -* **POP2-HC**: Workload-Optimized Instances, providing a ratio of vCPU:RAM of 1:8. -* **POP2-HM**: Workload-Optimized Instances, providing a ratio of vCPU:RAM of 1:2. -* **POP2-HN**: Workload-Optimized Instances, providing a ratio of vCPU:RAM of 1:2 and up to 10 Gbps bandwidth. +[Production-Optimized Instances](https://www.scaleway.com/en/production-optimized-instances/) (POP2) provide dedicated compute resources for high-performance workloads. Variants include: -## Power-off mode - -The Power-off mode [shuts down an Instance](/instances/how-to/power-off-instance/) by transferring all data on the local volume of the Instance to a volume store. The physical node is released back to the pool of available machines. The reserved flexible IP of the Instance remains available in the account. - - - Depending on the amount of data to be archived, this process can take some time. - +- **POP2**: Block Storage-based Instances. +- **POP2-HC**: High-memory Instances (vCPU:RAM 1:8). +- **POP2-HM**: Balanced memory Instances (vCPU:RAM 1:2). +- **POP2-HN**: High-network Instances (vCPU:RAM 1:2, up to 10 Gbps bandwidth). ## Private Networks -Private Networks allow your virtual Instances to communicate in an isolated and secure network without requiring a connection to the public internet. Each Instance can be [connected to one or several Private Networks](/instances/how-to/use-private-networks/), letting you build your own network topologies. - -Private Networks are LAN-like layer 2 Ethernet networks. A new network interface with a unique media access control address (MAC address) is configured on each Instance in a Private Network. Use this interface to communicate in a secure and isolated network, using private IP addresses of your choice. - -## Protected Instance - -Protected Instance is a feature that prevents any halt action from being performed on your Instance. This only applies to running Instances. [Enabling the Protected Instance feature](/instances/how-to/use-protected-instance/) means that you will not be able to delete, power off, or reboot your Instance, nor put it into standby mode. - -## Public IP - -Public IP addresses are routed on the internet. You can enter the public IP address of your Instance into any browser connected to the internet, and access content being served from that Instance. You can think of public IP addresses like postal addresses for buildings - they are unique and tell the routers directing traffic through the internet where to find a particular server. - -## Region +Private Networks enable secure, isolated communication between Instances without internet access. [Learn more](/instances/how-to/use-private-networks/). -A region is a geographical area such as France (Paris: fr-par), the Netherlands (Amsterdam: nl-ams), or Poland (Warsaw: pl-waw) in which Scaleway products and resources are located. Each region contains multiple Availability Zones. +## Security groups -For an extensive list of which regions and AZ a resource is available in, refer to our [Product availability guide](/account/reference-content/products-availability/) +Security groups [control inbound and outbound traffic](/instances/how-to/use-security-groups/). They can be: -## Rescue mode +- **Stateful**: Allows return traffic for initiated connections. +- **Stateless**: Enforces strict inbound/outbound rules regardless of connection origin. -Rescue mode restarts your server via the network on a minimal operating system. You can [use rescue mode](/instances/how-to/use-boot-modes/#how-to-use-rescue-mode) to debug your server and recover your system data. Rescue mode creates a ramdisk with the content of a downloaded rootfs. You will have access to all your disks and will be able to perform debug and rescue actions. After disabling rescue mode, you will have to reboot your server. Your server needs to be running to switch to rescue mode. - -## Reverse DNS - -Reverse DNS is the opposite of classic "forward" DNS, and maps an IP address to a hostname. This can be useful if, for example, you want to send emails from your Instance. Find out how to [configure reverse DNS on your Instance](/instances/how-to/configure-reverse-dns/) with our how-to documentation. - -## Routed flexible IP - -A routed flexible IP means assigning a public IP address to an Instance (virtual machine) that is reachable directly from the internet. This means there's [no address translation](/instances/concepts/#carrier-grade-nat-cgnat), and the Instance uses the public IP as its identity on the internet. -The Instance can be accessed or can communicate directly using this public IP, which helps to make network configuration straightforward, with unrestricted inbound and outbound connections, crucial for services like web hosting or email servers. - -## Security group - -Security groups allow you to [create rules to drop or allow public traffic coming to and from your Instances](/instances/how-to/use-security-groups/). You can set default policies for inbound and outbound traffic, and/or define rules to deal with traffic differently depending on its source. Security groups can be [stateful](#stateful-security-groups) or [stateless](#stateless-security-groups). Note that security groups for Elastic Metal servers cannot be stateful. - Security Groups only allow the filtering of **public** traffic to and from your Instances. To filter traffic within a Private Network, you can [configure a firewall](/tutorials/installation-uncomplicated-firewall/) directly on your Instance, or use `iptables` or `nftables` from the command line interface of your Instance. + Security groups filter **public** traffic only. Use a firewall (e.g., `iptables`) to control Private Network traffic. ## Snapshot -A snapshot takes a picture of a specific volume at one point in time. For example, you may have a server with one volume containing the OS and another containing the application data and want to use different snapshot strategies on both volumes. [Creating snapshots of your volumes](/instances/how-to/create-a-snapshot/) gives you total freedom of which volumes you want to back up, while [images](#image) are more convenient for full backups of your Instance. - -## Snapshot type - -An image is composed of snapshots of volumes. Snapshots can only be restored to a volume of the original type. - -## Standby mode - -Standby mode is a way to stop an Instance temporarily. When you [put an Instance in standby mode](/instances/how-to/use-standby-mode/), the server is halted, but the Instance remains allocated to your account, and all data remains on the Local Storage of the Instance. - -## Stateful security groups - -Stateful security groups disregard the default policy and inbound/outbound rules if a connection is initiated from your Instance. Traffic will always be permitted on connections that you initiated. This is useful for example if you want to initiate connections on many and various ports for messaging, video streaming, or other purposes. In this case, the traffic from/to that connection will not be blocked, even if you have defined a rule that would otherwise do so. [Learn how to use security groups](/instances/how-to/use-security-groups/). - -## Stateless security groups - -Stateless security groups strictly apply the default policy and inbound/outbound rules, regardless of whether a connection is initiated from your Instance or not. This is useful if you know exactly which ports you will always require for your Instance, e.g. port `22` for SSH. You can make your security group stateless, define a rule to allow traffic on port `22` and block incoming traffic on other ports regardless of whether a connection is initiated from your Instance on this port. [Learn how to use security groups](/instances/how-to/use-security-groups/). +A snapshot is a point-in-time backup of a specific volume. Unlike images, which capture entire Instances, snapshots allow granular control over volume backups. [Learn more](/instances/how-to/create-a-snapshot/). ## Tags -Tags allow you to organize, sort, filter, and monitor your cloud resources using any pattern you wish. You can assign as many tags as you want to each Scaleway product. +Tags help organize, filter, and monitor cloud resources efficiently. Multiple tags can be assigned to each Scaleway product. ## Volumes -Volumes are the storage space of your Instances. Two types of volumes exist: +Scaleway offers two volume types: -* **Local volumes**: The local volume of an Instance is an all-SSD-based storage solution, using a RAID array for redundancy and performance, hosted on the local hypervisor. On Scaleway Instances, the size of the local volume is fixed and depends on the Instance type. Some Instance types do not use local volumes and [boot directly on block volumes](#boot-on-block). +- **Local volumes**: Fixed-size SSD storage hosted on the local hypervisor. +- **Block volumes**: Network-attached storage that can be attached/detached like a virtual disk. -* **Block volumes**: Block volumes provide network-attached storage you can plug in and out of Instances like a virtual hard drive. Block volumes behave like regular disks and can be used to increase the storage of an Instance. \ No newline at end of file +For more details, refer to [Block Volumes](#block-volumes) and [Local Volumes](#local-volumes). diff --git a/pages/instances/how-to/create-a-block-volume.mdx b/pages/instances/how-to/create-a-block-volume.mdx index 68b6263fc6..ebdaa9bb6b 100644 --- a/pages/instances/how-to/create-a-block-volume.mdx +++ b/pages/instances/how-to/create-a-block-volume.mdx @@ -32,7 +32,7 @@ categories: The volume must be in the same Availability Zone as the Instance you want to connect it to. 5. Enter the volume name and select a size. -6. Configure the volume type. You can either create a **Block Storage** or **Local Storage** volume. +6. Configure the volume type. You can either create a **Block Storage** or **Local NVMe storage** volume. To use **[Block Storage Low Latency](/block-storage/) 15k**, your Instance must have at least **3 GiB/s of block bandwidth**. You can verify if an Instance type meets this requirement by consulting the [Scaleway Instances internet and Block Storage bandwidth overview](/instances/reference-content/instances-bandwidth-overview/) documentation. diff --git a/pages/instances/how-to/create-a-snapshot.mdx b/pages/instances/how-to/create-a-snapshot.mdx index 25f6877098..6222c4453b 100644 --- a/pages/instances/how-to/create-a-snapshot.mdx +++ b/pages/instances/how-to/create-a-snapshot.mdx @@ -17,7 +17,7 @@ The snapshot feature allows you to create an image of a specific [volume](/insta Several options are available to create snapshots from your Instance: -* **LSSD (Local Storage):** This snapshot type can be created from local volumes. LSSD snapshots can be converted to local volumes only. +* **LSSD (Local NVMe storage):** This snapshot type can be created from local volumes. LSSD snapshots can be converted to local volumes only. * **BSSD (Block Storage):** This snapshot type can be created from block volumes. BSSD snapshots can be converted to block volumes only. diff --git a/pages/instances/how-to/create-an-instance.mdx b/pages/instances/how-to/create-an-instance.mdx index 907b06edff..c39194f075 100644 --- a/pages/instances/how-to/create-an-instance.mdx +++ b/pages/instances/how-to/create-an-instance.mdx @@ -181,7 +181,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 (`b_ssd`), others also support Local NVMe 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). | 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 3bbb3dfe9b..1f5cd1c860 100644 --- a/pages/instances/how-to/create-image-from-snapshot.mdx +++ b/pages/instances/how-to/create-image-from-snapshot.mdx @@ -51,7 +51,7 @@ scw instance image create snapshot-id="$SCW_VOLUME_ID_1" additional-volumes.0.id Supported volume IDs include: - - Local Storage volumes (`l_ssd`) + - Local NVMe storage volumes (`l_ssd`) - Block Storage Low Latency volumes (`sbs`) - Block Storage legacy (`b_ssd`) volumes (deprecated). @@ -82,7 +82,7 @@ curl --location "https://api.scaleway.com/instance/v1/zones/$SCW_AVAILABILITY_ZO Supported volume IDs include: - - Local Storage volumes (`l_ssd`) + - Local NVMe storage volumes (`l_ssd`) - Block Storage Low Latency volumes (`sbs`) - Block Storage legacy (`b_ssd`) volumes (deprecated). diff --git a/pages/instances/how-to/use-standby-mode.mdx b/pages/instances/how-to/use-standby-mode.mdx index d96455949a..366ef48cc3 100644 --- a/pages/instances/how-to/use-standby-mode.mdx +++ b/pages/instances/how-to/use-standby-mode.mdx @@ -13,7 +13,7 @@ categories: - compute --- -[Standby mode](/instances/concepts/#standby-mode) temporarily stops an Instance. The Instance remains allocated to your account and all data remains on the Local Storage of the Instance. +[Standby mode](/instances/concepts/#standby-mode) temporarily stops an Instance. The Instance remains allocated to your account and all data remains on the Local NVMe storage of the Instance. diff --git a/pages/instances/reference-content/choosing-instance-type.mdx b/pages/instances/reference-content/choosing-instance-type.mdx index 7d06564938..54e8800f5c 100644 --- a/pages/instances/reference-content/choosing-instance-type.mdx +++ b/pages/instances/reference-content/choosing-instance-type.mdx @@ -55,7 +55,7 @@ Use this table to help identify the right Instance range for your use case and c | **Instance range** | [Learning](/instances/reference-content/learning/) | [Cost-Optimized](/instances/reference-content/cost-optimized/) | [Production-Optimized](/instances/reference-content/production-optimized/) | [Workload-Optimized](/instances/reference-content/workload-optimized/) | |-----------------------|----------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Use cases** | Discovering the Scaleway ecosystem
Hosting personal projects | Scaling your development and testing environment
Hosting CI/CD runners and containerized worker nodes | Hosting production workloads and business-critical applications
Ensuring predictable CPU performance in the face of high traffic | Hosting high-demanding analysis, in-memory calculation, big-data processing, high-performance or cache databases
Designed for high-performance web-serving, video encoding, machine learning, batch processing, CI/CD | -| **Supported storage** | Resilient Block Storage or Local Storage | Resilient Block Storage or Local Storage, OR Resilient Block Storage only (depending on Instance type) | Resilient Block Storage | Resilient Block Storage | +| **Supported storage** | Resilient Block Storage or Local NVMe storage | Resilient Block Storage or Local NVMe storage, OR Resilient Block Storage only (depending on Instance type) | Resilient Block Storage | Resilient Block Storage | | **vCPU** | 1 core | From 1 to 32 cores | From 2 to 96 cores | From 2 to 64 cores | | **Shared/Dedicated** | Shared vCPU | Shared vCPU | Dedicated vCPU | Dedicated vCPU | | **RAM** | 1 GiB | From 2 GiB to 128 GiB | From 8 GiB to 384 GiB | From 4 GiB to 512 GiB | diff --git a/pages/kubernetes/concepts.mdx b/pages/kubernetes/concepts.mdx index 202b14c2e3..1c37f60f09 100644 --- a/pages/kubernetes/concepts.mdx +++ b/pages/kubernetes/concepts.mdx @@ -147,7 +147,7 @@ The system volume is a read-only volume that stores essential files for the Kube Depending on the type of node selected, we provide one or two types of volume. - - **Local Storage:** your system is stored locally on the hypervisor of your node. + - **Local NVMe storage:** your system is stored locally on the hypervisor of your node. - **Block Storage:** your system is remotely stored on a centralized and resilient cluster. As a general guideline, your system volume disk should have a capacity of at least 20 GB to ensure enough space to store the necessary system files and configurations. \ No newline at end of file diff --git a/pages/managed-databases-for-postgresql-and-mysql/concepts.mdx b/pages/managed-databases-for-postgresql-and-mysql/concepts.mdx index 1446fccbd6..d84251877b 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/concepts.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/concepts.mdx @@ -92,12 +92,12 @@ The HA standby node is linked to the main node, using synchronous replication. S HA standby nodes are not accessible to users unless the main node becomes unavailable and the standby takes over. If you wish to run queries on a read-only node, you can use [Read Replicas](/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica/). -## Local Storage +## Local NVMe storage With this type, your storage is fixed and tied to your compute resource. - Local Storage is only available with first-generation node types. + Local NVMe storage is only available with first-generation node types. ## Logs @@ -122,7 +122,7 @@ A database type that uses the relational model, which means that it stores and p ## Volume type -This is the type of storage used on your Database Instances. Three types are available: [Local Storage](#local-storage), [Block Storage Legacy](#block-storage-legacy), and [Block Storage](#block-storage). +This is the type of storage used on your Database Instances. Three types are available: [Local NVMe storage](#local-storage), [Block Storage Legacy](#block-storage-legacy), and [Block Storage](#block-storage). New Block Storage volumes are only available with new-generation node types and only in the PAR and AMS regions. diff --git a/pages/organizations-and-projects/additional-content/organization-quotas.mdx b/pages/organizations-and-projects/additional-content/organization-quotas.mdx index 4718898368..486bc609e6 100644 --- a/pages/organizations-and-projects/additional-content/organization-quotas.mdx +++ b/pages/organizations-and-projects/additional-content/organization-quotas.mdx @@ -323,13 +323,13 @@ Local and Block Storage options are available with our compute offers. Regardless of the quotas displayed below, be aware that: - A virtual Instance can bear up to 16 volumes, including the mandatory local volume. Therefore, the maximum number of block volumes that can be attached to an Instance is 15. - The maximum size of a block volume is 10 TB. - - The maximum Local Storage for a DEV Instance depends on the DEV Instance type. For example, for the DEV1-XL the maximum Local Storage is 120 GB. + - The maximum Local NVMe storage for a DEV Instance depends on the DEV Instance type. For example, for the DEV1-XL the maximum Local NVMe storage is 120 GB. | | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card ) | Payment method and [identity validated](/account/how-to/verify-identity/) | |------------------------------------------------|:------------------------------------------------------------------------------------------------------------:|:--------------------------------------------------------------------------------------:| | Block Storage total size in GB | 500 | 5 000 | -| Local Storage total size in GB | 1 000 | 5 000 | +| Local NVMe storage total size in GB | 1 000 | 5 000 | | Snapshots | 99 999 | 99 999 | | Images | 99 999 | 99 999 | | Volumes | 200 | 5 000 |