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

Unclear repetition #34

Open
abersnaze opened this issue Mar 1, 2022 · 1 comment
Open

Unclear repetition #34

abersnaze opened this issue Mar 1, 2022 · 1 comment

Comments

@abersnaze
Copy link
Contributor

I'm working on summarizing the cost, cpu, disk (local & attached) for both regional and zonal clusters. I want there to be more consistency in the way repetition is represented.

us-east-1: # trimmed
us-west-2:
  least_regret:
    - candidate_clusters:
        total_annual_cost: # redacted
        zonal:
          - cluster_type: cassandra # trimmed
          - cluster_type: cassandra # trimmed
          - cluster_type: cassandra # trimmed
        regional:
          - cluster_type: dgwkv
            total_annual_cost: # redacted
            count: 3
            instance:
              total_annual_cost: # redacted
              name: r5.large
            attached_drives:
              - name: gp2
                size_gib: 20
                annual_cost_per_gib: # redacted
                annual_cost_per_read_io: # redacted
                annual_cost_per_write_io: # redacted

In the sample above there are:

  • enumerated list of regions
  • duplicated zonals
  • instance with a count property
@jolynch
Copy link
Contributor

jolynch commented Mar 9, 2022

Yeah the tricky part is that regions may have two or more zones, and some services deploy regionally (in which case it's usually a single cluster) or zonally (in which case its O(n) clusters where n = that regions number of zones). I chose the most compact representation I could figure out that accurately describes all possible deployments. Feel free to improve it if you can (just remember that there are variable size of cluster per zone [e.g. in leader-follower dbs] and different cluster types, and possibly multiple clusters of the same cluster type (e.g. a metadata db and a data plane db of the same type).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants