bouncer_r/php index.php,1.6,1.7
David Farning (dfarning)
fedora-extras-commits at redhat.com
Tue Aug 2 06:43:16 UTC 2005
Author: dfarning
Update of /cvs/fedora/bouncer_r/php
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv30079/php
Modified Files:
index.php
Log Message:
modified intro to fit Fedora
Index: index.php
===================================================================
RCS file: /cvs/fedora/bouncer_r/php/index.php,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- index.php 2 Aug 2005 05:20:25 -0000 1.6
+++ index.php 2 Aug 2005 06:43:14 -0000 1.7
@@ -6,7 +6,6 @@
$template = new Page;
-
$template->displayHeader('Fedora Finder');
?>
@@ -15,6 +14,7 @@
<h2> Abstract </h2>
<p>Bouncer uses MySQL to organize the Mozilla mirror network. Its primary responsibility is to know what mirrors are supposed to contain what files and periodically query their availability. Based on this knowledge, accumulated by a "sentry" script, Bouncer redirects simple user requests to appropriate mirrors based on a random seed that is affected by the mirror's relative bandwidth capabilities.</p>
+<p>Bouncer_r is a version of bouncer that is modified to handle the additional needs of a repository based linux distrobution.</p>
<p>In short, Bouncer is a smarter way to use an extended mirror network to help users get what they need.</p>
<p>It contains three main pieces:</p>
<ul>
@@ -24,17 +24,21 @@
</ul>
<h2> History </h2>
-<p>Bouncer went live at 2pm, November 9th, 2004 and has been serving files since. It was originally developed as a backup plan, but was pushed to production when the demand for Firefox 1.0 overloaded the existing mirror network. Utilizing secondary mirrors through Bouncer helped keep downloads flowing in the wake of Mozilla's largest release to date.</p>
-<p>Bouncer was originally developed at Oregon State University by Scott Kveton and Mike Morgan. The intent was to help the Mozilla community meet its growing demands.</p><p>Additional development on Bouncer has continued into 2005. K Lars Lohn, a developer at the Oregon State University Open Source Lab, has made great contributions to the project by assisting with database improvements and the migration of Sentry from Perl to Python. He has helped make Sentry a multi-threaded daemon that will scale much better for an increased mirror network hosting a greater number of projects/files.</p>
+<p>Bouncer went live at Mozilla at 2pm, November 9th, 2004 and has been serving files since. It was originally developed as a backup plan, but was pushed to production when the demand for Firefox 1.0 overloaded the existing mirror network. Utilizing secondary mirrors through Bouncer helped keep downloads flowing in the wake of Mozilla's largest release to date.</p>
+<p>Bouncer was originally developed at Oregon State University by Scott Kveton and Mike Morgan. The intent was to help the Mozilla community meet its growing demands.</p>
+<p>Additional development on Bouncer has continued into 2005. K Lars Lohn, a developer at the Oregon State University Open Source Lab, has made great contributions to the project by assisting with database improvements and the migration of Sentry from Perl to Python. He has helped make Sentry a multi-threaded daemon that will scale much better for an increased mirror network hosting a greater number of projects/files.</p>
+<p>Development of Bouncer_r started in June of 2005 by David Farning and Luke Maken.</p>
+
<h2> Status </h2>
-<p>Bouncer 1.0 is currently directing users to the latest Firefox and Thunderbird releases through the mirror network. Bouncer 2.0 is nearing the final stages of development and should be deployed before Firefox 1.0.1 is released.</p>
+<p>Bouncer 1.0 is currently directing users to the latest Firefox and Thunderbird releases through the mirror network. Bouncer 2.0 is nearing the final stages of development and should be deployed before Firefox 1.0.1 is released. Bouncer_r 2.0 is in the early development stage.</p>
<h2> Schedule </h2>
<ul>
<li> November 9th, 2004 - Bouncer goes live as a Plan B for Firefox v1.0 release.</li>
<li> February 18th, 2005 - Tentative release date for Bouncer v2.0 in preparation for Firefox 1.0.1 release.</li>
<li> Spring, 2005 - Development of Bouncer v3.0, integration with build process.</li>
+ <li> August, 2005 - Tentative release date for Bouncer_r 2.0 in preparation for Fedora Core 5 release.</li>
</ul>
<h2> Roadmap </h2>
@@ -112,10 +116,43 @@
</li>
</ul>
-<p>This first joint effort provides better overall security and granularity. It fixes Language and Version gaps and provides better assurance through improved file checking (MD5,SHA1).</p>
-<p>Second priorities were improved statistical tools for generating trend reporting. That was not completed, but will be addressed in 3.0.</p>
-<h3> Bouncer 3.0 </h3>
+<h3> Bouncer_r 2.0 </h3>
+<ul>
+ <li> Administrative changes
+ <ul>
+ <li> Added repository information
+ <ul>
+ <li> Products</li>
+ <li> Versions </li>
+ <li> Architectures </li>
+ </ul>
+ </li>
+ <li> Modified database structure to handle repoository metadata</li>
+ <li> Modified look and feel to match existing Fedora website throught use of cascading stype sheets</li>
+ </ul>
+ </li>
+ <li> Sentry
+ <ul>
+ <li> Monitors repoitory status information</li>
+ <li> Parses repomd files</li>
+ </ul>
+ </li>
+ <li> Bouncer
+ <ul>
+ <li> Not yet implemented</li>
+ </ul>
+ </li>
+ <li> Development Model
+ <ul>
+ <li> Integration with Fedora CVS tree</li>
+ <li> Intergation into Fedora infrastructure</li>
+ </ul>
+ </li>
+</ul>
+
+
+<h3> Bouncer 3.0 (mainline)</h3>
<ul>
<li> Build Features
<ul>
@@ -135,9 +172,16 @@
<li> Any other public tools to assist the community</li>
</ul>
+<h3> Bouncer_r 3.0 </h3>
+<ul>
+ <li> Follow improvements in Bouncer mainline</li>
+ <li> Encapsulate bouncer_r modifacation and pass back to main line</li>
+
+</ul>
+
<p>The future of Bouncer depends on the development of UMO and what role people see it playing in relation to Mozilla's update service. It will continue to distribute binaries through the mirror network, but how it can better fit into Mozilla's workflow has yet to be determined. We are working on figuring out how it can help automate and combine builds, updates, etc. The best is yet to come.</p>
-<h2> Bouncer Ideas </h2>
+<h2> Bouncer Ideas (mainline)</h2>
<ul>
<li> Proactive mirroring
<ul>
@@ -169,6 +213,19 @@
</li>
</ul>
+<h2> Bouncer_r Ideas</h2>
+<ul>
+ <li> Modify createrepo so that repomd contains inforamtion about ISOs</li>
+ <li> Data push system
+ <ul>
+ <li>createrepo passes change of repo status information to sentry</li>
+ <li>sentry passes change of repo status to mirrors</li>
+ <li>mirror passes mirror updated information back to sentry</li>
+ </ul>
+ </li>
+ <li>GeoIP interface to find 'close' mirror</li>
+</ul>
+
<h2> Server Requirements </h2>
<h3> v1.0 </h3>
More information about the fedora-extras-commits
mailing list