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

Add txcontroller max-rate rules for 40Gbps uplinks #349

Merged
merged 1 commit into from
Oct 4, 2024
Merged

Conversation

nkinkade
Copy link
Contributor

@nkinkade nkinkade commented Oct 4, 2024

The new Ziply sites have 40Gbps uplinks. This sets the max-rates to 10Gbps for regular "full" sites, and 30Gbps for "minimal" sites.


This change is Reviewable

The new Ziply sites have 40Gbps uplinks.
Copy link
Contributor

@stephen-soltesz stephen-soltesz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewable status: 0 of 1 approvals obtained (waiting on @nkinkade)


lib/site.jsonnet line 204 at r1 (raw file):

      if subnet == 26 then
        // 10Gbits/s
        10000000000

Can you say more about this branch? There's something I'm missing.

Is Zipply running a standard configuration site (e.g. /26) with 40G switches? Why would we not want this condition to be 30Gbps?

Copy link
Contributor Author

@nkinkade nkinkade left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewable status: 0 of 1 approvals obtained (waiting on @stephen-soltesz)


lib/site.jsonnet line 204 at r1 (raw file):

Previously, stephen-soltesz (Stephen Soltesz) wrote…

Can you say more about this branch? There's something I'm missing.

Is Zipply running a standard configuration site (e.g. /26) with 40G switches? Why would we not want this condition to be 30Gbps?

@stephen-soltesz : This is just following our "standard" convention of setting the max-rate for the tx-controller to 1/4 of the uplink speed for "full" sites, and 3/4 of the uplink speed for "minimal" sites.

Yeah, Ziply is deploying full sites, with 4 Dell R630 servers (connected to the switch at 40Gbps), and 1 Juniper QFX switch (with a 40Gbps) uplink to Ziply's network.

Did I do my math wrong, or so we need another strategy for this type of site?

Copy link
Contributor

@stephen-soltesz stephen-soltesz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed 1 of 1 files at r1.
Reviewable status: :shipit: complete! 1 of 1 approvals obtained (waiting on @nkinkade)


lib/site.jsonnet line 204 at r1 (raw file):

Previously, nkinkade wrote…

@stephen-soltesz : This is just following our "standard" convention of setting the max-rate for the tx-controller to 1/4 of the uplink speed for "full" sites, and 3/4 of the uplink speed for "minimal" sites.

Yeah, Ziply is deploying full sites, with 4 Dell R630 servers (connected to the switch at 40Gbps), and 1 Juniper QFX switch (with a 40Gbps) uplink to Ziply's network.

Did I do my math wrong, or so we need another strategy for this type of site?

No this is right. For some reason, my brain didn't go to the 3xNode capacity - lgtm

@nkinkade nkinkade merged commit 97353f0 into main Oct 4, 2024
3 checks passed
@nkinkade nkinkade deleted the sandbox-kinkade branch October 4, 2024 19:17
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

Successfully merging this pull request may close these issues.

2 participants