Skip to content

Commit 23fbcca

Browse files
committed
2 parents bc1d562 + e365b22 commit 23fbcca

File tree

22 files changed

+258
-61
lines changed

22 files changed

+258
-61
lines changed
Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
---
2+
macro: availability-zone
3+
---
4+
5+
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.
6+
7+
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/).

macros/concepts/block-snapshot.mdx

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
macro: block-snapshot
3+
---
4+
5+
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](/block-storage/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.

macros/concepts/block-volumes.mdx

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
macro: block-volumes
3+
---
4+
5+
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.

macros/concepts/local-volumes.mdx

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
macro: local-volumes
3+
---
4+
5+
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 extra block volumes.

macros/concepts/region.mdx

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
---
2+
macro: region
3+
---
4+
5+
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.
6+
7+
For an extensive list of which regions and AZs a resource is available in, refer to our [Product availability guide](/account/reference-content/products-availability/).

macros/concepts/volumes.mdx

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
---
2+
macro: volumes
3+
---
4+
5+
Volumes are the storage space of your Instances. Two types of volumes exist:
6+
7+
* **[Local volumes](/local-storage/)**: 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](/instances/concepts/#boot-on-block).
8+
9+
* **[Block volumes](/block-storage/)**: 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.

menu/navigation.json

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1875,6 +1875,10 @@
18751875
"label": "Connect to a cluster with kubectl",
18761876
"slug": "connect-cluster-kubectl"
18771877
},
1878+
{
1879+
"label": "Manage Kapsule node pools",
1880+
"slug": "manage-node-pools"
1881+
},
18781882
{
18791883
"label": "Deploy an image from Container Registry",
18801884
"slug": "deploy-image-from-container-registry"

package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@
2525
"@commitlint/config-conventional": "^19.8.1",
2626
"husky": "^8.0.3",
2727
"lint-staged": "^16.1.2",
28-
"prettier": "^3.5.3"
28+
"prettier": "^3.6.0"
2929
},
3030
"scripts": {
3131
"prepare": "husky install",

pages/block-storage/concepts.mdx

Lines changed: 19 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,17 @@ categories:
1414
- storage
1515
---
1616

17-
## Block device
17+
## Availability Zone
1818

19-
A block device is a storage volume on a network-connected storage system that is exposed to the guest operating system as if it were a physical disk.
19+
<Macro id="availability-zone" />
20+
21+
## Block volumes
22+
23+
<Macro id="block-volumes" />
24+
25+
## Boot-on-block
26+
27+
<Macro id="storage-boot-on-block" />
2028

2129
## IOPS
2230

@@ -29,7 +37,15 @@ Scaleway Block Storage Low Latency offers two IOPS limits:
2937

3038
## Local volume
3139

32-
The local volume of an Instance is an all SSD-based storage solution, using a RAID array for redundancy and performance, that is hosted on the local hypervisor.
40+
<Macro id="local-volumes" />
41+
42+
## Region
43+
44+
<Macro id="region" />
45+
46+
## Snapshot
47+
48+
<Macro id="block-snapshot" />
3349

3450
## Storage Area Networks (SANs)
3551

pages/elastic-metal/how-to/use-private-networks.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -141,7 +141,7 @@ You must configure the virtual network interface on each Elastic Metal server yo
141141
- Ensure that you have defined the same adapter name (`eno1`) for the default network interface in the default Netplan configuration file (`/etc/netplan/50-cloud-init.yaml`) before applying the new configuration.
142142
</Message>
143143

144-
## How to configure the Private Network on Windows Server 2019
144+
## How to configure the Private Network on Windows Server 2019 and 2022
145145

146146
1. Log into your server as `Administrateur` using the Remote Desktop client.
147147
<Message type="note">

0 commit comments

Comments
 (0)