From f1f0dd97971b0b065842713104058a7e713f24db Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Tue, 1 Jul 2025 14:42:13 +0200 Subject: [PATCH 01/13] feat(efc): bls pt1 --- .../block-storage-env-footprint.mdx | 50 +++++++++++++++++++ .../environmental-footprint-integration.mdx | 9 ++-- 2 files changed, 55 insertions(+), 4 deletions(-) create mode 100644 pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx diff --git a/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx b/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx new file mode 100644 index 0000000000..056c20c974 --- /dev/null +++ b/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx @@ -0,0 +1,50 @@ +--- +meta: + title: Block Storage footprint calculation + description: This page explains how Scaleway calculates the environmental footprint of its Block Storage in detail. +content: + h1: Block Storage footprint calculation + paragraph: This page explains how Scaleway calculates the environmental footprint of its Block Storage in detail. +tags: block-storage environmental-footprint impact datacentre +dates: + validation: 2025-07-01 + posted: 2025-07-01 +categories: + - environmental-footprint + - block-storage +--- + +This page includes the specificities of the environmental footprint calculation for Block Storage. + +## Resources used for estimation +The main unit taken into account in the Block Storage footprint estimation is **VOLsto**, which represents the **reserved volume** per user. + +The total estimated impact is calculated by integrating: + +- **Manufacturing impact** - Related to the physical servers hosting the storage volumes. +- **Shared infrastructure impact** - The impact of the tools used to manage the Block Storage offers: control plane, monitoring, internal load balancers, and others. +- **Energy usage impact** - The average electricity consumption of storage servers and their energy efficiency. + +## Calculation aspects + +### Ratio per storage volume +To allocate the impact of a specific storage volume, we apply the following RCP allocation rule: + +- Attribution of the manufacturing impact to **VOLsto**: with a **factor of 3 to account for replication**. +We use this ratio in the rest of the calculations. + +### Manufacturing impact +The manufacturing impact is attributed based on the servers hosting the storage: + +Retrieval of **hardware specifications** of Block Storage servers → The only available data source today is the [Confluence BLOCK STORAGE page](https://confluence.internal.scaleway.com/display/BLOCK+STORAGE), which will need to be transcribed into a YML file (2 different types of HW currently). In this YML file, we indicate the available volume, which corresponds to 60% of the total volume (the rest being reserved for performance reasons). + +### Shared infrastructures +| Component | Description | Hardware | Manufacturing & Usage | +| --- | --- | --- | --- | +| Control Plane | List of infrastructure VMs used by the Block Storage team | All VMs of the tenant [https://netbox.internal.scaleway.com/tenancy/tenants/212/](https://netbox.internal.scaleway.com/tenancy/tenants/212/), "blk" VMs of the tenant [https://netbox.internal.scaleway.com/tenancy/tenants/148/](https://netbox.internal.scaleway.com/tenancy/tenants/148/) | Calculate impact as done for Apple Silicon product VMs | +| Data Plane | List of servers used by the Block Storage team | All devices of the tenant [https://netbox.internal.scaleway.com/tenancy/tenants/148/](https://netbox.internal.scaleway.com/tenancy/tenants/148/) | Calculate manufacturing impact via [Boavizta](https://www.boavizta.org/), retrieve electricity consumption estimation and multiply by PUE and energy mix | + +* The allocation is done **based on electrical power**: we need to retrieve the electrical power dedicated to Block Storage: + * Retrieval of the estimation of the electricity consumption of the Block Storage servers –> [Handbook](https://handbook.scaleway.com/) (static data, like for Elastic Metal). + * Retrieval of the **quantities of hardware of the Data plane**. + * We add the **electricity consumption of the Control Plane VMs**. diff --git a/pages/environmental-footprint/additional-content/environmental-footprint-integration.mdx b/pages/environmental-footprint/additional-content/environmental-footprint-integration.mdx index 0b757724be..556dbad95b 100644 --- a/pages/environmental-footprint/additional-content/environmental-footprint-integration.mdx +++ b/pages/environmental-footprint/additional-content/environmental-footprint-integration.mdx @@ -19,22 +19,23 @@ The following tables provide details about the Scaleway products that currently | **Product Name** | **Environmental Footprint calculator available** | |----------------------------|---------------------------------| -| Elastic Metal | **Yes** | | Apple Silicon | **Yes** | -| CPU Instances | **Yes** | +| CPU Instances | **Yes** | +| Block Storage | **Yes** | +| Elastic Metal | **Yes** | +| Instances | **Yes** | ## Planned product integration | **Product Name** | **Environmental Footprint calculator available** | |----------------------------|---------------------------------| | Dedibox | **Integration ongoing** | -| Block Storage | **Integration ongoing** | +| Object Storage | **Integration ongoing** | | GPU Instances | **Not integrated yet** | | Kubernetes | **Not integrated yet** | | Container Registry | **Not integrated yet** | | Managed Inference | **Not integrated yet** | | Generative APIs | **Not integrated yet** | -| Object Storage | **Not integrated yet** | | Managed Databases for PostgreSQL and MySQL | **Not integrated yet** | | Serverless Functions | **Not integrated yet** | | Serverless Containers | **Not integrated yet** | From b76206623de45f4eab01a898b60c7b6759e64c2e Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Tue, 8 Jul 2025 16:52:17 +0200 Subject: [PATCH 02/13] feat(efc): bls --- .../bare-metal-env-footprint.mdx | 2 +- .../block-storage-env-footprint.mdx | 50 +++++++++++++------ 2 files changed, 35 insertions(+), 17 deletions(-) diff --git a/pages/environmental-footprint/additional-content/bare-metal-env-footprint.mdx b/pages/environmental-footprint/additional-content/bare-metal-env-footprint.mdx index 996b5b6859..a7cf43076b 100644 --- a/pages/environmental-footprint/additional-content/bare-metal-env-footprint.mdx +++ b/pages/environmental-footprint/additional-content/bare-metal-env-footprint.mdx @@ -41,7 +41,7 @@ The manufacturing impact is prorated based on the server's lifespan and the dura ## Calculation example -For the use of an Elastic Metal server, with a lifespan of 6 years (52 560 hours) and power of 110w, for 100 hours and considering via Boavizta estimates that the impact of the manufacturing of this server is 850 kgCo2e, we make the following calculation: +For the use of an Elastic Metal server, with a lifespan of 6 years (52 560 hours) and power of 110w, for 100 hours and considering via [Boavizta estimates](https://doc.api.boavizta.org/) that the impact of the manufacturing of this server is 850 kgCo2e, we make the following calculation: ```math ServerManufacturing = (100 / 52560) * 850 = 1,62 kgCO2e diff --git a/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx b/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx index 056c20c974..b143fff5f2 100644 --- a/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx +++ b/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx @@ -16,35 +16,53 @@ categories: This page includes the specificities of the environmental footprint calculation for Block Storage. -## Resources used for estimation -The main unit taken into account in the Block Storage footprint estimation is **VOLsto**, which represents the **reserved volume** per user. +## Calculation aspects -The total estimated impact is calculated by integrating: +The total estimated impact of Block Storage volumes is calculated by integrating the: - **Manufacturing impact** - Related to the physical servers hosting the storage volumes. -- **Shared infrastructure impact** - The impact of the tools used to manage the Block Storage offers: control plane, monitoring, internal load balancers, and others. +- **Cross-IT equipment impact** - The impact of the tools used to manage the Block Storage offers: control plane, monitoring, internal load balancers, and others. - **Energy usage impact** - The average electricity consumption of storage servers and their energy efficiency. -## Calculation aspects - ### Ratio per storage volume -To allocate the impact of a specific storage volume, we apply the following RCP allocation rule: -- Attribution of the manufacturing impact to **VOLsto**: with a **factor of 3 to account for replication**. -We use this ratio in the rest of the calculations. +To allocate the impact of a Block Storage volume, we apply the unit resulting from the RCP allocation rule to all calculation steps, the `bls_ration`: + +``` +VOLsto/VolstoPool = bls_ratio +``` + +- **VOLsto** - represents the **reserved volume** per user. In Block Storage, your data is replicated three times on multiple nodes to guarantee availability, so the **VOLsto** is applied with factor of 3 to account for replication. +- **VolstoPool** - represents all the storage for Block Storage volumes on the server that hosts them (around 60%). ### Manufacturing impact -The manufacturing impact is attributed based on the servers hosting the storage: -Retrieval of **hardware specifications** of Block Storage servers → The only available data source today is the [Confluence BLOCK STORAGE page](https://confluence.internal.scaleway.com/display/BLOCK+STORAGE), which will need to be transcribed into a YML file (2 different types of HW currently). In this YML file, we indicate the available volume, which corresponds to 60% of the total volume (the rest being reserved for performance reasons). +The manufacturing impact of Block Storage volumes is attributed based on the servers that host the storage. + +Considering a server with a lifespan of 6 years (52 560 hours) and power of 110w, for 100 hours and considering via Boavizta estimates that the impact of the manufacturing of this server is 850 kgCo2e, and a `bls_ratio` of we can make the following calculation: + +``` +VolumeManufacturingImpact = (100 / 52560) * 850 * bls_ratio = [À REMPLIR] kgCO2e +``` -### Shared infrastructures -| Component | Description | Hardware | Manufacturing & Usage | -| --- | --- | --- | --- | -| Control Plane | List of infrastructure VMs used by the Block Storage team | All VMs of the tenant [https://netbox.internal.scaleway.com/tenancy/tenants/212/](https://netbox.internal.scaleway.com/tenancy/tenants/212/), "blk" VMs of the tenant [https://netbox.internal.scaleway.com/tenancy/tenants/148/](https://netbox.internal.scaleway.com/tenancy/tenants/148/) | Calculate impact as done for Apple Silicon product VMs | -| Data Plane | List of servers used by the Block Storage team | All devices of the tenant [https://netbox.internal.scaleway.com/tenancy/tenants/148/](https://netbox.internal.scaleway.com/tenancy/tenants/148/) | Calculate manufacturing impact via [Boavizta](https://www.boavizta.org/), retrieve electricity consumption estimation and multiply by PUE and energy mix | +### Cross-IT equipment impact + +The calculation of the impact of cross-IT equipments takes into consideration the manufacturing and usage impacts of both the control and data plane of the internal Scaleway infrastructure for Block Storage. + +- **Control Plane** - Calculate impact as done for Apple Silicon product VMs | +- **Data Plane** - Calculate manufacturing impact via [Boavizta](https://www.boavizta.org/), retrieve electricity consumption estimation and multiply by PUE and energy mix | * The allocation is done **based on electrical power**: we need to retrieve the electrical power dedicated to Block Storage: * Retrieval of the estimation of the electricity consumption of the Block Storage servers –> [Handbook](https://handbook.scaleway.com/) (static data, like for Elastic Metal). * Retrieval of the **quantities of hardware of the Data plane**. * We add the **electricity consumption of the Control Plane VMs**. + + +To calculate the usage, we consider the French energy mix and the datacenter's PUE. In this example, they are O,056kgCo2e/kwh and 1,16, respectively. Which results in: + +```math +UsageFootprint = 0,110 x 100 x 0,056 x 1,16 = 0,715 kgCo2e +``` + +### Energy usage impact + From bb6b498515b0ad3972bad473368ae9c0669baea1 Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Wed, 9 Jul 2025 14:20:55 +0200 Subject: [PATCH 03/13] feat(efc): bls --- .../additional-content/block-storage-env-footprint.mdx | 9 ++++----- .../additional-content/instances-env-footprint.mdx | 4 ++-- 2 files changed, 6 insertions(+), 7 deletions(-) diff --git a/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx b/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx index b143fff5f2..fd1b4c1774 100644 --- a/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx +++ b/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx @@ -21,7 +21,7 @@ This page includes the specificities of the environmental footprint calculation The total estimated impact of Block Storage volumes is calculated by integrating the: - **Manufacturing impact** - Related to the physical servers hosting the storage volumes. -- **Cross-IT equipment impact** - The impact of the tools used to manage the Block Storage offers: control plane, monitoring, internal load balancers, and others. +- **Usage Impact** - The impact of the tools used to manage the Block Storage offers: control plane, monitoring, internal load balancers, and others. - **Energy usage impact** - The average electricity consumption of storage servers and their energy efficiency. ### Ratio per storage volume @@ -45,19 +45,18 @@ Considering a server with a lifespan of 6 years (52 560 hours) and power of 110w VolumeManufacturingImpact = (100 / 52560) * 850 * bls_ratio = [À REMPLIR] kgCO2e ``` -### Cross-IT equipment impact +### Usage impact The calculation of the impact of cross-IT equipments takes into consideration the manufacturing and usage impacts of both the control and data plane of the internal Scaleway infrastructure for Block Storage. -- **Control Plane** - Calculate impact as done for Apple Silicon product VMs | -- **Data Plane** - Calculate manufacturing impact via [Boavizta](https://www.boavizta.org/), retrieve electricity consumption estimation and multiply by PUE and energy mix | +- **Control Plane** - Calculate impact as done for Apple Silicon product VMs - hardware and vms +- **Data Plane** - Calculate manufacturing impact via [Boavizta](https://www.boavizta.org/), retrieve electricity consumption estimation and multiply by PUE and energy mix * The allocation is done **based on electrical power**: we need to retrieve the electrical power dedicated to Block Storage: * Retrieval of the estimation of the electricity consumption of the Block Storage servers –> [Handbook](https://handbook.scaleway.com/) (static data, like for Elastic Metal). * Retrieval of the **quantities of hardware of the Data plane**. * We add the **electricity consumption of the Control Plane VMs**. - To calculate the usage, we consider the French energy mix and the datacenter's PUE. In this example, they are O,056kgCo2e/kwh and 1,16, respectively. Which results in: ```math diff --git a/pages/environmental-footprint/additional-content/instances-env-footprint.mdx b/pages/environmental-footprint/additional-content/instances-env-footprint.mdx index 40830a25cc..57636c8852 100644 --- a/pages/environmental-footprint/additional-content/instances-env-footprint.mdx +++ b/pages/environmental-footprint/additional-content/instances-env-footprint.mdx @@ -36,7 +36,7 @@ The calculation using the elements above can be broken down into: - Energy mix of the country that provides the electricity. ### Usage Impact - - Resources consumed by the Instance, calculated based on the material specifications of the hypervisors. + - Resources consumed by the Instance, [calculated based on the material specifications of the hypervisors](#electricity-consumption-calculation). ### Indirect Emissions - Impact related to cross-functional services necessary to guarantee the operation of the Instance, such as network and shared storage. @@ -57,7 +57,7 @@ Refer to the table below to understand how the `Resources_Used_VM` is integrated To obtain an accurate calculation of the Instance's footprint, we multiply the results in each step of the [basis calculation](/environmental-footprint/additional-content/environmental-footprint-calculator/), bar the Cross-IT equipment & stock calculations step, by the `Resources_Used_VM` ratio. -## Cross-IT equipment calculation for Instances +## Electricity consumption calculation The only part of the calculation that will differ from the basis is the [Customer Servers](/environmental-footprint/additional-content/environmental-footprint-calculator/#customer-servers) section. From 82564f1b150430a84b0fb32e2e9be89b449725f0 Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Thu, 10 Jul 2025 14:48:12 +0200 Subject: [PATCH 04/13] feat(bls): final version --- menu/navigation.json | 4 ++ .../bare-metal-env-footprint.mdx | 2 +- .../block-storage-env-footprint.mdx | 44 ++++++++++++------- .../environmental-footprint-calculator.mdx | 1 + .../instances-env-footprint.mdx | 2 +- 5 files changed, 34 insertions(+), 19 deletions(-) diff --git a/menu/navigation.json b/menu/navigation.json index 5e794a45c9..443a1f48e4 100644 --- a/menu/navigation.json +++ b/menu/navigation.json @@ -300,6 +300,10 @@ { "label": "Instances footprint calculation", "slug": "instances-env-footprint" + }, + { + "label": "Block Storage footprint calculation", + "slug": "block-storage-env-footprint" } ], "label": "Additional Content", diff --git a/pages/environmental-footprint/additional-content/bare-metal-env-footprint.mdx b/pages/environmental-footprint/additional-content/bare-metal-env-footprint.mdx index a7cf43076b..ccad9f578e 100644 --- a/pages/environmental-footprint/additional-content/bare-metal-env-footprint.mdx +++ b/pages/environmental-footprint/additional-content/bare-metal-env-footprint.mdx @@ -52,5 +52,5 @@ Therefore 1,62 kgCO2e is added to the total manufacturing impact of this server. To calculate the usage, we consider the French energy mix and the datacenter's PUE. In this example, they are O,056kgCo2e/kwh and 1,16, respectively. Which results in: ```math -UsageFootprint = 0,110 x 100 x 0,056 x 1,16 = 0,715 kgCo2e +UsageFootprint = 0,110 * 100 * 0,056 * 1,16 = 0,715 kgCo2e ``` \ No newline at end of file diff --git a/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx b/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx index fd1b4c1774..a64da6f410 100644 --- a/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx +++ b/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx @@ -7,8 +7,8 @@ content: paragraph: This page explains how Scaleway calculates the environmental footprint of its Block Storage in detail. tags: block-storage environmental-footprint impact datacentre dates: - validation: 2025-07-01 - posted: 2025-07-01 + validation: 2025-07-10 + posted: 2025-07-10 categories: - environmental-footprint - block-storage @@ -26,42 +26,52 @@ The total estimated impact of Block Storage volumes is calculated by integrating ### Ratio per storage volume -To allocate the impact of a Block Storage volume, we apply the unit resulting from the RCP allocation rule to all calculation steps, the `bls_ration`: +To allocate the impact of a Block Storage volume, we apply the unit resulting from the RCP allocation rule to all calculation steps, the `bls_ratio`: ``` -VOLsto/VolstoPool = bls_ratio +bls_ratio = VOLsto/VolstoPool ``` - **VOLsto** - represents the **reserved volume** per user. In Block Storage, your data is replicated three times on multiple nodes to guarantee availability, so the **VOLsto** is applied with factor of 3 to account for replication. - **VolstoPool** - represents all the storage for Block Storage volumes on the server that hosts them (around 60%). +In the example below we consider a **Volsto** of 600 and a **VolstoPool** of 1000. + +``` +bls_ratio = 600/1000 = 0,6 +``` + ### Manufacturing impact -The manufacturing impact of Block Storage volumes is attributed based on the servers that host the storage. +The calculation of the manufacturing impact of Block Storage volumes is based on: + +- The fabrication impact of servers that host user storage +- The fabrication impact of servers used by the Scaleway Block Storage team to manage the service - on both the Control and Data planes + +The calculation is the same used for [measuring the impact of manufacturing for Bare Metal servers](/environmental-footprint/additional-content/environmental-footprint-calculator/#customer-servers), but for Block Storage we also apply the `bls_ratio` to break the impact down to only the allocated volumes. + +#### Calculation example -Considering a server with a lifespan of 6 years (52 560 hours) and power of 110w, for 100 hours and considering via Boavizta estimates that the impact of the manufacturing of this server is 850 kgCo2e, and a `bls_ratio` of we can make the following calculation: +For the example below, we consider a single server with a lifespan of 6 years (52 560 hours) and power of 110w. We measure the impact of 100 hours and consider through [Boavizta estimates](https://www.boavizta.org/) that the impact of the manufacturing of this server is 850 kgCo2e. Also considering a `bls_ratio` of 0,6, we make the following calculation: ``` -VolumeManufacturingImpact = (100 / 52560) * 850 * bls_ratio = [À REMPLIR] kgCO2e +VolumeManufacturingImpact = (100 / 52560) * 850 * 0,6 = 0,97 kgCO2e ``` ### Usage impact -The calculation of the impact of cross-IT equipments takes into consideration the manufacturing and usage impacts of both the control and data plane of the internal Scaleway infrastructure for Block Storage. +The calculation of the usage impact of Block Storage volumes is based on: -- **Control Plane** - Calculate impact as done for Apple Silicon product VMs - hardware and vms -- **Data Plane** - Calculate manufacturing impact via [Boavizta](https://www.boavizta.org/), retrieve electricity consumption estimation and multiply by PUE and energy mix +- The usage of servers that host user storage +- The usage of infrastructure and service management servers by the Scaleway Block Storage team to run the Block Storage service. In this case we consider both the Control and Data planes. +- The impact of the electrical power dedicated to Block Storage across the infrastructure -* The allocation is done **based on electrical power**: we need to retrieve the electrical power dedicated to Block Storage: - * Retrieval of the estimation of the electricity consumption of the Block Storage servers –> [Handbook](https://handbook.scaleway.com/) (static data, like for Elastic Metal). - * Retrieval of the **quantities of hardware of the Data plane**. - * We add the **electricity consumption of the Control Plane VMs**. +To calculate the usage, we consider the French energy mix and the datacenter's PUE. -To calculate the usage, we consider the French energy mix and the datacenter's PUE. In this example, they are O,056kgCo2e/kwh and 1,16, respectively. Which results in: +In the example below, they are O,065kgCo2e/kwh and 1,16, respectively. Considering an electrical consumption of 600wh, 100 hours of usage, and a `bls_ratio` of 0,6, the total usage impact comes down to: ```math -UsageFootprint = 0,110 x 100 x 0,056 x 1,16 = 0,715 kgCo2e +UsageImpact = (0,600 x 0,065) * 100 * 0,6 = 2,34 kgCo2e ``` -### Energy usage impact diff --git a/pages/environmental-footprint/additional-content/environmental-footprint-calculator.mdx b/pages/environmental-footprint/additional-content/environmental-footprint-calculator.mdx index 05eac03a61..8af8b71729 100644 --- a/pages/environmental-footprint/additional-content/environmental-footprint-calculator.mdx +++ b/pages/environmental-footprint/additional-content/environmental-footprint-calculator.mdx @@ -134,6 +134,7 @@ You can find the calculation specifications for each of the available products i - [Bare Metal](/environmental-footprint/additional-content/bare-metal-env-footprint) - [Instances](/environmental-footprint/additional-content/instances-env-footprint) +- [Block Storage](/environmental-footprint/additional-content/block-storage-env-footprint) ### Cross-IT equipment & stock diff --git a/pages/environmental-footprint/additional-content/instances-env-footprint.mdx b/pages/environmental-footprint/additional-content/instances-env-footprint.mdx index 57636c8852..806d07e81b 100644 --- a/pages/environmental-footprint/additional-content/instances-env-footprint.mdx +++ b/pages/environmental-footprint/additional-content/instances-env-footprint.mdx @@ -95,7 +95,7 @@ The allocation of the hypervisor resources for this particular Instance is calcu We multiply the resource allocation by the Instance's lifespan ratio and the hypervisor's manufacturing impact to obtain the manufacturing impact allocated to the Instance: ``` -(100 hours / 52,680 hours) × 100 kgCO2e × 0.425 = 0.080 kgCO2eq +(100 hours / 52,680 hours) * 100 kgCO2e * 0.425 = 0.080 kgCO2eq ``` From eae8cb5191de5c4d344712aadc5c6fa24d18542d Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Thu, 10 Jul 2025 14:53:00 +0200 Subject: [PATCH 05/13] feat(bls): fix ins --- .../additional-content/environmental-footprint-integration.mdx | 1 - 1 file changed, 1 deletion(-) diff --git a/pages/environmental-footprint/additional-content/environmental-footprint-integration.mdx b/pages/environmental-footprint/additional-content/environmental-footprint-integration.mdx index 556dbad95b..b3c712f533 100644 --- a/pages/environmental-footprint/additional-content/environmental-footprint-integration.mdx +++ b/pages/environmental-footprint/additional-content/environmental-footprint-integration.mdx @@ -23,7 +23,6 @@ The following tables provide details about the Scaleway products that currently | CPU Instances | **Yes** | | Block Storage | **Yes** | | Elastic Metal | **Yes** | -| Instances | **Yes** | ## Planned product integration From ea3497b787b251d406884dd0adfb2e5ba53382d8 Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Tue, 15 Jul 2025 10:22:55 +0200 Subject: [PATCH 06/13] fix(efc): reviews elise 1 Co-authored-by: eauvray-github <67907289+eauvray-github@users.noreply.github.com> --- .../block-storage-env-footprint.mdx | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx b/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx index a64da6f410..b95a945b27 100644 --- a/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx +++ b/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx @@ -20,9 +20,9 @@ This page includes the specificities of the environmental footprint calculation The total estimated impact of Block Storage volumes is calculated by integrating the: -- **Manufacturing impact** - Related to the physical servers hosting the storage volumes. +- **Dedicated manufacturing impact** - Related to the physical servers hosting the storage volumes. - **Usage Impact** - The impact of the tools used to manage the Block Storage offers: control plane, monitoring, internal load balancers, and others. -- **Energy usage impact** - The average electricity consumption of storage servers and their energy efficiency. +- **Energy usage impact** - The average electricity consumption of storage servers and their energy efficiency and of the tools used to manage the Block Storage offers. ### Ratio per storage volume @@ -33,9 +33,9 @@ bls_ratio = VOLsto/VolstoPool ``` - **VOLsto** - represents the **reserved volume** per user. In Block Storage, your data is replicated three times on multiple nodes to guarantee availability, so the **VOLsto** is applied with factor of 3 to account for replication. -- **VolstoPool** - represents all the storage for Block Storage volumes on the server that hosts them (around 60%). +- **VolstoPool** - represents the total storage volume reserved for Block Storage. -In the example below we consider a **Volsto** of 600 and a **VolstoPool** of 1000. +In the example below we consider a **Volsto** of 600 GB and a **VolstoPool** of 1000 GB. ``` bls_ratio = 600/1000 = 0,6 @@ -62,11 +62,10 @@ VolumeManufacturingImpact = (100 / 52560) * 850 * 0,6 = 0,97 kgCO2e The calculation of the usage impact of Block Storage volumes is based on: -- The usage of servers that host user storage -- The usage of infrastructure and service management servers by the Scaleway Block Storage team to run the Block Storage service. In this case we consider both the Control and Data planes. -- The impact of the electrical power dedicated to Block Storage across the infrastructure +- Impact of electricity consumption of servers that host user storage +- Impact of electricity consumption of infrastructure and service management servers by the Scaleway Block Storage team to run the Block Storage service. In this case we consider both the Control and Data planes. -To calculate the usage, we consider the French energy mix and the datacenter's PUE. +To calculate the impact of a kwh, we consider the French energy mix and the datacenter's PUE. In the example below, they are O,065kgCo2e/kwh and 1,16, respectively. Considering an electrical consumption of 600wh, 100 hours of usage, and a `bls_ratio` of 0,6, the total usage impact comes down to: From 22de9134f9cbfc8bfcb84da5d84c4db9885028e0 Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Tue, 15 Jul 2025 10:26:47 +0200 Subject: [PATCH 07/13] feat(efc): review elise 2 --- .../additional-content/block-storage-env-footprint.mdx | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx b/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx index b95a945b27..8e83421719 100644 --- a/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx +++ b/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx @@ -21,7 +21,7 @@ This page includes the specificities of the environmental footprint calculation The total estimated impact of Block Storage volumes is calculated by integrating the: - **Dedicated manufacturing impact** - Related to the physical servers hosting the storage volumes. -- **Usage Impact** - The impact of the tools used to manage the Block Storage offers: control plane, monitoring, internal load balancers, and others. +- **Related manufacturing impact** - The impact of the tools used to manage the Block Storage offers: control plane, monitoring, internal load balancers, and others. - **Energy usage impact** - The average electricity consumption of storage servers and their energy efficiency and of the tools used to manage the Block Storage offers. ### Ratio per storage volume @@ -58,6 +58,8 @@ For the example below, we consider a single server with a lifespan of 6 years (5 VolumeManufacturingImpact = (100 / 52560) * 850 * 0,6 = 0,97 kgCO2e ``` +In the example, the dedicated manufacturing impact of a 600 GB usage for 100 hours is 0,97 kgCo2e. + ### Usage impact The calculation of the usage impact of Block Storage volumes is based on: @@ -73,4 +75,5 @@ In the example below, they are O,065kgCo2e/kwh and 1,16, respectively. Consideri UsageImpact = (0,600 x 0,065) * 100 * 0,6 = 2,34 kgCo2e ``` +In the example, the usage impact of a 600 GB usage for 100 hours is 2,34 kgCo2e. From aeb25a486da9d37037859b328b09cac8659981f5 Mon Sep 17 00:00:00 2001 From: numa Date: Wed, 16 Jul 2025 15:31:39 +0200 Subject: [PATCH 08/13] Update bare-metal-env-footprint.mdx update frontmatter --- .../additional-content/bare-metal-env-footprint.mdx | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/pages/environmental-footprint/additional-content/bare-metal-env-footprint.mdx b/pages/environmental-footprint/additional-content/bare-metal-env-footprint.mdx index ccad9f578e..341b61aca3 100644 --- a/pages/environmental-footprint/additional-content/bare-metal-env-footprint.mdx +++ b/pages/environmental-footprint/additional-content/bare-metal-env-footprint.mdx @@ -1,10 +1,6 @@ --- -meta: - title: Bare Metal footprint calculation - description: This page explains how Scaleway calculates the environmental footprint of its Bare Metal servers in detail. -content: - h1: Bare Metal footprint calculation - paragraph: This page explains how Scaleway calculates the environmental footprint of its Bare Metal servers in detail. +title: Bare Metal footprint calculation +description: This page explains how Scaleway calculates the environmental footprint of its Bare Metal servers in detail. tags: bare-metal environmental-footprint impact datacentre dates: validation: 2025-05-27 @@ -53,4 +49,4 @@ To calculate the usage, we consider the French energy mix and the datacenter's P ```math UsageFootprint = 0,110 * 100 * 0,056 * 1,16 = 0,715 kgCo2e -``` \ No newline at end of file +``` From 415d95b67266cbd7391123f0bbb047522d3780f0 Mon Sep 17 00:00:00 2001 From: numa Date: Wed, 16 Jul 2025 15:32:01 +0200 Subject: [PATCH 09/13] Update block-storage-env-footprint.mdx update frontmatter --- .../additional-content/block-storage-env-footprint.mdx | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx b/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx index 8e83421719..1cc93bd27f 100644 --- a/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx +++ b/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx @@ -1,10 +1,6 @@ --- -meta: - title: Block Storage footprint calculation - description: This page explains how Scaleway calculates the environmental footprint of its Block Storage in detail. -content: - h1: Block Storage footprint calculation - paragraph: This page explains how Scaleway calculates the environmental footprint of its Block Storage in detail. +title: Block Storage footprint calculation +description: This page explains how Scaleway calculates the environmental footprint of its Block Storage in detail. tags: block-storage environmental-footprint impact datacentre dates: validation: 2025-07-10 From f4a7f6c1c94d8bb29fb14de9afe588e068933f4c Mon Sep 17 00:00:00 2001 From: numa Date: Wed, 16 Jul 2025 15:32:27 +0200 Subject: [PATCH 10/13] Update environmental-footprint-calculator.mdx update frontmatter --- .../environmental-footprint-calculator.mdx | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/pages/environmental-footprint/additional-content/environmental-footprint-calculator.mdx b/pages/environmental-footprint/additional-content/environmental-footprint-calculator.mdx index 8af8b71729..5f906cfc02 100644 --- a/pages/environmental-footprint/additional-content/environmental-footprint-calculator.mdx +++ b/pages/environmental-footprint/additional-content/environmental-footprint-calculator.mdx @@ -1,10 +1,6 @@ --- -meta: - title: Environmental Footprint calculation breakdown - description: This page explains how Scaleway calculates the environmental footprint of its products and services in detail. -content: - h1: Environmental Footprint calculation breakdown - paragraph: This page explains how Scaleway calculates the environmental footprint of its products and services in detail. +title: Environmental Footprint calculation breakdown +description: This page explains how Scaleway calculates the environmental footprint of its products and services in detail. tags: environmental-footprint impact environment datacentre dates: validation: 2025-03-17 From 7031f1bb8695c1be2d539e93850417d3f102557f Mon Sep 17 00:00:00 2001 From: numa Date: Wed, 16 Jul 2025 15:32:53 +0200 Subject: [PATCH 11/13] Update environmental-footprint-integration.mdx update frontmatter --- .../environmental-footprint-integration.mdx | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/pages/environmental-footprint/additional-content/environmental-footprint-integration.mdx b/pages/environmental-footprint/additional-content/environmental-footprint-integration.mdx index b3c712f533..a67ff8f741 100644 --- a/pages/environmental-footprint/additional-content/environmental-footprint-integration.mdx +++ b/pages/environmental-footprint/additional-content/environmental-footprint-integration.mdx @@ -1,10 +1,6 @@ --- -meta: - title: Environmental footprint calculator product integration - description: Discover the Scaleway Products that integrate the Environmental Footprint calculator. -content: - h1: Environmental footprint calculator product integration - paragraph: Discover the Scaleway Products that integrate the Environmental Footprint calculator. +title: Environmental footprint calculator product integration +description: Discover the Scaleway Products that integrate the Environmental Footprint calculator. tags: environmental-footprint calculator dates: validation: 2025-01-14 From 2760768b4a98bb5c7f40a9f3ab1923cebbbfbd78 Mon Sep 17 00:00:00 2001 From: numa Date: Wed, 16 Jul 2025 15:33:21 +0200 Subject: [PATCH 12/13] Update instances-env-footprint.mdx update frontmatter --- .../additional-content/instances-env-footprint.mdx | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/pages/environmental-footprint/additional-content/instances-env-footprint.mdx b/pages/environmental-footprint/additional-content/instances-env-footprint.mdx index 806d07e81b..2ee2bfc382 100644 --- a/pages/environmental-footprint/additional-content/instances-env-footprint.mdx +++ b/pages/environmental-footprint/additional-content/instances-env-footprint.mdx @@ -1,10 +1,6 @@ --- -meta: - title: Instances footprint calculation - description: This page explains how Scaleway calculates the environmental footprint of its Instances in detail. -content: - h1: Instances footprint calculation - paragraph: This page explains how Scaleway calculates the environmental footprint of its Instances in detail. +title: Instances footprint calculation +description: This page explains how Scaleway calculates the environmental footprint of its Instances in detail. tags: instances environmental-footprint impact cloud-computing dates: validation: 2025-05-27 From 29d6a3a0d4790aa3b8ac00d585fb9ca58272afa6 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Wed, 16 Jul 2025 17:29:46 +0200 Subject: [PATCH 13/13] Apply suggestions from code review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Néda <87707325+nerda-codes@users.noreply.github.com> --- .../additional-content/block-storage-env-footprint.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx b/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx index 1cc93bd27f..1e2859d64f 100644 --- a/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx +++ b/pages/environmental-footprint/additional-content/block-storage-env-footprint.mdx @@ -31,7 +31,7 @@ bls_ratio = VOLsto/VolstoPool - **VOLsto** - represents the **reserved volume** per user. In Block Storage, your data is replicated three times on multiple nodes to guarantee availability, so the **VOLsto** is applied with factor of 3 to account for replication. - **VolstoPool** - represents the total storage volume reserved for Block Storage. -In the example below we consider a **Volsto** of 600 GB and a **VolstoPool** of 1000 GB. +In the example below we consider a **VOLsto** of 600 GB and a **VolstoPool** of 1000 GB. ``` bls_ratio = 600/1000 = 0,6 @@ -41,14 +41,14 @@ bls_ratio = 600/1000 = 0,6 The calculation of the manufacturing impact of Block Storage volumes is based on: -- The fabrication impact of servers that host user storage -- The fabrication impact of servers used by the Scaleway Block Storage team to manage the service - on both the Control and Data planes +- The manufacturing impact of servers that host user storage +- The manufacturing impact of servers used by the Scaleway Block Storage team to manage the service - on both the Control and Data planes The calculation is the same used for [measuring the impact of manufacturing for Bare Metal servers](/environmental-footprint/additional-content/environmental-footprint-calculator/#customer-servers), but for Block Storage we also apply the `bls_ratio` to break the impact down to only the allocated volumes. #### Calculation example -For the example below, we consider a single server with a lifespan of 6 years (52 560 hours) and power of 110w. We measure the impact of 100 hours and consider through [Boavizta estimates](https://www.boavizta.org/) that the impact of the manufacturing of this server is 850 kgCo2e. Also considering a `bls_ratio` of 0,6, we make the following calculation: +For the example below, we consider a single server with a lifespan of 6 years (52 560 hours) and power of 110w. We measure the impact of 100 hours and consider through [Boavizta estimates](https://www.boavizta.org/) that the impact of the manufacturing of this server is 850 kgCo2e. Also considering a `bls_ratio` of `0,6`, we make the following calculation: ``` VolumeManufacturingImpact = (100 / 52560) * 850 * 0,6 = 0,97 kgCO2e @@ -65,7 +65,7 @@ The calculation of the usage impact of Block Storage volumes is based on: To calculate the impact of a kwh, we consider the French energy mix and the datacenter's PUE. -In the example below, they are O,065kgCo2e/kwh and 1,16, respectively. Considering an electrical consumption of 600wh, 100 hours of usage, and a `bls_ratio` of 0,6, the total usage impact comes down to: +In the example below, they are O,065kgCo2e/kwh and 1,16, respectively. Considering an electrical consumption of 600wh, 100 hours of usage, and a `bls_ratio` of `0,6`, the total usage impact comes down to: ```math UsageImpact = (0,600 x 0,065) * 100 * 0,6 = 2,34 kgCo2e