Skip to content

feat(efc): bls MTA-6233 #5257

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

feat(efc): bls MTA-6233 #5257

wants to merge 5 commits into from

Conversation

ldecarvalho-doc
Copy link
Contributor

No description provided.

@ldecarvalho-doc ldecarvalho-doc self-assigned this Jul 10, 2025
@ldecarvalho-doc ldecarvalho-doc added type: new content New pages or categories status: tech review Waiting for technical review priority: medium Maintenance PRs to fix several visible mistakes status: doc review Waiting for doc team review labels Jul 10, 2025
@ldecarvalho-doc ldecarvalho-doc changed the title Mta 6233 feat(efc): bls MTA-6233 Jul 10, 2025

The total estimated impact of Block Storage volumes is calculated by integrating the:

- **Manufacturing impact** - Related to the physical servers hosting the storage volumes.
Copy link

@eauvray-github eauvray-github Jul 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- **Manufacturing impact** - Related to the physical servers hosting the storage volumes.
- **Dedicated manufacturing impact** - Related to the physical servers hosting the storage volumes.

The total estimated impact of Block Storage volumes is calculated by integrating the:

- **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.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- **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.


- **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.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- **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.

```

- **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%).

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- **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 the block storage product.

- **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.
Copy link

@eauvray-github eauvray-github Jul 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.


The calculation of the usage impact of Block Storage volumes is based on:

- The usage of servers that host user storage

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- The usage of servers that host user storage
- Impact of electricity consumption of servers that host user storage

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.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- 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.
- 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.


- 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

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- The impact of the electrical power dedicated to Block Storage across the infrastructure

- 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

To calculate the usage, we consider the French energy mix and the datacenter's PUE.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.

```math
UsageImpact = (0,600 x 0,065) * 100 * 0,6 = 2,34 kgCo2e
```

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can also add a conclusion here

@ldecarvalho-doc ldecarvalho-doc added the do not merge PR that shouldn't be merged before a specific date (eg release) label Jul 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do not merge PR that shouldn't be merged before a specific date (eg release) priority: medium Maintenance PRs to fix several visible mistakes status: doc review Waiting for doc team review status: tech review Waiting for technical review type: new content New pages or categories
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants