Open da-ekchajzer opened 1 year ago
V0.3 will introduce a new format for server instances.
id | manufacturer | CASE.case_type | year | CPU.units | CPU.core_units | CPU.name | CPU.manufacturer | CPU.model_range | CPU.family | CPU.tdp | CPU.manufacture_date | RAM.capacity | RAM.units | SSD.units | SSD.capacity | HDD.units | HDD.capacity | POWER_SUPPLY.units | GPU.memory | GPU.memory | GPU.units | POWER_SUPPLY.units | POWER_SUPPLY.unit_weight | USAGE.instance_per_server | USAGE.time_workload | USAGE.use_time | USAGE.years_life_time | USAGE.other_consumption_ratio | USAGE.overcommited | Warnings |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
xyz | GCP | rack | 2018 | 1 | 16 | Xeon E5-2651 v2 | 40 | 2018 | 16 | 2 | 0 | 0 | 0 | 2 | 2;2;2 | 2.99;1;5 | 2 | 50;0;100 | 8760 | 35040 | 0.33;0.2;0.6 | 0 |
Note that in case an instance has multiple type of components, you can put : default;min;max
Adding new cloud providers and new cloud instance should now follow this process : https://doc.api.boavizta.org/contributing/cloud_provider/
Problem
As we did for AWS (https://boavizta.github.io/boaviztapi/Explanations/devices/cloud/) we should be able to retrieve the impacts of GCP instances.
Solution
The same implementation as AWS instances.
Additional context or elements
We should gather data on GCP instance's hardware.
Format