Architecture - HSM and Cache - Revision history

Docadmin at 21:12, 22 January 2010

2010-01-22T21:12:24Z

← Older revision		Revision as of 14:12, 22 January 2010
Line 1:		Line 1:
	'''''Note:''''' The content on this page reflects the state of design of a Lustre feature at a particular point in time and may contain outdated information.		'''''Note:''''' ''The content on this page reflects the state of design of a Lustre feature at a particular point in time and may contain outdated information.''

	== Deployments ==		== Deployments ==

Docadmin: Protected "Architecture - HSM and Cache" ([edit=sysop] (indefinite) [move=sysop] (indefinite))

2010-01-21T19:49:59Z

Protected "Architecture - HSM and Cache" ([edit=sysop] (indefinite) [move=sysop] (indefinite))

← Older revision	Revision as of 12:49, 21 January 2010
(No difference)

Docadmin: /* Deployments */

2010-01-18T23:58:53Z

Deployments

← Older revision		Revision as of 16:58, 18 January 2010
Line 1:		Line 1:
			'''''Note:''''' The content on this page reflects the state of design of a Lustre feature at a particular point in time and may contain outdated information.

	== Deployments ==		== Deployments ==

Docadmin: /* Migration */

2010-01-14T22:31:25Z

Migration

← Older revision		Revision as of 15:31, 14 January 2010
Line 27:		Line 27:
	## the OSS calls a 3pio_init(transport id, object range_desc, file_range_desc, transport_data, &3pio_fini, cb_data). There are rules		## the OSS calls a 3pio_init(transport id, object range_desc, file_range_desc, transport_data, &3pio_fini, cb_data). There are rules
	## the 3rd party transport		## the 3rd party transport

	~~[[Category:Architecture\|HSM]]~~

Docadmin: moved Architecture HSM and Cache to Architecture - HSM and Cache

2010-01-14T20:38:38Z

moved Architecture HSM and Cache to Architecture - HSM and Cache

← Older revision	Revision as of 13:38, 14 January 2010
(No difference)

Docadmin: moved Architecture cache and HSM to Architecture HSM and Cache

2010-01-14T20:28:20Z

moved Architecture cache and HSM to Architecture HSM and Cache

← Older revision	Revision as of 13:28, 14 January 2010
(No difference)

Docadmin: 1 revision

2010-01-14T20:06:55Z

1 revision

← Older revision	Revision as of 13:06, 14 January 2010
(No difference)

Adilger: s/LAID/SNS?

2007-10-16T03:13:08Z

s/LAID/SNS?

New page

== Deployments ==

Multiple Lustre features have significant overlap because they involve migration of file system objects:
* HSM
* Space rebalancing
* Data migration
* Caches for Lustre proxy services
* Server Network Striping rebuild
* 3rd party IO

[[Image:HSM-deploy.jpg]]

The architecture under consideration will target re-use of components.

== Software Subsystem Decomposition ==

== Migration ==

Migration enables an initiator to request that file data is read from one location and stored in another.

# '''3rd Party IO''' - A node requests through a lustre client that data can be read/written through a 3rd party transport
## the node gives {R,W}, offset, length, and a transport id, and transport data to a Lustre client
## the Lustre client decodes the ranges of the file that reside on OSS nodes and forwards corresponding range descriptors in the file and in the objects to the OSS nodes
## the OSS nodes prepare pages for the IO corresponding to the object ranges that need to read/written.
## the OSS calls a 3pio_init(transport id, object range_desc, file_range_desc, transport_data, &3pio_fini, cb_data). There are rules
## the 3rd party transport

[[Category:Architecture|HSM]]