| | The following is a listing of possible project ideas for the Google Summer of Code that Oregon State University would be willing to mentor for. |
| | |
| | h2. Bouncer |
| | |
| |  | Have you ever wondered how Mozilla keeps such up-to-date download statistics? Did you know that its a piece of software called Bouncer? Bouncer is an open source project used to manage the mirror network and downloads for any download-intensive project. |
| | | Have you ever wondered how Mozilla keeps such up-to-date download statistics? Did you know that its a piece of software called Bouncer? Bouncer is an open source project used to manage the mirror network and downloads for any download-intensive project. |
| | |
 | | Bouncer is a PHP/Python application written by [Mike Morgan|http://morgamic.com] and [Lars Lohn|http://osuosl.org/Members/lars/]. The tool allows you to gather download statistics, monitor your mirror network, redirect users to the "best" mirror possible as well as check the integrity of files on remote mirrors. Check out the [Bouncer wiki|http://wiki.osuosl.org/pages/recentlyupdated.action?key=Bouncer] for more information about this project. |
| | | Bouncer is a PHP/Python application written by [Mike Morgan|http://morgamic.com] and [Lars Lohn|http://osuosl.org/Members/lars/]. The tool allows you to gather download statistics, monitor your mirror network, redirect users to the "best" mirror possible as well as check the integrity of files on remote mirrors. Check out the [Bouncer wiki|http://wiki.osuosl.org/pages/recentlyupdated.action?key=Bouncer] for more information about this project. |
| | |
| | We are interested in finding a student to help with [Bouncer v3|http://wiki.osuosl.org/display/Bouncer/Bouncer+3] and get the tool ready to work with projects like [OpenOffice] and others that have shown interest in its use. New features we would like to see implemented include: |
| | * Dashboard interface for seeing "live" status of the mirror network |
| | * Better interface for presenting statistics in the GUI |
| | * Tools for ease-of-use for multiple projects |
| | * Pagination |
| | |
| | [!bouncer-dashboard-thumb.jpg!|http://wiki.osuosl.org/download/attachments/8815/bouncer-dashboard.jpg][!bouncer-products-thumb.png!|http://wiki.osuosl.org/download/attachments/8815/bouncer-products.png][!bouncer-sentry-thumb.jpg!|http://wiki.osuosl.org/download/attachments/8815/bouncer-sentry.jpg] |
| | |
| | h2. Hosting management app |
| | |
| | Currently we have a simple ruby on rails app to track servers hosted here. See [http://staff.osuosl.org/~cshields/?p=115]. The idea with this project is to start with a new db schema, write a new app in php with the same current functionality, but with the added schema we would add support for a new version of rackview (rackview.sourceforge.net) developed at the OSDL (currently written in perl). The 2 apps would basically be merged into one. (Google could probably make good use of such an app if they don't have such a beast already) ;) |
| | | Currently we have a simple ruby on rails app to track servers hosted here. See [http://staff.osuosl.org/~cshields/?p=115]. The idea with this project is to start with a new db schema, write a new app in php with the same current functionality, but with the added schema we would add support for a new version of rackview (rackview.sourceforge.net) developed at the OSDL (currently written in perl). The 2 apps would basically be merged into one. (Google could probably make good use of such an app if they don't have such a beast already) ;) |
| | |
| | The new schema is already drawn out on paper and consists of about 20 tables (most of those tables just a few fields in size). The app would need to start with simple CRUD forms and then features added to that. Frameworks are more than welcome as long as coding documentation is well maintained so that the project can live and grow beyond the summer of code project. The end result would be packaged up for anyone to use, and there is already interest from quite a few hosting environments, so there will be no lack of input on requirements. |
| | | The new schema is already drawn out on paper and consists of about 20 tables (most of those tables just a few fields in size). The app would need to start with simple CRUD forms and then features added to that. Frameworks are more than welcome as long as coding documentation is well maintained so that the project can live and grow beyond the summer of code project. The end result would be packaged up for anyone to use, and there is already interest from quite a few hosting environments, so there will be no lack of input on requirements. |
| | |
| | Current features in our rails app: |
| | * CRUD |
| | * Simple searching (index based, not db based) |
| | * Relational navigation |
| | |
| | Added features would include: |
| | * Better searching |
| | * Query forms for criteria navigation ("show me all servers running Debian linux and working as a mysql server") |
| | * Virtual machine tracking |
| | * Aforementioned integration with Rackview |
| | ** Current rack usage (space, network, power) |
| | ** Current rack availability (space, network, power) |
| | ** Cabling assignments |
| | |
| | Other feature ideas include (but not limited to): |
| | * Cacti integration |
| | * Nagios integration |
| | * Plugin architecture (make it easier to integrate things like the above two!) |
| | | * Plugin architecture (make it easier to integrate things like the above two\!) |
| | |
| | Technical Requirements: |
| | * PHP |
| | * Perl |
| | * [MySQL] |
| | |
| | Screenshots of the existing apps (click for full-size): |
| | |
| | [!inventory-thumb1.png!|http://wiki.osuosl.org/download/attachments/8815/inventory1.png] [!inventory-thumb2.png!|http://wiki.osuosl.org/download/attachments/8815/inventory2.png] |
| | |
| | h2. Laszlo-based Infrastructure Monitor |
| | |
| | We have an existing app that displays vital statistics on to a big screen display in our NOC. Currently it acts as a slideshow of some network graphs, along with pulling some other data from rss feeds (current security alerts, nagios outages, debian and gentoo security announcements). While this is very handy for our needs, we would like to: 1) extend it's features, 2) modify the code and package it up for others to benefit from it.. Make it more environment-neutral. |
| | | We have an existing app that displays vital statistics on to a big screen display in our NOC. Currently it acts as a slideshow of some network graphs, along with pulling some other data from rss feeds (current security alerts, nagios outages, debian and gentoo security announcements). While this is very handy for our needs, we would like to: 1) extend it's features, 2) modify the code and package it up for others to benefit from it.. Make it more environment-neutral. |
| | |
| | Added features would include: |
| | * Site-independent code |
| | * Integration into current system information tools such as Nagios and Cacti |
| | * Remote control of the display (changing modes, pausing the display, etc.. Keeping in mind that the display may not always have a keyboard attached) |
| | | * Remote control of the display (changing modes, pausing the display, etc.. Keeping in mind that the display may not always have a keyboard attached) |
| | * Event-based stats and modes (ie, when a server goes DOWN, the Nagios notification should not go off the screen.. maybe change the color of the background, etc) |
| | * Be creative\! Laszlo is a fun, flashy environment to work with. |
| | Time-permitted features: |
| | * Data handlers for system statistics (via snmp, rrdtool, etc) to display some statistics natively, rather than just slideshowing images. |
| | |
| | Requirements: |
| | * Laszlo - this part can be learned in no time at all. see [http://www.laszlosystems.com] or [http://www.openlaszlo.org] for their 10-minute tutorial |
| | * j2ee - Laszlo is built with j2ee, and to get some functionality beyond the base Laszlo API, some j2ee modules will need to be written |
| | |
| | Screenshots of the existing app (click for full-size): |
| | |
| | [!oslmon-thumb1.png!|http://wiki.osuosl.org/download/attachments/8815/oslmon1.png] [!oslmon-thumb2.png!|http://wiki.osuosl.org/download/attachments/8815/oslmon2.png] |
| | |
| | h2. Our infrastructure |
| | |
| | We use various open-source tools on our network, enhancements to which would directly benefit us. |
| | * cfengine |
| | ** Support for Gentoo Portage in packages.c |
| | |
| | * dirvish |
| | ** At one time, the maintainer contacted us interested in having us do some development on this backup tool we use. Perhaps he still wants help making improving it or making it more robust. |
| | | ** At one time, the maintainer contacted us interested in having us do some development on this backup tool we use. Perhaps he still wants help making improving it or making it more robust. |
| | |
| | * Dream app - centralized management for community-based distros |
| | ** So, this is a beast that might be beyond the summer of code, but it needs to be bootstrapped somewhere. The idea is simple: a RHN-like management platform for community-based Linux distributions (Debian, Gentoo, Ubuntu...). Anything to make my life as a sysadmin easier.. |
| | | ** So, this is a beast that might be beyond the summer of code, but it needs to be bootstrapped somewhere. The idea is simple: a RHN-like management platform for community-based Linux distributions (Debian, Gentoo, Ubuntu...). Anything to make my life as a sysadmin easier.. |
| | |
| | h2. Maintain |
| | |
| | Maintain is a LAMP DHCP/DNS management product that is designed by the OSL. This project started out as a project from Oregon State University's network services department to manage the the campus' network. Today, it is in its third major revision and currently is used not only by Oregon State University, but also by Purdue, Waterloo and many more. |
| | |
| | A student's responsibilities on Maintain would be wide and varied, allowing for a building of a broad base of skills, as well as exposure to different aspects of software development. These responsibilities include, but are not limited to: |
| | * Module writing |
| | ** New feature implementations |
| | *** SNMP Integration |
| | ** Porting of existing modules |
| | *** autoreg - Module that allows students to easily register their computer on campus |
| | *** antivirus - Allows Maintain to keep track of antivirus software versions |
| | * Bug fixing |
| | * Documentation writing |
| | * Product testing |
