Table of Contents
This chapter provides on overview of the procedures required to set up, install and configure a Lustre file system.
If the Lustre file system is new to you, you may find it helpful to refer to Introducing the Lustre* File System for a description of the Lustre architecture, file system components and terminology before proceeding with the installation procedure.
To set up Lustre file system hardware and install and configure the Lustre software, refer the the chapters below in the order listed:
-
(Required) Set up your Lustre file system hardware.
See Determining Hardware Configuration Requirements and Formatting Options - Provides guidelines for configuring hardware for a Lustre file system including storage, memory, and networking requirements.
-
(Optional - Highly Recommended) Configure storage on Lustre storage devices.
See Configuring Storage on a Lustre File System - Provides instructions for setting up hardware RAID on Lustre storage devices.
-
(Optional) Set up network interface bonding.
See Setting Up Network Interface Bonding - Describes setting up network interface bonding to allow multiple network interfaces to be used in parallel to increase bandwidth or redundancy.
-
(Required) Install Lustre software.
See Installing the Lustre Software - Describes preparation steps and a procedure for installing the Lustre software.
-
(Optional) Configure Lustre Networking (LNet).
See Configuring Lustre Networking (LNet) - Describes how to configure LNet if the default configuration is not sufficient. By default, LNet will use the first TCP/IP interface it discovers on a system. LNet configuration is required if you are using InfiniBand or multiple Ethernet interfaces.
-
(Required) Configure the Lustre file system.
See Configuring a Lustre File System - Provides an example of a simple Lustre configuration procedure and points to tools for completing more complex configurations.
-
(Optional) Configure Lustre failover.
See Configuring Failover in a Lustre File System - Describes how to configure Lustre failover.