Talk:Protocol Standardization Efforts: Difference between revisions

From ReddNet
Jump to navigation Jump to search
(New page: I added this diagram to try to understand these pieces better. *RSP is missing from my picture Thinking about exnodes and erasure codings. *L-Store writes extra erasure allocations. *L-Sto...)
 
No edit summary
Line 1: Line 1:
I added this diagram to try to understand these pieces better.
I added this diagram to try to understand these pieces better.
*RSP is missing from my picture
*RDP is missing from my picture
Thinking about exnodes and erasure codings.
Thinking about exnodes and erasure codings.
*L-Store writes extra erasure allocations.
*L-Store writes extra erasure allocations.

Revision as of 20:14, 16 January 2008

I added this diagram to try to understand these pieces better.

  • RDP is missing from my picture

Thinking about exnodes and erasure codings.

  • L-Store writes extra erasure allocations.
  • L-Store can write a LoRS compatible exnode file that excludes the erasure allocations.
    • LoRS compatibility
    • LoRS does not have access to L-Store's capability to regain a file.

Is this OK?

  • The data user does not need (and probably should not be bothered with) to handle error recovery.
  • data recovery, data warming, etc all are done by services/agents apart from the data consumer.
  • So what user interface and development API are needed by the data users?
  • command line tools
    • file movement
    • file system (some use the term namespace management) tools
      • list files, create directories, etc
  • C/C++ API
    • just need my simple offsets and lengths
    • would like to read a vector of data blocks (non-blocked reads)
    • don't want to deal with erasure stuff at this point.
      • is there a nice way to recover from errors?