|
| 1 | +--- |
| 2 | +meta: |
| 3 | + title: Block Storage footprint calculation |
| 4 | + description: This page explains how Scaleway calculates the environmental footprint of its Block Storage in detail. |
| 5 | +content: |
| 6 | + h1: Block Storage footprint calculation |
| 7 | + paragraph: This page explains how Scaleway calculates the environmental footprint of its Block Storage in detail. |
| 8 | +tags: block-storage environmental-footprint impact datacentre |
| 9 | +dates: |
| 10 | + validation: 2025-07-01 |
| 11 | + posted: 2025-07-01 |
| 12 | +categories: |
| 13 | + - environmental-footprint |
| 14 | + - block-storage |
| 15 | +--- |
| 16 | + |
| 17 | +This page includes the specificities of the environmental footprint calculation for Block Storage. |
| 18 | + |
| 19 | +## Resources used for estimation |
| 20 | +The main unit taken into account in the Block Storage footprint estimation is **VOLsto**, which represents the **reserved volume** per user. |
| 21 | + |
| 22 | +The total estimated impact is calculated by integrating: |
| 23 | + |
| 24 | +- **Manufacturing impact** - Related to the physical servers hosting the storage volumes. |
| 25 | +- **Shared infrastructure impact** - The impact of the tools used to manage the Block Storage offers: control plane, monitoring, internal load balancers, and others. |
| 26 | +- **Energy usage impact** - The average electricity consumption of storage servers and their energy efficiency. |
| 27 | + |
| 28 | +## Calculation aspects |
| 29 | + |
| 30 | +### Ratio per storage volume |
| 31 | +To allocate the impact of a specific storage volume, we apply the following RCP allocation rule: |
| 32 | + |
| 33 | +- Attribution of the manufacturing impact to **VOLsto**: with a **factor of 3 to account for replication**. |
| 34 | +We use this ratio in the rest of the calculations. |
| 35 | + |
| 36 | +### Manufacturing impact |
| 37 | +The manufacturing impact is attributed based on the servers hosting the storage: |
| 38 | + |
| 39 | +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). |
| 40 | + |
| 41 | +### Shared infrastructures |
| 42 | +| Component | Description | Hardware | Manufacturing & Usage | |
| 43 | +| --- | --- | --- | --- | |
| 44 | +| 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 | |
| 45 | +| 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 | |
| 46 | + |
| 47 | +* The allocation is done **based on electrical power**: we need to retrieve the electrical power dedicated to Block Storage: |
| 48 | + * Retrieval of the estimation of the electricity consumption of the Block Storage servers –> [Handbook](https://handbook.scaleway.com/) (static data, like for Elastic Metal). |
| 49 | + * Retrieval of the **quantities of hardware of the Data plane**. |
| 50 | + * We add the **electricity consumption of the Control Plane VMs**. |
0 commit comments