Architecture - Pools of targets - Revision history

Docadmin at 02:48, 3 February 2010

2010-02-03T02:48:07Z

← Older revision		Revision as of 19:48, 2 February 2010
Line 44:		Line 44:
	If an extended attribute is encountered that contains a pool name the MDS routines using that attribute access the hash table and allocate objects accordingly.		If an extended attribute is encountered that contains a pool name the MDS routines using that attribute access the hash table and allocate objects accordingly.

	Command line utilities will start to use the libarg2 library. An additional ~~CFS~~ library will be added to allow comma separated sequences, ranges, kilo/mega/giga/tera/peta/exa/yotta bytes to be understood and other argument parsing issues.		Command line utilities will start to use the libarg2 library. An additional library will be added to allow comma separated sequences, ranges, kilo/mega/giga/tera/peta/exa/yotta bytes to be understood and other argument parsing issues.

Docadmin at 21:20, 22 January 2010

2010-01-22T21:20:41Z

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

	== Definitions ==		== Definitions ==

Docadmin: Protected "Architecture - Pools of targets" ([edit=sysop] (indefinite) [move=sysop] (indefinite))

2010-01-22T18:53:14Z

Protected "Architecture - Pools of targets" ([edit=sysop] (indefinite) [move=sysop] (indefinite))

← Older revision	Revision as of 11:53, 22 January 2010
(No difference)

Docadmin at 00:18, 19 January 2010

2010-01-19T00:18:17Z

← Older revision		Revision as of 17:18, 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.

	== Definitions ==		== Definitions ==

Docadmin: /* Implementation Constraints */

2010-01-14T23:48:33Z

Implementation Constraints

← Older revision		Revision as of 16:48, 14 January 2010
Line 43:		Line 43:

	Command line utilities will start to use the libarg2 library. An additional CFS library will be added to allow comma separated sequences, ranges, kilo/mega/giga/tera/peta/exa/yotta bytes to be understood and other argument parsing issues.		Command line utilities will start to use the libarg2 library. An additional CFS library will be added to allow comma separated sequences, ranges, kilo/mega/giga/tera/peta/exa/yotta bytes to be understood and other argument parsing issues.

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

Docadmin: /* Use cases */

2010-01-14T23:48:22Z

Use cases

← Older revision		Revision as of 16:48, 14 January 2010
Line 13:		Line 13:

	# A directory or file can be given an EA restricting striping to a pool		# A directory or file can be given an EA restricting striping to a pool
	## [~~http://arch.lustre.org/index.php?title=Architecture_Wide_Striping~~ Wide Striping] can use this to stripe over a large number of OSTs		## [[Architecture - Wide Striping\|Wide Striping]] can use this to stripe over a large number of OSTs
	## a subset of OSTs may be slower or faster than others and preferred for certain jobs		## a subset of OSTs may be slower or faster than others and preferred for certain jobs
	## doing [~~http://arch.lustre.org/index.php?title=Simple_Space_Balance_Migration~~ Object Migration] from a set OSTs to another pool of OSTs		## doing [[Architecture - Simple Space Balance Migration\|Object Migration]] from a set OSTs to another pool of OSTs
	# Pools can be assigned to specific clusters by client NID perferably or exclusively		# Pools can be assigned to specific clusters by client NID perferably or exclusively
	# Pools can be assigned to specific users or groups by UID/GID preferably or exclusively		# Pools can be assigned to specific users or groups by UID/GID preferably or exclusively

Docadmin: moved Pools of targets to Architecture - Pools of targets

2010-01-14T21:10:16Z

moved Pools of targets to Architecture - Pools of targets

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

Docadmin: 1 revision

2010-01-14T21:01:06Z

1 revision

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

Jcl: /* Command line Definitions */

2008-07-30T16:17:39Z

Command line Definitions

New page

== Definitions ==

'''Definition''': A pool is a name associated with a set of OSTs in a Lustre cluster.

Note the following:
# An OST can be in multiple pools
# No ordering is implied or defined
# Memberhship of a pool can change over time

The purpose of pools is to make object placement definitions more flexible.

== Use cases ==

# A directory or file can be given an EA restricting striping to a pool
## [http://arch.lustre.org/index.php?title=Architecture_Wide_Striping Wide Striping] can use this to stripe over a large number of OSTs
## a subset of OSTs may be slower or faster than others and preferred for certain jobs
## doing [http://arch.lustre.org/index.php?title=Simple_Space_Balance_Migration Object Migration] from a set OSTs to another pool of OSTs
# Pools can be assigned to specific clusters by client NID perferably or exclusively
# Pools can be assigned to specific users or groups by UID/GID preferably or exclusively
# Pools can be assigned to specific types of files by filename (e.g. *.mpg) to allow different striping for some files without requiring a default EA for all files in the output directory

== Command line Definitions ==

Pools can be defined using configuration log entries of the following type:
# lctl pool_new <fs name>.<pool name> Define a new pool, where pool name is an ascii string of up to 16 characters
# lctl pool_add <fs name>.<pool name> <ostname index list1> ... Add the named OSTs to the pool. Each addition leads to a new llog configuration record, but for convenience a single command can be given. <ostname index list> is <fs name>-OST<list> where <list> = N,<list> or <first[-last[/step]]>,<list>. if leading <fsname> or ending _UUID are missing, they are automatically added.
# lctl pool_remove <fs name>.<pool name> <ostname index list1> ... Remove the named OST from the pool
# lctl pool_destroy <fs name>.<pool name> Remove the definition of the pool

To set striping patterns:
lfs setstripe [--size|-s stripe_size] [--index|-i stripe_index]
[--count|-c stripe_count] [--pool|-p pool_name]
[--raid|-r raid_pattern] {file|dir}

To see already defined pools:
lfs poollist <fsname>[.<poolname>] | <absolute pathname>

== Implementation Constraints ==

When the configuration llog is parsed nodes that require the pool information the node will build a hash table mapping pool names to lists of OST's.

If an extended attribute is encountered that contains a pool name the MDS routines using that attribute access the hash table and allocate objects accordingly.

Command line utilities will start to use the libarg2 library. An additional CFS library will be added to allow comma separated sequences, ranges, kilo/mega/giga/tera/peta/exa/yotta bytes to be understood and other argument parsing issues.

[[Category:Architecture|Pools]]