3 | |_ _ ___| |_ _ __ ___
4 | | | | / __| __| '__/ _ \
5 | | |_| \__ | |_| | | __/
6 |_|\__,_|___/\__|_| \___|
8 Lustre is an open-source, distributed parallel file system designed for
9 scalability, high-performance, and high-availability.
11 Lustre is purpose-built to provide a coherent, global POSIX-compliant
12 namespace for very large scale computer clusters, including the world's
13 largest supercomputer platforms.
15 It can support hundreds of petabytes of data storage and hundreds of
16 gigabytes per second in simultaneous, aggregate throughput.
19 More information about Lustre:
20 http://www.lustre.org/
21 Many resources for using, configuring, and troubleshooting Lustre are at:
22 http://wiki.lustre.org/
28 The low-volume list for announcements of new releases is at:
29 http://lists.lustre.org/listinfo.cgi/lustre-announce-lustre.org
30 The generic Lustre discussion mailing list is available at:
31 http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
32 The Lustre developer mailing list is at:
33 http://lists.lustre.org/pipermail/lustre-devel-lustre.org
35 To report bugs, please visit:
36 https://jira.whamcloud.com/
38 The official repository is hosted at:
39 https://git.whamcloud.com/
41 +----------------------+
42 | Building and Testing |
43 +----------------------+
45 Detailed instructions for building, configuring and running Lustre:
46 http://wiki.lustre.org/Compiling_Lustre
48 https://wiki.whamcloud.com/display/PUB/Getting+started+with+Lustre.
57 To play with a test Lustre filesystem:
59 ./lustre/tests/llmount.sh
63 ./lustre/tests/llmountcleanup.sh
69 Instructions for contributing patches for Lustre:
70 http://wiki.lustre.org/Submitting_Changes
72 http://wiki.lustre.org/Using_Gerrit
75 The Lustre Coding Style Guidelines can be found at:
76 http://wiki.lustre.org/Lustre_Coding_Style_Guidelines
78 The Lustre Test Script Style Guidelines can be found at:
79 http://wiki.lustre.org/Lustre_Script_Coding_Style
82 In order to improve the quality of patches submitted to the Lustre tree,
83 it is possible to automatically check every patch and commit against the
84 Lustre Coding Guidelines. To do this, run in the top-level lustre/ tree:
87 ln -s ../../contrib/git-hooks/{prepare-,}commit-msg ./