Skip to content
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

The impacts of storage may be counted twice for some instances (to be confirmed) #556

Open
demeringo opened this issue Jul 11, 2024 · 0 comments
Labels
documentation Improvements or additions to documentation question Further information is requested

Comments

@demeringo
Copy link
Collaborator

demeringo commented Jul 11, 2024

In the general case, Cloud scanner perform a separate inventory of instances and block storage.

When estimating impacts, CS adds the impacts of instance and block storage.

In Boavizta API The archetype of most aws instances are configured with a zero sized storage, so counting separately (and summing) the impacts of instances and storage is not an issue. Example: a1.4xlarge

See the definition of aws archetypes here: https://github.com/Boavizta/boaviztapi/blob/main/boaviztapi/data/archetypes/cloud/aws.csv

Howether, some instances are configured with non zero sotrage in Boavizta API. Example: c1.medium

We should investigate if this does not lead to double accounting of the storage.

@demeringo demeringo added documentation Improvements or additions to documentation question Further information is requested labels Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant