SoC/Ideas: Difference between revisions

From SambaWiki
(→‎Linux Kernel CIFS/SMB2/SMB3 client improvements: Commenting out stale proposals, feel free to re-add things that are still relevant)
m (Add back Ceph key/value store task)
Line 85: Line 85:
*Possible Mentors: Andreas Schneider
*Possible Mentors: Andreas Schneider


-->
===dbwrap back-end for Ceph RADOS key-value storage===
===dbwrap back-end for Ceph RADOS key-value storage===


Line 98: Line 99:
*Language(s): C
*Language(s): C
*Possible Mentors: David Disseldorp
*Possible Mentors: David Disseldorp
<!-- Commented out possibly stale proposals


===Samba AD DC as the ideal POSIX Directory===
===Samba AD DC as the ideal POSIX Directory===

Revision as of 12:01, 17 January 2018

Google Summer of Code: Suggested Project ideas

The following are the Samba project ideas for Summer of Code. Of course you are free to come up with ideas not listed here. Please discuss the your planned project by either joining us on irc://irc.freenode.net/#samba-technical or by sending email to samba-technical@lists.samba.org

Most of our projects will require C programming skills, but the Samba section has a couple of Python projects.

Samba

Some additional possible GSoC topics can be found in Bugzilla in the form of bugs which are marked as "Feature request": here. Questions regarding complexity and requirements should be directed to the technical mailing list.

dbwrap back-end for Ceph RADOS key-value storage

Ceph offers a highly scalable and fault-tolerant storage system. Samba is already capable of sharing data located on the Ceph Filesystem, however scale-out sharing (the same data exposed by multiple Samba nodes) currently requires the use of CTDB for consistent and coherent state across Samba cluster nodes. In such a setup CTDB provides a clustered database with persistent key-value data storage and locking. Database usage is abstracted out via a generic dbwrap interface.

Ceph's librados library provides an API for the storage and retrieval of arbitrary key-value data via the omap functions. A watch/notify protocol is also provided as a mechanism for synchronising client state (locking). Key-value data stored in the RADOS back-end inherits the same redundancy features as regular objects, making it a potentially good candidate as a replacement for CTDB in scale-out Samba clusters.

Alternatively, the RocksDB key-value store includes a Ceph librados back-end, which could perhaps also be plumbed into dbwrap. Doing so would however require architectural changes, to ensure that the RocksDB database is only consumed by a single process on each node.

This task involves the implementation and testing of a new dbwrap back-end that uses librados for the storage, retrieval and locking of Samba key-value state. Ideally, the candidate would also allow time for benchmarking, and an investigation of scalability bottlenecks.

  • Difficulty: Medium, Hard
  • Language(s): C
  • Possible Mentors: David Disseldorp

Linux Kernel CIFS/SMB2/SMB3 client improvements

Interested students should contact Steve French (or Jeff Layton) and discuss possible improvements to the Linux Kernel CIFS VFS client. Here are some ideas to get you started: