| Version 94 (modified by davidsarah, at 2010-03-16T21:28:45Z) (diff) |
|---|
Tahoe-LAFS Summer-of-Code Projects
This page contains specific suggestions for projects we would like to see in the Summer of Code. Note that they vary a lot in required skills and difficulty. We hope to get applications with a broad spectrum.
If you are interested in working on any of these projects, please contact the Mentors listed at the bottom of the page.
In addition, you may wish to discuss your proposal on IRC—join us on #tahoe-lafs on irc.freenode.net.
We encourage you to come up with your own suggestions, if you cannot find a suitable project here. You can find more project ideas by exploring the issue tracker. Especially see tickets labelled 'gsoc' (developers: please add this label to any tickets that might make a good GSoC project). You may also want to read this mailing list thread about GSoC ideas.
Deadlines and directions for students' applications to the Google Summer-of-Code can be found on the Google pages.
| Project | Difficulty | Contact |
| Redundant Array of Independent Clouds | Medium | Zooko Wilcox-O'Hearn or any mentor |
| Share Migration | Medium | Brian Warner or any mentor |
| Secure Decentralized Wiki | Medium | Zooko Wilcox-O'Hearn or any mentor |
| Cloud Apps | Easy–Hard | Jack Lloyd or any mentor |
| WebDAV | Medium-Hard | David-Sarah Hopwood or any mentor |
| Distributed Introduction | Easy | Zooko Wilcox-O'Hearn or any mentor |
| DVCS Integration | Medium | Jack Lloyd or any mentor |
Redundant Array of Independent Clouds
Add backends to the storage servers so that they store their shares on a cloud storage system instead of on their local filesystem. This means that you can get all of the availability and scalability of services such as Amazon S3 or Rackspace CloudFiles combined with the security properties of Tahoe-LAFS. See the RAIC diagram. For details read ticket #999 which including pointers to the relevant source code and instructions on how to begin writing the code.
Share Migration
When uploading a file to a grid, Tahoe-LAFS will make sure that the file is healthy (a good discussion of what healthy means is found in #778) before reporting that the file is uploaded successfully. Tools to effectively maintain file health (or to adapt to new definitions of health) aren't quite complete, however -- our users have had several use cases that aren't easily addressed with what we have. Students taking this project would be building tools to address those use cases.
A good starting point would be to become familiar with how files are placed on a grid. architecture.txt, file-encoding.txt, mutable.txt, the immutable file upload code, and the mutable file upload code are good places to do that. Also, you might want to look at the storage server code to understand that better. Some good tickets to start looking at are #699, #543, and #232; you'll find that those link to other tickets.
There are many ways to help address these issues. Some ideas:
- Alter the CLI and the WUI to give users the ability to rebalance files that they've uploaded already. (#699)
- Build tools that allow node administrators to moves shares around a grid (#543, #864)
- Alter Tahoe-LAFS to rebalance mutable files when uploading a new version of them. (#232)
Any one of these projects is probably too small to fill a summer, but combining a few of them would be a big usability improvement for Tahoe-LAFS.
Depending on how you address this, this is tightly integrated with ideas of file health and accounting, so prospective students would do well to explore those open issues, too. A good accounting jumping-off point is #666. A good jumping-off point for health is #778.
Secure Decentralized Wiki
Write a wiki in Google's caja dialect of JavaScript. This wiki will load and store data directly on a Tahoe-LAFS storage grid so that it is a full "Cloud App"—there is no server. All computation is done in the user's web browser in caja and all of the storage is done by the decentralized Tahoe-LAFS storage grid. This wiki should leverage Tahoe-LAFS's secure sharing features to offer fine-grained, dynamic, and easy transclusion or client-side mashups. This project is intended to be the successor to the TiddlyWiki-on-Tahoe-LAFS project, which is a wiki written in JavaScript and hosted on Tahoe-LAFS, but one that has been "bolted on" to Tahoe-LAFS instead of designed for Tahoe-LAFS, and is currently incapable of good transclusions or mashups.
To get started, play with the TiddlyWiki-on-Tahoe-LAFS quick start, read the source code of the HTTPSavingPlugin and the TahoePlugin for TiddlyWiki, and experiment with writing live caja applets.
Cloud Apps
Difficulty: easy to hard, depending on project choice and how far you want to push it
Invent your own Summer-of-Code project by building a new web app on top of Tahoe-LAFS. The Secure Decentralized Wiki is one example of a Cloud App. See GSoCIdeas/CloudApps for other ideas.
WebDAV support
Difficulty: medium to hard, depending on how much of an existing WebDAV implementation you are able to reuse
Implement a WebDAV front-end for Tahoe-LAFS so that files and directories stored in a distributed grid can be accessed by operating systems and applications that speak the WebDAV protocol. WebDAV is specified in RFC 2518 and a few other documents; it essentially extends HTTP to act as a filesystem access protocol. For details see #451 which describes what the Tahoe-LAFS web server does now, how this differs from what a WebDAV web server does, and how to get started experimenting with the relevant source code.
The main attraction of implementing a WebDAV interface is that several operating systems have bundled and somewhat integrated support for it, including Windows, Mac OS X, and most distributions of Linux. In fact WebDAV may turn out to be an easier alternative to SMB/CIFS for allowing filesystem access from Windows.
However, there is currently no working WebDAV implementation in Twisted Python. There used to be one (the web2.dav package), but it bitrotted. You'll have to decide whether to help fix that implementation, use a non-Twisted implementation such as WsgiDAV that might be more difficult to integrate wth the existing Tahoe code, or write your own. In any case, WebDAV is a complicated protocol and you will need to decide what subset of it gives most "bang for the buck" and is practical to support in the time available. For example, locking is optional in the WebDAV spec; is it needed to interoperate with commonly used WebDAV clients?
Unlike most filesystems which are constrained to be trees, the structure of a Tahoe is in general a cyclic graph. draft-ietf-webdav-bind is an Internet Draft that clarifies how WebDAV servers should handle cycles.
davfs2 is a FUSE-based WebDAV filesystem client for Linux. To ensure that this runs correctly over your implementation of WebDAV, you'll probably need to adapt the tests for the existing Tahoe blackmatch FUSE interface (this would not be redundant since the blackmatch implementation has limitations, especially for write access, that davfs2 would not have).
The WebDAV mini-redirector is the component of Windows providing its WebDAV filesystem support. It is actually the less buggy of two implementations, but it still has had bugs and security vulnerabilities that you may need to take into account.
Distributed Introduction
Implement a protocol for distributed introduction, thus removing the only remaining Single Point of Failure (SPoF) in the Tahoe-LAFS system. For details see ticket #68 which describes the distributed notification algorithm and points to the relevant source code.
DVCS Integration
Write patches for the git or darcs distributed revision control tool so that it reads and writes directly to a Tahoe-LAFS storage grid instead of its local filesystem. This creates a "revision control repository in the sky"—a repository that is distributed, fault-tolerant, and highly available. It also lends Tahoe-LAFS's unique security and access-control properties to your revision control system—you can share read-only access or read-write access with specific people through Tahoe-LAFS's capability access control system, and you can rely on the integrated digital signatures to verify that you are reading an authorized version of the repository.
When Zooko was at the RSA 2010 security conference in March 2010, an employee of the U.S. National Security Agency told him that they were interested in integrating git with Tahoe-LAFS.
There is already a simple kind of integration for Tahoe-LAFS with the bzr distributed revision control tool. Bzr can be configured to write its repositories through ftp and Tahoe-LAFS offers and ftp front-end. Here are instructions on how to use the combination of bzr and Tahoe-LAFS. Improving the bzr+Tahoe-LAFS integration to be faster, more flexible, and easier to use would be an alternative to integrating git or darcs.
Required skills: for git you need to know some C and understand git's behavior. For darcs you need to know some Haskell and understand darcs's behavior. For bzr you need to know some Python (or actually forget it you can just learn Python as you go because it is so easy) and understand bzr's behavior.
Mentors
Who is willing to spend about five hours a week (estimated) helping a student do it right?
- Zooko Wilcox-O'Hearn blog (Python/C/C++/JavaScript, security+cryptography)
- Jack Lloyd blog (C/C++/Python, security+cryptography)
- David-Sarah Hopwood (Python/C/JavaScript, SFTP frontend, security+cryptography)
- Brian Warner (Python/C/JavaScript, security+cryptography)
