3,035
edits
Bouncer/Sentry Requirements: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(New page: = Must-haves = == Q4 2008 == * logging of mirror status over time * md5 sum hash-checking using byte-ranges * consolidate different branches and get trunk up-to-date * add more here == Q1 ...) |
No edit summary |
||
| Line 1: | Line 1: | ||
= Must-haves = | = Must-haves = | ||
== Q4 2008 == | == Q4 2008 == | ||
* | * 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 | |||
* consolidate different branches and get trunk up-to-date | * consolidate different branches and get trunk up-to-date | ||
== Q1 2009 == | == Q1 2009 == | ||
= | * 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 | |||
* files that don't exist are wrongly offered to users | |||
** sentry does not check for locales | |||
* md5 sum hash-checking using byte-ranges | |||
= 2009 Notes = | |||
* 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 - 457609 | |||
* peeringdb.com - re-use their stuff or use ours? | |||
* sourceforge-like download "credit" - mirror icons | |||
* rewrite admin tools to be more user-friendly | |||