Bouncer/Sentry Requirements

From MozillaWiki
Jump to: navigation, search


  • mirrors dropping in and out under high load and we're not able to adjust it automatically
    • need to be able to see that this is happening
    • drop weight down until the mirror stops the behavior
      • and supporting code to take care of this half in in the production branch --Justdave 07:52, 7 August 2009 (UTC)
  • consolidate different branches and get trunk up-to-date
  • sentry sees something as slow from SJC but for remote centers it works fine
    • override a mirror so sentry can't pull it
    • adjust what we deem as "slow" by using relative latency
    • deploy a sentry system that has multiple instances that are local
    • use virtual machines in other countries
    • The above were wild ideas we've had at certain points. --Justdave 07:52, 7 August 2009 (UTC)
      • GeoIP locating and monitoring from multiple locations will probably be the best solution for this.
      • Adjust the Geolocation targets for each mirror based on where it tests best from, for example.
      • Many mirrors have massive amounts of bandwidth available within their own country, but have international bandwidth restrictions, need to be able to restrict foreign traffic in these cases.
  • files that don't exist are wrongly offered to users
    • sentry does not check for locales
      • hacked on the production branch to check for the last locale in the rsync for each product, would be better to individually check them all --Justdave 07:52, 7 August 2009 (UTC)
  • md5 sum hash-checking using byte-ranges
  • need to check that all files are served with the correct mime types
  • set up a login system to allow mirror admins to be able to log in to admin screens
  • they would see only information they were allowed to see via ACL
  • email mirror contact if sentry pull out a mirror - bug 457609
  • - re-use their stuff or use ours?
  • sourceforge-like download "credit" - mirror icons
  • rewrite admin tools to be more user-friendly