Cloud instances
Characteristics
In addition to the characteristics available for a server, you can use the following:
Name | Unit | Default value | Description | Example |
---|---|---|---|---|
usage | None | See cloud usage | .. |
Cloud usage
In addition to the characteristics available for server usage, you can use the following:
Name | Unit | Default value | Description | Example |
---|---|---|---|---|
instance_per_server | None | None | See usage | 10 |
hours_life_time | hours | 35040 | Lifespan of the cloud element | 2 |
use_time_ratio | /1 | 1 | Proportion of time the device is used during the given duration. | 0.5 |
Embedded impacts
Impacts criteria
Criteria | Implemented | Source |
---|---|---|
gwp | yes | Bottom-up approach based on Green Cloud Computing, 2021 |
adp | yes | Bottom-up approach based on Green Cloud Computing, 2021 |
pe | yes | Bottom-up approach based on Green Cloud Computing, 2021 |
gwppb | yes | Base IMPACTS® ADEME |
gwppf | yes | Base IMPACTS® ADEME |
gwpplu | yes | Base IMPACTS® ADEME |
ir | yes | Base IMPACTS® ADEME |
lu | yes | Base IMPACTS® ADEME |
odp | yes | Base IMPACTS® ADEME |
pm | yes | Base IMPACTS® ADEME |
pocp | yes | Base IMPACTS® ADEME |
wu | yes | Base IMPACTS® ADEME |
mips | yes | Base IMPACTS® ADEME |
adpe | yes | Base IMPACTS® ADEME |
adpf | yes | Base IMPACTS® ADEME |
ap | yes | Base IMPACTS® ADEME |
ctue | yes | Base IMPACTS® ADEME |
ctuh_c | yes | Base IMPACTS® ADEME |
ctuh_nc | yes | Base IMPACTS® ADEME |
epf | yes | Base IMPACTS® ADEME |
epm | yes | Base IMPACTS® ADEME |
ept | yes | Base IMPACTS® ADEME |
Method
Embedded impacts of cloud instances correspond to the impact of the physical server hosting the instance divided by the number of instances hosted on the server.
\[
\text{cloud_instance}_\text{embedded}^\text{criteria} = \frac{\text{server}_
\text{embedded}^\text{criteria}}{\text{instances_per_server}}
\]
Components configuration are never sent by the user but pre-recorded as an archetype.
Usage impacts
Usage impact of cloud instance are measured only from its consumption profile.
As for embedded, usage impacts for a physical server are divided into the number of instances hosted by the server.
Consumption profile
We use the same process as described for the servers .