1,885
edits
Changes
→Potential Fedora Projects
* http://fedoraproject.org/wiki/Packaging/Java
* http://jpackage.org
== Benchmark Nightlife Scalability Issues ==
Using Puppet, or some other management tool, create a grid of a
dozen machines, then turn that into 12,000 machine. Address the network
characteristics - how much bandwidth do you need on different
components, the communication mechanisms - does UDP work at such a
scale, the grid topology - what happens when two nodes are behind firewalls.
Resource: [[:fedora:Nightlife Nightlife wiki page]], Matthew Farrellee
== Add IPv6 Support to Condor ==
Sooner or later we're going to have to live with IPv6. Many
applications are very tied to IPv4 and that includes Condor. Understand
what IP addresses really mean to Condor, like many existing systems, and
what the implications of an IPv6 conversion means and how it can be
done. There are many resources about IPv6 interfaces, but not many good
transition guides, and fewer that address what the change can really
mean to an application - Condor takes addresses and passes them as ascii
text between components.
Resource: [[:fedora:Nightlife Nightlife wiki page]], Matthew Farrellee
== Update Condor Build System ==
At the foundation of many good applications is its build
infrastructure. The latest generation of tools includes GNU make with a
very powerful interpreted language and ever increasing functionality in
autotools. Condor has a build system from a few generations back. It
uses imake, originally designed for building X. While new systems are
more powerful and provide enhanced functionality, there isn't always a
clear mapping to features of older systems. Don't only find a way to use
newer tools to build Condor, but find a way to use the power of current
generation tools in ways that aren't just a straight mapping of need
satisfied by older systems.
Resource: [[:fedora:Nightlife Nightlife wiki page]], Matthew Farrellee
== Create Test Suite for Condor ==
Along with a good build infrastructure, a strong test framework and
methodology is key to survival of modern software. Condor is a system
that is shipped on, currently, 14 different platforms - OS + Arch
combinations. New features need to be verified to work on all those
platforms and shown to cause no regressions in other features. Condor
has a large test suite, but no suite covers everything or in sufficient
depth. Pick a few features, say the VM Universe or Concurrency Limits,
and demonstrate full understanding of them by testing all of the corner
cases. This is far from a simple task, and requires more than a cursory
understand of the system to properly complete. Understanding the complex
interactions of distributed components, common patterns exist across
many distribute systems, as well as intimate interactions with the OS is
key.
Resource: [[:fedora:Nightlife Nightlife wiki page]], Matthew Farrellee
<!-- Commented out by Chris Tyler 2008-08-31 -- I think we'll get all the students doing this.
