[OpenAFS] Re: openafs OSD

Andrew Deason adeason@sinenomine.net
Tue, 28 May 2013 10:56:07 -0500

On Tue, 28 May 2013 10:48:37 -0400
Jeffrey Altman <jaltman@your-file-system.com> wrote:

> is not intended to be incorporated into the OpenAFS repository.  It is
> a standalone service that can and should be developed independently of
> OpenAFS.

Yes yes, I mean the portions going into openafs.

> There is some glue code that needs to be added to OpenAFS to permit
> third party modules to be loaded into OpenAFS but the overall impact
> on OpenAFS should be relatively small.

That's the goal, yes. But that doesn't mean the only code that's pending
"cleanup and submit to openafs" is some small glue code. From what I
recall there is still quite a bit of code in that tree modifying openafs
sections that are required for osd to work (and can't just go in the
tree without thinking). In addition, there is the entirety of the client
code, which is not separable into a separate component (at least, I am
aware of no such plans).

And since everything is currently in the same tree and git branch, the
libafsosd-y components I assumed would need to be split out of the tree,
since the goal was to not require rebasing against openafs constantly.

All of this is "relatively small" if you mean relative to the entire OSD
project, or perhaps compared to the previous plan to integrate OSD. It's
not what I would call "small" compared to most any other openafs-related
task (certainly not volunteer "when-I-have-time" tasks).

Andrew Deason