Bug #15687
Have lizard plugged to a Gbps switch
100%
Description
Goal: lower the time it takes for mirrors to pick up newly uploaded ISO and IUKs during our release process.
Once this is done, we shall remove the network bandwidth cap we’ve set for rsync.lizard.
Subtasks
Related issues
Related to Tails - |
Resolved | 2018-01-10 |
History
#1 Updated by intrigeri 2018-06-27 08:16:03
As reported on Bug #15162, this seems to be doable. The exact timeline is unclear yet.
#2 Updated by intrigeri 2018-06-27 08:16:30
- Description updated
#3 Updated by intrigeri 2018-06-27 08:17:04
- related to
Bug #15162: Remove rsync.torproject.org from the mirrors synchronization chain added
#4 Updated by intrigeri 2018-09-06 13:19:00
- Target version changed from Tails_3.10.1 to Tails_3.11
I’ve pinged those who can make this happen.
#5 Updated by intrigeri 2018-09-18 13:37:06
- Target version changed from Tails_3.11 to Tails_3.10.1
- % Done changed from 10 to 50
Done! I’ve removed the bandwidth cap and added an ISO to the rsync shared directory to see how it fares when actual mirrors download from it.
#6 Updated by intrigeri 2018-09-18 13:37:17
- QA Check set to Ready for QA
#7 Updated by intrigeri 2018-09-18 14:59:58
- Status changed from In Progress to Resolved
- Assignee deleted (
intrigeri) - % Done changed from 50 to 100
- QA Check deleted (
Ready for QA)
1.5h later, all mirrors but 3 have sync’ed. Max outgoing recorded traffic was 113.58 MByte/s :) Many mirrors have too slow connection to lizard to fully benefit from the increased transfer rates, but at least our own pipe is not congested anymore by 10 concurrent downloads, because most downloads take ~1 minute. So I think we’re done here.
The 3 remaining mirrors haven’t even tried to sync AFAICT, which I’ll report to our mirror pool maintenance team.
#8 Updated by intrigeri 2018-10-01 13:29:41
- Target version changed from Tails_3.10.1 to Tails_3.9.1