Dashboard > Bouncer > ... > Bouncer 2 > Bouncer TODO
Bouncer Log In   View a printable version of the current page.
Bouncer TODO
Added by Michael Morgan, last edited by Michael Morgan on Dec 09, 2005  (view change)
Labels: 
(None)

  1. Add product_active to
    1. Modify production / dev databases - add product_active field (morgamic)
    2. Add ability to toggle product status (morgamic)
      1. Need to make sure that all downloadables entries that are mapped to the changed product are disabled when a product is disabled
      2. When a product is disabled, entries should be made in sentry_tests and sentry_events to notify sentry about why a particular group of files was deactivated. This way in the HTML reports it says, "disabled by admin" or something along those lines.
      3. When a product is reenabled the admin interface does NOT update the downloadables to be active again. The pv_active flag is the only thing chagned, and Sentry should be responsible for verifying and reenabling the downloadable statuses based on test results (and assume they are defunct until then). This is so that we don't end up with a lack of security between the time when an admin reenables a product and Sentry's initial run-through of the newly "reactivated" downloadable records attached to the pv_id in question. I don't know what I just said, but I hope it makes sense.
    3. Add conditions to Sentry when searching for files
      1. v1, Perl (kveton)
      2. v2, Python (lars) - Sentry needs to know that it shouldn't check downloadables for any pv_id that has pv_active = '0'.
  2. Migration
    1. Run v1.0 and v2.0 in parallel
    2. Database synchronization / comparison
      1. MySQL dump from prod -> dev (kveton)
      2. Script to compare actual results and to preserve hit counts (lars)
    3. Deploy v2.0 on gecko.mozilla.org
  3. Usability - shouldn't we call this Banana?
    1. Add links to HTML reports in admin interface.
    2. Add CSV exports to lists of values.
    3. Add confirmation dialogs to delete operations (to prevent unintended deletions)
  4. Community (morgamic)
    1. Drupal
    2. Licensing and packaging
    3. Other community aspects (see [OSL:Building Communities])
  • Logging
    • Adding dated logs
    • Adding knowledge of where the redirect went
    • Source IP
    • Add ability to store filesize in database
  • Reporting Ideas
    • How much a mirror actually pushed over a period of time
    • Other stuff over time
  • Sentry Bandwidth Idea
    • When a download occurs for a mirror, dynamically compare database bandwidth rating with what the actual rating is and update (might want to rate-limit so it can't just turn everything off or lower to the point where we are offering 10Mbit for the whole network )
    • Assumes no saturation locally


Hi Lars. I like your beard.

Posted by Michael Morgan at Dec 05, 2005 13:07 | Permalink
Site powered by a free Open Source Project / Non-profit License (more) of Confluence - the Enterprise wiki.
Learn more or evaluate Confluence for your organisation.
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.2.7 Build:#524 Jul 28, 2006) - Bug/feature request - Contact Administrators