Repository navigation
fcvm-fleet: raise G Spot quota in us-east-1 to 480 vCPU for the prod stack (closes #913) - #937
Conversation
…stack (#913) Production's two awake g4dn.metal hosts take 192 vCPU, which is the whole current quota. A Spot interruption notice launches a replacement (96) while the reclaimed host drains. Staging's host (96) and an image-factory build host (96) share the region. Together that is 480. The resource already files max(local, current), so the apply requests 480 and never lowers it. Tested: python3 -S -B scripts/test-fcvm-fleet-account.py (OK, with the test renamed to 480); terraform 1.10.3 fmt -check.
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 56 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
@coderabbitai review Please review the us-east-1 G Spot quota change on 8aaeaf5. The standing quota request only changes the account ceiling. |
Action not completed
|
Closes #913.
local.fcvm_fleet_spot_g_vcpusgoes from 192 to 480 vCPU. Production's two awake g4dn.metal hosts already take all 192.The 480 covers four users of the quota at once:
aws_servicequotas_service_quota.fcvm_fleet_spot_g_east1already filesmax(local, current), so the apply requests 480 and never lowers the quota. AWS may take time to grant it.Tested:
python3 -S -B scripts/test-fcvm-fleet-account.py(OK) and terraform 1.10.3fmt -check.