Instructions for building, configuring and running Lustre:
https://wiki.hpdd.intel.com/display/PUB/Building+Lustre+from+Source
and
https://wiki.hpdd.intel.com/display/PUB/Getting+started+with+Lustre.
Instructions for contributing patches for Lustre:
https://wiki.hpdd.intel.com/display/PUB/Submitting+Changes
and
https://wiki.hpdd.intel.com/display/PUB/Using+Gerrit
The Lustre Coding Style Guidelines can be found at:
https://wiki.hpdd.intel.com/display/PUB/Coding+Guidelines
The Lustre Test Script Style Guidelines can be found at:
https://wiki.hpdd.intel.com/display/PUB/Test+Coding+Style
In order to improve the quality of patches submitted to the Lustre tree,
it is possible to automatically check every patch and commit against the
Lustre Coding Guidelines. To do this, run in the top-level lustre/ tree:
cd .git/hooks
ln -s ../../contrib/git-hooks/{prepare-,}commit-msg ./
cd ../..
Nathaniel Clark
authored
When lustre-dkms is installed with other dkms packages, the PRE/POST scripts don't seem to function correctly. This includes the correct dkms.conf by default without having to recreate and reread it during build. Lustre-change: https://review.whamcloud.com/#/c/28210/ Lustre-commit: 2f4d11de2c37803822d6c1df0b7df6828477c11a Signed-off-by:Nathaniel Clark <nathaniel.l.clark@intel.com> Change-Id: Ic6f25480db40d784dfcb3b650f7c869716b903ee Reviewed-on: https://review.whamcloud.com/28224 Tested-by: Jenkins Tested-by: