3,035
edits
Bouncer:v3: Difference between revisions
m
→Build Requirements
mNo edit summary |
|||
| Line 90: | Line 90: | ||
== Build Requirements == | == Build Requirements == | ||
* P1: Warnings about invalid operations, i.e. specifying a location for a product that already exists, etc. | * P1: Warnings about invalid operations, i.e. specifying a location for a product that already exists, etc. | ||
** The file view lacks a dupe check -- this would be an easy fix for v2. | |||
* 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: 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. | ||
** Test type 4 could be scheduled to run every 10 minutes -- it is the test that verifies new files. If it ran frequently, Sentry would check new items automatically on a regularly scheduled basis -- I think that would meet the requirement. See the [http://wiki.osuosl.org/display/Bouncer/Installation+Guide#InstallationGuide-Options wiki page on Sentry's options]. | |||
* P1: We can dump the SHA1SUMS file directly into the DB (Bouncer2 has this?) | * P1: We can dump the SHA1SUMS file directly into the DB (Bouncer2 has this?) | ||
** Bouncer2 has this (loader.py) -- it was one of the main requirements for v2. | |||
* P2: 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. | * P2: 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. | ||
* P3: Some better reporting about which mirrors are serving which releases, i.e. "Show me all mirrors serving FFx 1.5.0.5" | * P3: Some better reporting about which mirrors are serving which releases, i.e. "Show me all mirrors serving FFx 1.5.0.5" | ||