Bouncer: Difference between revisions
Jump to navigation
Jump to search
(Remove some meeting information from 2008) |
|||
| (5 intermediate revisions by 5 users not shown) | |||
| Line 5: | Line 5: | ||
*[https://svn.osuosl.org/public/bouncer/trunk Public SVN for v1, v2] | *[https://svn.osuosl.org/public/bouncer/trunk Public SVN for v1, v2] | ||
*[http://lxr.mozilla.org/mozilla/source/webtools/bouncer Public CVS for v3] | *[http://lxr.mozilla.org/mozilla/source/webtools/bouncer Public CVS for v3] | ||
*[ | *[https://github.com/mozilla/tuxedo/ Tuxedo: Django-based admin backend] | ||
== Discussion == | == Discussion == | ||
* [[MirrorNetwork]] - discussion about the copy of Bouncer currently in use at Mozilla and ideas and brainstorming of how to improve the process, whether it involves Bouncer or not. | * [[MirrorNetwork]] - discussion about the copy of Bouncer currently in use at Mozilla and ideas and brainstorming of how to improve the process, whether it involves Bouncer or not. | ||
# 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 | # 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 | ||
# 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? | ||
Latest revision as of 16:39, 22 December 2015
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
Discussion
- MirrorNetwork - discussion about the copy of Bouncer currently in use at Mozilla and ideas and brainstorming of how to improve the process, whether it involves Bouncer or not.
- 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
- 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?