On Mon, 2010-05-10 at 16:28 -0400, Jeff Darcy wrote:
On 05/10/2010 03:13 PM, Jeff Garzik wrote:
> If I understand the vinzvault project correctly, it will be used to
> provide block-level storage to a node, somewhat similar to Amazon's
> Elastic Block Storage (EBS).
>
> For that case, each block device will likely have only a single writer:
> the kernel/FUSE to which vinzvault is providing storage.
Not only a single writer, then, but no sharing (even for read) between
that writer and anyone else. That certainly does make things simpler.
Is there any plan to implement an overlay/COW scheme as part of
vinzvault so that nodes can share a base object read-only and store
private changes in a per-instance object, or will we rely on the block
layer for that?
I was thinking 2.0+ for COW and snapshots. Hardest part at this point
is to get a working D1HT that integrates with a DB. A functional D1HT
is probably about 5k lines of C code of pure protocol - so that is quite
a bit of chunk of work to knock out :)
The best way to sum up 1.0 is D1HT where every node participates +
Tokyocabinet + fuse + autotool + basic replica consistency and
correctness. Eg really rough prototype.
Regards
-steve
_______________________________________________
vinzvault mailing list
vinzvault(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/vinzvault