Cap ISO upload bandwidth #75
No reviewers
Labels
No labels
bug
dependencies
documentation
duplicate
enhancement
github_actions
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
monolith-os/monolith!75
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "iso-upload-cap"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
ISO uploads go straight at the forge host over the direct (grey-cloud) route, sharing that box's connection with everything else it serves, and ISO dispatches happen whenever needed rather than just on the monthly schedule. Add --limit-rate to the release-asset curl, set from a documented UPLOAD_BWLIMIT env (12M per upload, ~100 Mbit/s; worst case ~400 Mbit/s with all 4 runner slots uploading).
This only covers the ISO workflow. The nightly image pushes are skopeo with no rate knob, so those get paced with traffic shaping on the runner host instead.
24d932e0c1d55a85f42dCap ISO upload bandwidth toward webnxto Cap ISO upload bandwidth