[OpenAFS-devel] convergence of RxOSD, Extended Call Backs, Byte Range Locking, etc.

[Derrick Brashear]

On Wed, Jul 22, 2009 at 2:06 PM, Jeffrey Hutzelman<jhutz@cmu.edu> wrote:
> --On Wednesday, July 22, 2009 01:26:39 PM -0400 Tom Keiser
> <tkeiser@sinenomine.net> wrote:
>
>> a) convergence of RxOSD with other protocol changes (XCB, byte-range
>> locking, perhaps others)
>> b) changes to cache coherence, especially DV semantics
>> c) tackling the thorny issue of distributed transactions
>> d) future-proofing (distributed RAID-n, journalling, rw repl, etc.)
>> e) protocol design issues (RXAFS_GetOSDlocation, the means by which
>> location data is XDR encoded, etc.)
>
> These all sound like things that belong on afs3-standardization.

Distributed transactions, at least, is not (strictly) an issue for
protocol standardization. Nor is necessarily future-proofing.

This discussion is going to end up bridging the purposes of both
openafs-devel and afs3-standardization, for better or for worse.