1 / 13

OpenAFS Roadmap F

OpenAFS Roadmap F. Jeffrey Altman Derrick Brashear. Wouldn’t it be nice if. Everyone has their pet project. Some are more polished than others. Some projects have been integrated more quickly than others.

iain
Download Presentation

OpenAFS Roadmap F

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OpenAFSRoadmapF Jeffrey Altman Derrick Brashear

  2. Wouldn’t it be nice if... • Everyone has their pet project. • Some are more polished than others. • Some projects have been integrated more quickly than others. • The usual barrier is how easily can the code be added and vetted, or added and proven to be able to be turned off. • Having a userbase known to be using the actual contributed code helps. • If it’s being tested with unstable, even better. 2

  3. How CVS has held us back • CVS doesn’t support distributed branches. • I had a plan to add it but it’s not worth the effort. It was a neat idea, too. • OpenAFS deltas are mostly analogous to Transarc (IBM) deltas but I wrote most of the tools myself. Thus, they are crude. • CVS was the obvious choice for an underlying repository in 2000. 3

  4. Why git isn’t done yet • git cvsimport uses discrete file revisions. • OpenAFS deltas assume patches. • tailor only converts one branch, the head. • OpenAFS uses branches heavily. • cvsps assumes one change per file in a patchset. • OpenAFS deltas can have multiple changes per file. • cvsps is broken. • Put beer in Derrick, listen to saga of woe. 4

  5. Not all news is bad • There’s no network on planes or trains. • git is much closer to done now. • Need to confirm branching. • Need to handle (and fix tagging of) binary files. • Need to send cvsps fixes upstream. 5

  6. Works in Progress - 1 • Windows client Unicode support. (1.5.50) • Windows native installable filesystem. • Google Summer of Code projects. • http://code.google.com/soc/2008/openafs/about.html • “libosi” portability interface. • This may be very ambitious given the scope of the code. • More likely, we will start with part of libosi. • Extended Callback interface.

  7. Works in Progress - 2 • Rx OSD (pending integration) • Lack of access to suitable hardware for testing has been a second roadblock here. • DESY will provide a persistent test system. • AFSCommander (pending integration) • This will be integrated when we move to git, so ideally Claudio Bisegni can be delegated version control permission to continue working on it directly. 7

  8. Works in Progress - 3 • Rx Kerberos 5 support. • rxk5 work substantially usable. • Multiple volume clones. • Multi-backend fileserver. • Inode and namei are obvious. • A local partition exporter could be taken inboard and use the existing callback and client management code.

  9. Works in Progress - 4 • Byte range locking. • Unix clients. • Initially as local upgrades to whole-file locks. • Servers. • A protocol extension will be needed. • Lock Delegation. • Give one client ownership of a range or a whole file for a fixed period of time. • All lock requests must be brokered through that client. 9

  10. Projects seeking support • Improving performance on 10gbit networks and implementing support for IPv6. • Rx/TCP. • bulk data transfer. • Removing directory limitations: • More than 64000 “blobs”. • POSIX Extended attributes. • Internationalization (Unicode). • Better hashing.

  11. More projects seeking support • NDMP • HostAFSd - local filesystem re-exporter • Non-coding • Web site replacement • Toolsmithing • Version control migration • (It’s not like I didn’t ask for volunteers... *) • Many more ...

  12. How can you help? • Today • Contribute code. • Contribute non-code (git anyone?). • Works for hire. • Tomorrow • That leads in to the OpenAFS governance discussion.

  13. OpenAFS Futures Questions?

More Related