Closed Bug 607748 Opened 14 years ago Closed 13 years ago

make mirror saturation take less time

Categories

(Release Engineering :: General, defect, P4)

All
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Unassigned)

References

Details

There's lots of different ways we could make mirror saturation faster, and we should do it. Some ideas:
- Do candidates directory -> releases rsync directly on dm-ftp01, instead of over an NFS mount
- Stage releases directory somewhere hidden/inaccessible ahead of time, and move it to the final location when we "go to mirrors"
- Pre-populate the mirrors with hidden/inaccessible files, and flip them on when we "go to mirrors" (this would depend on stricter mirror configuration requirements)
IT recently made a change that allows us to push out to Mozilla mirrors well in advance of a release. We haven't used it yet, but depending on how it goes we may not care to do anything more here.
I think we've done enough to call this FIXED. We always pre-seed the internal mirrors these days, and with 9.0.1, we managed to get good uptake on the full network in about 2 hours.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.