Bouncer: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
# Sentry has many options for tests, testing schedules, trouble notifications and reports. What should be used? See the Scheduling and Reporting sections on this page: http://wiki.osuosl.org/display/Bouncer/Running+Sentry+2 | # Sentry has many options for tests, testing schedules, trouble notifications and reports. What should be used? See the Scheduling and Reporting sections on this page: http://wiki.osuosl.org/display/Bouncer/Running+Sentry+2 | ||
# Sentry runs from one machine. What happens if that machine loses its connection to the network - suddenly all mirrors are marked bad because they're unreachable? | # Sentry runs from one machine. What happens if that machine loses its connection to the network - suddenly all mirrors are marked bad because they're unreachable? | ||
= Meetings = | |||
== Nov 19 == | |||
* understand requirements for Q4 goal | |||
* differentiate between must-haves and nice-to-haves | |||
* wind up with a more concrete list of requirements and schedule | |||
Revision as of 20:06, 18 November 2008
Bouncer is a database driven mirror management app that has three main components - a bounce script, a sentry script to check mirrors and files for integrity and a set of web-based administration tools.
Project Status
Documentation
Discussion
- Sentry has many options for tests, testing schedules, trouble notifications and reports. What should be used? See the Scheduling and Reporting sections on this page: http://wiki.osuosl.org/display/Bouncer/Running+Sentry+2
- Sentry runs from one machine. What happens if that machine loses its connection to the network - suddenly all mirrors are marked bad because they're unreachable?
Meetings
Nov 19
- understand requirements for Q4 goal
- differentiate between must-haves and nice-to-haves
- wind up with a more concrete list of requirements and schedule