Project Ideas » History » Version 1
Jessica Mack, 05/28/2015 11:47 PM
| 1 | 1 | Jessica Mack | h1. Project Ideas |
|---|---|---|---|
| 2 | |||
| 3 | This page was originally created as an idea list for Google Summer of Code 2013. However, we wanted it to be an open resource to anyone looking to get involved in Ceph (or anyone that wants to share a project idea with the Ceph community). Read below for projects you can break off and tackle. |
||
| 4 | |||
| 5 | h3. +File Locking in Ceph-FUSE+ |
||
| 6 | |||
| 7 | > |
||
| 8 | > h4. Technical Contact: "Greg Farnum":mailto:greg@inktank.com |
||
| 9 | > |
||
| 10 | > h4. Description: |
||
| 11 | > |
||
| 12 | >>The Ceph distributed file system can be accessed by either a kernel client or a (user mode) FUSE module. The kernel client (and the meta data servers) >>support file locking, but the FUSE implementation does not yet include include this support. Extend the current FUSE module to implement lock calls. Most >>of this can be very similar to the implementation already in the kernel client, but it will be necessary to extend the FUSE module to keep track of the >>locks it owns so that it can reestablish those locks in case of meta data server failure. |
||
| 13 | > |
||
| 14 | > h4. Required Skills and Resources: |
||
| 15 | > |
||
| 16 | >>The existing FUSE module is a single C++ module. This work will require a basic understanding of file system operations and distributed lock management. >>Most of the development and testing can be done with VMs on your computer; if anything requires additional resources we can probably provide VPN access to >>our lab. |
||
| 17 | > |