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 terabytes per
16 second in simultaneous, aggregate throughput.
22 More information about Lustre:
23 http://www.lustre.org/
24 Many resources for using, configuring, and troubleshooting Lustre are at:
25 http://wiki.lustre.org/
27 For in-tree documentation, see the following directories:
36 The low-volume list for announcements of new releases is at:
37 http://lists.lustre.org/listinfo.cgi/lustre-announce-lustre.org
38 The generic Lustre discussion mailing list is available at:
39 http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
40 The Lustre developer mailing list is at:
41 http://lists.lustre.org/pipermail/lustre-devel-lustre.org
43 To report bugs, please visit:
44 https://jira.whamcloud.com/
46 The official repository is hosted at:
47 https://git.whamcloud.com/
49 +----------------------+
50 | Building and Testing |
51 +----------------------+
53 Detailed instructions for building, configuring and running Lustre:
54 http://wiki.lustre.org/Compiling_Lustre
56 https://wiki.whamcloud.com/display/PUB/Getting+started+with+Lustre.
65 To see all available make targets:
69 To play with a test Lustre filesystem:
71 ./lustre/tests/llmount.sh
75 ./lustre/tests/llmountcleanup.sh
81 Instructions for contributing patches for Lustre:
82 http://wiki.lustre.org/Submitting_Changes
84 http://wiki.lustre.org/Using_Gerrit
87 The Lustre Coding Style Guidelines can be found at:
88 http://wiki.lustre.org/Lustre_Coding_Style_Guidelines
90 The Lustre Test Script Style Guidelines can be found at:
91 http://wiki.lustre.org/Lustre_Script_Coding_Style
94 In order to improve the quality of patches submitted to the Lustre tree,
95 it is possible to automatically check every patch and commit against the
96 Lustre Coding Guidelines. To do this, run in the top-level lustre/ tree:
99 ln -s ../../contrib/git-hooks/{prepare-,}commit-msg ./