Bouncer:v3

Revision as of 22:47, 20 June 2006 by Preed (talk | contribs) (Preed's list of requirements)

« back to Bouncer home

Schedule

Database

  • Renaming of tables
  • Renaming of columns
  • Verify indexing
  • geo-ip
    • load test set from maxgeo
    • map onto existing regions?
  • Fix SQL for *.py (sentry, loader)
  • Roles (Admin vs. User vs. Reports)

CRUD

  • Scaffold current models
    • Mirrors
    • Regions
    • Applications
    • Locales
    • Platforms
    • Files
    • Downloadables?
    • Users
  • Chip away at scaffolding (for all models)
    • Search criteria
    • Pagination
    • Basic edits
  • Delete confirmation
    • Do we even delete?

Stats

  • Add more tracking of users/hits/downloads
    • Integrate with Urchin
    • Would require us to include a javascript file with each download (cached)

Status Search (for all models)

  • Available bandwidth
  • Enabled mirrors
  • Disabled mirrors
  • # of files hosted
  • Lookup by other models or wildcard (Any _____)

Dashboard (front page)

  • Total mirrors
  • Inactive mirrors
  • Active mirrors
  • Megabits of bandwidth available
  • # of files served by # of mirrors
  • Recent users
  • Other ideas?

Sentry Visualization

  • Read tests, events for sentry tests data
  • Allow searching by date
  • Lookup on any model
  • Search criteria
    • Application
    • Locale
    • Platform
    • Mirror
    • Region
    • Start Date
    • End Date
    • Test Type
    • Results (failed, success)?

Integration with loader.py for multiple file upload

Install and stage on khan

  • Admin tools
  • Bounce scripts (with URI rewrites)
  • Sentry tests
  • Loader

Deployment

  • Install and verify in production
  • Handle multiple instances
    • load balanced
    • physically seperated instances (different datacenters)
  • Front with Netscaler
    • logging issues?
    • referrer issues?

Build Requirements

  • P1: Roles can be handed out in groups, to products, i.e. Seamonkey/Camino people can login and modify/admin their products, but not modify FFx/Tb, nor add/delete new products.
  • P1: Requested validations, i.e. Sentry can be told "Check on these three products right now," and they'll show up in the mirror list immediately.
  • P1: We can dump the SHA1SUMS file directly into the DB (Bouncer2 has this?)
  • P2: Some better reporting about which mirrors are serving which releases, i.e. "Show me all mirrors serving FFx 1.5.0.5"