LibLustre How-To Guide - Revision history

Sbarthel at 17:19, 22 February 2010

2010-02-22T17:19:39Z

← Older revision		Revision as of 10:19, 22 February 2010
Line 1:		Line 1:
			<small>''(Updated: Feb 2010)''</small>
	__TOC__		__TOC__
	For most Lustre™ versions, a library version of the Lustre client file system (''liblustre'') is available. ''liblustre'' gives a user application (linked with the library) access to Lustre file systems, without needing to mount Lustre (VFS) on the client. The key goals for the library are to provide a portable mechanism to access Lustre from different POSIX-compliant operating systems, and to provide access from microkernel-based systems.		For most Lustre™ versions, a library version of the Lustre client file system (''liblustre'') is available. ''liblustre'' gives a user application (linked with the library) access to Lustre file systems, without needing to mount Lustre (VFS) on the client. The key goals for the library are to provide a portable mechanism to access Lustre from different POSIX-compliant operating systems, and to provide access from microkernel-based systems.

Docadmin: /* Necessary Environmental Variables */

2010-02-02T20:25:08Z

Necessary Environmental Variables

Docadmin: /* Necessary Environmental Variables */

2010-02-02T20:23:40Z

Necessary Environmental Variables

← Older revision		Revision as of 13:23, 2 February 2010
Line 48:		Line 48:
	=== Necessary Environmental Variables ===		=== Necessary Environmental Variables ===

	~~There is a~~ simple script ''lustre/utils/lrun'' ~~which set~~ some environment variables:		A simple script ''lustre/utils/lrun'' sets some environment variables:

	* mount point		* mount point

Docadmin: /* Sanity Test */

2010-02-02T20:23:14Z

Sanity Test

← Older revision		Revision as of 13:23, 2 February 2010
Line 38:		Line 38:

	=== Sanity Test ===		=== Sanity Test ===
			A statically built-in liblustre test program ''lustre/liblustre/tests/sanity'' is also included in the lustre-tests RPM package. You can use this test to verify if liblustre is working properly:
	~~There is a~~ statically built-in liblustre test program ''lustre/liblustre/tests/sanity'' ~~that~~ is also included in the lustre-tests RPM package. You can use this test to verify if liblustre is working properly:

	sanity --target mgs_nid:/profile_name		sanity --target mgs_nid:/profile_name

Docadmin at 20:22, 17 December 2009

2009-12-17T20:22:28Z

← Older revision		Revision as of 13:22, 17 December 2009
Line 1:		Line 1:
			__TOC__
	For most Lustre™ versions, a library version of the Lustre client file system (''liblustre'') is available. ''liblustre'' gives a user application (linked with the library) access to Lustre file systems, without needing to mount Lustre (VFS) on the client. The key goals for the library are to provide a portable mechanism to access Lustre from different POSIX-compliant operating systems, and to provide access from microkernel-based systems.		For most Lustre™ versions, a library version of the Lustre client file system (''liblustre'') is available. ''liblustre'' gives a user application (linked with the library) access to Lustre file systems, without needing to mount Lustre (VFS) on the client. The key goals for the library are to provide a portable mechanism to access Lustre from different POSIX-compliant operating systems, and to provide access from microkernel-based systems.

Docadmin: Protected "LibLustre How-To Guide" ([edit=sysop] (indefinite) [move=sysop] (indefinite))

2009-12-16T18:21:48Z

Protected "LibLustre How-To Guide" ([edit=sysop] (indefinite) [move=sysop] (indefinite))

← Older revision	Revision as of 11:21, 16 December 2009
(No difference)

Docadmin at 18:21, 16 December 2009

2009-12-16T18:21:36Z

← Older revision		Revision as of 11:21, 16 December 2009
Line 1:		Line 1:
	For most ~~Lustre~~ versions, a library version of the Lustre client file system (''liblustre'') is available. ''liblustre'' gives a user application (linked with the library) access to Lustre file systems, without needing to mount Lustre (VFS) on the client. The key goals for the library are to provide a portable mechanism to access Lustre from different POSIX-compliant operating systems, and to provide access from microkernel-based systems.		For most Lustre™ versions, a library version of the Lustre client file system (''liblustre'') is available. ''liblustre'' gives a user application (linked with the library) access to Lustre file systems, without needing to mount Lustre (VFS) on the client. The key goals for the library are to provide a portable mechanism to access Lustre from different POSIX-compliant operating systems, and to provide access from microkernel-based systems.

	Currently, ''liblustre'' is still under development and only works on linux (i386 & x86_64, not tested on ia64).		Currently, ''liblustre'' is still under development and only works on linux (i386 & x86_64, not tested on ia64).

Docadmin: /* How to Use liblustre */

2009-12-14T22:36:54Z

How to Use liblustre

← Older revision		Revision as of 15:36, 14 December 2009
Line 22:		Line 22:
	== How to Use liblustre ==		== How to Use liblustre ==

	First, you must configure the networking on Lustre servers (MDS/OSTs) to accept connections on insecure ports. For example, add '''options lnet networks=tcp(eth0) accept=all''' to /etc/modprobe.conf before mounting the server(s) as usual. If you do not have any Lustre filesystem, the ''llmount.sh'' script will format temporary MDT and OST filesystems and start up MDS, OSS, and clients on that machine. You should umount the Lustre client at /mnt/lustre to avoid confusion between the liblustre client and the normal VFS client if you are also using that node for the liblustre client.		First, you must configure the networking on Lustre servers (MDS/OSTs) to accept connections on insecure ports. For example, add ''options lnet networks=tcp(eth0) accept=all'' to /etc/modprobe.conf before mounting the server(s) as usual. If you do not have any Lustre filesystem, the ''llmount.sh'' script will format temporary MDT and OST filesystems and start up MDS, OSS, and clients on that machine. You should umount the Lustre client at /mnt/lustre to avoid confusion between the liblustre client and the normal VFS client if you are also using that node for the liblustre client.

	=== Mount Target ===		=== Mount Target ===

Docadmin: /* Mount Target */

2009-12-14T22:36:36Z

Mount Target

← Older revision		Revision as of 15:36, 14 December 2009
Line 30:		Line 30:
	mgs_nid:/profile_name		mgs_nid:/profile_name

	* '''mgs_nid''' is the actual hostname of the MGS (or IP address if you do not have proper name resolution set up).		* ''mgs_nid'' is the actual hostname of the MGS (or IP address if you do not have proper name resolution set up).

	* '''profile_name''' is the profile name of the client mount point, also called the '''filesystem name''' in many configurations.		* ''profile_name'' is the profile name of the client mount point, also called the ''filesystem name'' in many configurations.

	For additional information on mount target, refer to Lustre documentation. This can be passed to most liblustre programs via the environment variable LIBLUSTRE_MOUNT_TARGET.		For additional information on mount target, refer to Lustre documentation. This can be passed to most liblustre programs via the environment variable LIBLUSTRE_MOUNT_TARGET.

Docadmin: /* Running Programs over liblustre */

2009-12-14T22:35:53Z

Running Programs over liblustre

← Older revision		Revision as of 15:35, 14 December 2009
Line 94:		Line 94:
	* grep		* grep

	You need to prepend 'lrun' before the programs that you intend to run:		You need to prepend ''lrun'' before the programs that you intend to run:

	lrun iozone -f /mnt/lustre/ioz_testfile -r 256k -s 1g		lrun iozone -f /mnt/lustre/ioz_testfile -r 256k -s 1g

← Older revision		Revision as of 13:25, 2 February 2010
Line 53:		Line 53:

	LIBLUSTRE_MOUNT_POINT=${LIBLUSTRE_MOUNT_POINT:-"/mnt/lustre"}		LIBLUSTRE_MOUNT_POINT=${LIBLUSTRE_MOUNT_POINT:-"/mnt/lustre"}
	This is where liblustre mounts the remote Lustre filesystem. The default location is ''/mnt/lustre''. Make sure this directory exists on the client system.		:This is where liblustre mounts the remote Lustre filesystem. The default location is ''/mnt/lustre''. Make sure this directory exists on the client system.

	* mount target		* mount target

	LIBLUSTRE_MOUNT_TARGET=${LIBLUSTRE_MOUNT_TARGET:-"your_mount_target"}		LIBLUSTRE_MOUNT_TARGET=${LIBLUSTRE_MOUNT_TARGET:-"your_mount_target"}
	Before using liblustre, you need to fill in the mount target (e.g. mdshost:/profile_name).		:Before using liblustre, you need to fill in the mount target (e.g. mdshost:/profile_name).

	* shared library		* shared library

	LD_PRELOAD=${LD_PRELOAD:-"/usr/lib/liblustre.so"}		LD_PRELOAD=${LD_PRELOAD:-"/usr/lib/liblustre.so"}
	Make sure you have installed lustre/liblustre/liblustre.so in this location.		:Make sure you have installed lustre/liblustre/liblustre.so in this location.

	* server port		* server port

	LNET_ACCEPT_PORT=${LNET_ACCEPT_PORT:-"988"}		LNET_ACCEPT_PORT=${LNET_ACCEPT_PORT:-"988"}
	This is optional, necessary only when the Lustre server doesn't listen on the default port (e.g. server uses the lnet option "accept_port" to change its port). It's only meaningful for the socklnd (TCP network).		:This is optional, necessary only when the Lustre server doesn't listen on the default port (e.g. server uses the lnet option "accept_port" to change its port). It's only meaningful for the socklnd (TCP network).

	* other LNET options		* other LNET options

	You'd need to set LNET_ROUTES for the liblustre client to use routing to access the remote filesystem.		:You'd need to set LNET_ROUTES for the liblustre client to use routing to access the remote filesystem.

	=== Running Programs over liblustre ===		=== Running Programs over liblustre ===