Talk:Protocol Standardization Efforts - Revision history

Dano: Replacing page with 'I added this diagram to try to understand these pieces better. *RDP is missing from my picture'

2008-01-17T01:16:33Z

Replacing page with 'I added this diagram to try to understand these pieces better. *RDP is missing from my picture'

← Older revision		Revision as of 20:16, 16 January 2008
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.
	*RDP is missing from my picture		*RDP is missing from my picture
	~~Thinking about exnodes and erasure codings.~~
	*L-Store writes extra erasure allocations.
	**These allocations are also stored in the exnode file
	**These allocations are only useful to a data-rebuilder not the data user
	*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?

Dano at 01:15, 17 January 2008

2008-01-17T01:15:56Z

← Older revision		Revision as of 20:15, 16 January 2008
Line 3:		Line 3:
	Thinking about exnodes and erasure codings.		Thinking about exnodes and erasure codings.
	*L-Store writes extra erasure allocations.		*L-Store writes extra erasure allocations.
			**These allocations are also stored in the exnode file
			**These allocations are only useful to a data-rebuilder not the data user
	*L-Store can write a LoRS compatible exnode file that excludes the erasure allocations.		*L-Store can write a LoRS compatible exnode file that excludes the erasure allocations.
	**LoRS compatibility		**LoRS compatibility

Dano at 01:14, 17 January 2008

2008-01-17T01:14:17Z

← Older revision		Revision as of 20:14, 16 January 2008
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.

Dano: 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...

2008-01-17T00:10:32Z

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...

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-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?

Talk:Protocol Standardization Efforts - Revision history

Dano: Replacing page with 'I added this diagram to try to understand these pieces better. *RDP is missing from my picture'

Dano at 01:15, 17 January 2008

Dano at 01:14, 17 January 2008

Dano: 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...

Dano: 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...