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

Provide estimations related to storage #272

Closed
demeringo opened this issue May 22, 2023 · 3 comments
Closed

Provide estimations related to storage #272

demeringo opened this issue May 22, 2023 · 3 comments
Assignees
Labels
draft feature draft feature enhancement New feature or request help wanted Extra attention is needed
Milestone

Comments

@demeringo
Copy link
Collaborator

demeringo commented May 22, 2023

Problem

Current cloud scanner does not take into account storage requirements.

Solution

Boavizta API provides data related to HDD / SSD, we could define a way to estimate the impacts of cloud resources related to storage.

Idea, similarly to what is done with the instances, retrieve impacts(type of storage / volume).

  • Without detailled information from cloud providers, this means that we have to decide which storage archetype (or characteristics) from Boavizta API we want to map to a given storage type of the cloud provider.
  • This mean also that we are likely to under-estimate the impacts (as we do not account for the control plan of storage)
  • Decide if we count the "ordered capacity" (easier) or the "used capacity" of storage (more realistic, depending on storage type).

Object storage (like s3) will be implemented in a separate feature: #336

Alternatives

Additional context or elements

@demeringo demeringo added enhancement New feature or request help wanted Extra attention is needed draft feature draft feature labels May 22, 2023
@demeringo
Copy link
Collaborator Author

See #205

@demeringo demeringo added this to the 0.4.x milestone Jul 24, 2023
@demeringo
Copy link
Collaborator Author

demeringo commented Jul 24, 2023

This should be split into 2 workstreams (and maybe 3 issues)

  • VM disks
    • inventory of disks attached to VM
    • get estimations for disks
  • S3 BUCKETS (in a separate feature Provide estimation of impact of S3 storage #336 )
    • inventory of S3 buckets (may require differents permissions)
    • get estimations for buckets

@demeringo
Copy link
Collaborator Author

Verbose output fails when used in conjunction with the include_block_storage option:

See cargo run estimate -b -u 1 --output-verbose-json |jq

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
draft feature draft feature enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant