Retrieve the overall impacts of a cloud instance

[da-ekchajzer]

Problem

In cloud environments, an instance is a layer of abstraction for multiple resources :

• Client allocated corresponding to the resources paid by the client
• CSP & control plane corresponding to the computing power used to monitor, secure and orchestrate the resources
• unalocated ressources resulting from :
  • the need for redundancy. In that case, unallocated resources depends on the number of redundancy and the number of datacenters. If two datacenters are available, redundancy will use 50% of the potential compute resources in order to back up each other. If three datacenters are available, redundancy will use 33% of the potential compute resources.
  • the lack of optimization.
• Support equipment corresponding to the cooling and other overhead that supports the compute resources.

Today, cloud instances impacts are measured based exclusively on the impacts of Client allocated resources. We should be able to retrieve the overall impacts of a cloud instance.

Solution

client_allocated_impacts

Already implemented #29

unalocated_ressources_impacts

Scope 3 = client_allocated_impacts*(1/nb_redondancy_datacenter) Scope 2 = client_allocated_impacts(IDLE)/nb_redondancy_datacenter

Only redundancy is taken in consideration, we should also consider unaffected resources waiting for clients.

CSP_control_plane_impacts

• Those resources could be measure as function of the overall resources, i.e the resources represent X% of the compute power of a cloud provider, the impact represent X% of the impacts :

Scope 3 = ((unalocated_ressources_impacts + client_allocated_impacts) * X)/100-X Scope 2 = ((unalocated_ressources_impacts + client_allocated_impacts) * X)/100-X

• In reality, those resources are not linearly dependent on the client load but on the overall quantity of load. Since unalocated_ressources_impacts is dependent on the client load this approach will make CSP_control_plane_impacts also dependent on the client load. Another approach would be to allocate a fix impact per instance :

Scope 3 = fix_impact_per_instance Scope 2 = fix_impact_per_instance

Support equipments

Scope 2 = (compute_impact * PUE) / compute_impact

Scope 3 = ?

[da-ekchajzer]

@JacobValdemar @AirLoren we have done some work on the topic already there.

The main missing data would be the data for “support equipment Scope 3” (which should be renamed to embedded).