From fefc9b7b1f7655e94cf65f1e4ab77ac13e5cb235 Mon Sep 17 00:00:00 2001 From: Richard Henwood Date: Tue, 17 May 2011 14:44:51 -0500 Subject: [PATCH] FIX: xrefs --- InstallingLustre.xml | 281 ++++++++++++++++++++++++--------------------------- 1 file changed, 134 insertions(+), 147 deletions(-) diff --git a/InstallingLustre.xml b/InstallingLustre.xml index 8cb3ca1..7c84dcb 100644 --- a/InstallingLustre.xml +++ b/InstallingLustre.xml @@ -1,30 +1,33 @@ - + Installing the Lustre Software + This chapter describes how to install the Lustre software. It includes: - - Preparing to Install the Lustre Software - - - - - - Lustre Installation Procedure - - - - - - For hardware/system requirements, see Chapter 5: Setting Up a Lustre File System. -
- <anchor xml:id="dbdoclet.50438261_pgfId-1294006" xreflabel=""/> -
- 8.1 <anchor xml:id="dbdoclet.50438261_99193" xreflabel=""/>Preparing to Install the Lustre Software - If you are using a supported Linux distribution and architecture, you can install Lustre from downloaded packages (RPMs). For a list of supported configurations, see the Lustre_2.0 topic on the Lustre wiki. - A list of supported Lustre LNET drivers can be found in Chapter 2: Understanding Lustre Networking (LNET). - If you are not using a supported configuration, you can install Lustre directly from the source code. For more information on this installation method, see Chapter 29: Installing Lustre from Source Code. + + + + + + + + + + + + + + + + + + For hardware/system requirements, see . +
+ 8.1 Preparing to Install the Lustre Software + If you are using a supported Linux distribution and architecture, you can install Lustre from downloaded packages (RPMs). For a list of supported configurations, see the Lustre 2.0 topic on the Lustre wiki. + A list of supported Lustre LNET drivers can be found in . + If you are not using a supported configuration, you can install Lustre directly from the source code. For more information on this installation method, see .
<anchor xml:id="dbdoclet.50438261_pgfId-1292590" xreflabel=""/>8.1.1 <anchor xml:id="dbdoclet.50438261_37079" xreflabel=""/>Required Software To install Lustre, the following are required: @@ -32,43 +35,29 @@ (On Linux servers only) Linux kernel patched with Lustre-specific patches for your platform and architecture. A Linux patched kernel can be installed on a client if it is desireable to use the same kernel on all nodes, but this is not required. - + Lustre modules compiled for the Linux kernel (see for which packages are required for servers and clients in your configuration). - Lustre modules compiled for the Linux kernel (see TABLE 8-1 for which packages are required for servers and clients in your configuration). - - - - - - Lustre utilities required for configuring Lustre (see TABLE 8-1 for which packages are required for servers and clients in your configuration). - - - + Lustre utilities required for configuring Lustre (see for which packages are required for servers and clients in your configuration). (On Linux servers only)e2fsprogs package containing Lustre-specific tools (e2fsck and lfsck) used to repair a backing file system. This replaces the existing e2fsprogs package but provides complete e2fsprogs functionality - - - (Optional) Network-specific kernel modules and libraries such as the Lustre-specific OFED package required for an InfiniBand network interconnect. - - - - At least one Lustre RPM must be installed on each server and on each client in a Lustre file system. TABLE 8-1 lists required Lustre packages and indicates where they are to be installed. Some Lustre packages are installed on Lustre servers (MGS, MDS, and OSSs), some are installed on Lustre clients, and some are installed on all Lustre nodes. +At least one Lustre RPM must be installed on each server and on each client in a Lustre file system. lists required Lustre packages and indicates where they are to be installed. Some Lustre packages are installed on Lustre servers (MGS, MDS, and OSSs), some are installed on Lustre clients, and some are installed on all Lustre nodes. . - - <anchor xml:id="dbdoclet.50438261_pgfId-1295320" xreflabel=""/> TABLE 8-1 <anchor xml:id="dbdoclet.50438261_21654" xreflabel=""/> Lustre required packages, descriptions and installation guidance + +
+ Lustre required packages, descriptions and installation guidance - - + + - - + + Lustre Package @@ -166,38 +155,25 @@ Several third-party utilities are must be installed on servers: e2fsprogs : Lustre requires a recent version of e2fsprogs that understands extents. Use e2fsprogs-1.41-10-sun2 or later, available at: - - - - - - http://downloads.lustre.org/public/tools/e2fsprogs/ + http://downloads.lustre.org/public/tools/e2fsprogs/ A quilt patchset of all changes to the vanilla e2fsprogs is available in e2fsprogs-{version}-patches.tgz. - - - - - - Note -The Lustre-patched e2fsprogs utility is only required on machines that mount backend (ldiskfs) file systems, such as the OSS, MDS and MGS nodes. It does not need to be loaded on clients. - - - - - - Perl - Various userspace utilities are written in Perl. Any recent version of Perl will work with Lustre. + The Lustre-patched e2fsprogs utility is only required on machines that mount backend (ldiskfs) file systems, such as the OSS, MDS and MGS nodes. It does not need to be loaded on clients. + - - + + + Perl - Various userspace utilities are written in Perl. Any recent version of Perl will work with Lustre. - + +
<anchor xml:id="dbdoclet.50438261_pgfId-1292903" xreflabel=""/>8.1.1.3 <anchor xml:id="dbdoclet.50438261_29838" xreflabel=""/>(Optional) <anchor xml:id="dbdoclet.50438261_marker-1292902" xreflabel=""/>High-Availability Software - If you plan to enable failover server functionality with Lustre (either on an OSS or the MDS), you must add high-availability (HA) software to your cluster software. For more information, see Setting up High-Availability (HA) Software with Lustre. + If you plan to enable failover server functionality with Lustre (either on an OSS or the MDS), you must add high-availability (HA) software to your cluster software. For more information, see Setting up High-Availability (HA) Software with Lustre.
<anchor xml:id="dbdoclet.50438261_pgfId-1292911" xreflabel=""/>8.1.1.4 (Optional) Debugging Tools and Other Optional Packages - A variety of optional packages are provided on the Lustre download site. These include debugging tools, test programs and scripts, Linux kernel and Lustre source code, and other packages. + A variety of optional packages are provided on the Whamcloud download site. These include debugging tools, test programs and scripts, Linux kernel and Lustre source code, and other packages. For more information about debugging tools, see the topic Debugging Lustre on the Lustre wiki.
@@ -208,102 +184,92 @@ (Required)Disable Security-Enhanced Linux (SELinux) on servers and clients . Lustre does not support SELinux. Therefore, disable the SELinux system extension on all Lustre nodes and make sure other security extensions, like Novell AppArmorand network packet filtering tools (such as iptables) do not interfere with Lustre. See Step 3 in the Lustre Installation Procedure below. - - - (Required)Maintain uniform user and group databases on all cluster nodes . Use the same user IDs (UID) and group IDs (GID) on all clients. If use of supplemental groups is required, verify that the group_upcall requirements have been met. See User/Group Cache Upcall. - - - (Recommended)Provide remote shell access to clients . Although not strictly required to run Lustre, we recommend that all cluster nodes have remote shell client access to facilitate the use of Lustre configuration and monitoring scripts. Parallel Distributed SHell (pdsh) is preferable, although Secure SHell (SSH) is acceptable. - - - (Recommended)Ensure client clocks are synchronized . Lustre uses client clocks for timestamps. If clocks are out of sync between clients, files will appear with different time stamps when accessed by different clients. Drifting clocks can also cause problems, for example, by making it difficult to debug multi-node issues or correlate logs, which depend on timestamps. We recommend that you use Network Time Protocol (NTP) to keep client and server clocks in sync with each other. For more information about NTP, see: http://www.ntp.org. - - - -
- 8.2 <anchor xml:id="dbdoclet.50438261_41900" xreflabel=""/>Lustre Installation Procedure - - - - - - -
- - - - - - - - - Caution -Before installing Lustre, back up ALL data. Lustre contains kernel modifications which interact with storage devices and may introduce security issues and data loss if not installed, configured or administered properly. - - - - +
+ 8.2 Lustre Installation Procedure + + +Before installing Lustre, back up ALL data. Lustre contains kernel modifications which interact with storage devices and may introduce security issues and data loss if not installed, configured or administered properly. + + Use this procedure to install Lustre from RPMs. - 1. Verify that all Lustre installation requirements have been met. + + + Verify that all Lustre installation requirements have been met. For more information on these prerequisites, see: - Hardware requirements in Chapter 5: Setting Up a Lustre File System + Hardware requirements in - - - - Software and environmental requirements in Preparing to Install the Lustre Software - - - + Software and environmental requirements in - 2. Download the Lustre RPMs. - a. On the Lustre download site, select your platform. + + + Download the Lustre RPMs. + + + On the Lustre download site, select your platform. The files required to install Lustre (kernels, modules and utilities RPMs) are listed for the selected platform. - b. Download the required files. - 3. Install the Lustre packages on the servers. - a. Refer to TABLE 8-1 to determine which Lustre packages are to be installed on servers for your platform and architecture. + + + Download the required files. + + + + + Install the Lustre packages on the servers. + + + Refer to to determine which Lustre packages are to be installed on servers for your platform and architecture. Some Lustre packages are installed on the Lustre servers (MGS, MDS, and OSSs). Others are installed on Lustre clients. Lustre packages must be installed in the order specified in the following steps. - b. Install the kernel, modules and ldiskfs packages. + + + Install the kernel, modules and ldiskfs packages. Use the rpm -ivh command to install the kernel, module and ldiskfs packages. - - - -
- - Note -It is not recommended that you use the rpm -Uvh command to install a kernel, because this may leave you with an unbootable system if the new kernel doesn’t work for some reason. - - - - + + + It is not recommended that you use the rpm -Uvh command to install a kernel, because this may leave you with an unbootable system if the new kernel doesn't work for some reason. + + For example, the command in the following example would install required packages on a server with Infiniband networking$ rpm -ivh kernel-<ver>_lustre-<ver> kernel-ib-<ver> \ lustre-modules-<ver> lustre-ldiskfs-<ver> - c. Update the bootloader (grub.conf or lilo.conf) configuration file as needed. - i. Verify that the bootloader configuration file has been updated with an entry for the patched kernel. + + + Update the bootloader (grub.conf or lilo.conf) configuration file as needed. + + + Verify that the bootloader configuration file has been updated with an entry for the patched kernel. Before you can boot to a new distribution or kernel, there must be an entry for it in the bootloader configuration file. Often this is added automatically when the kernel RPM is installed. - ii. Disable security-enhanced (SE) Linux on servers and clients by including an entry in the bootloader configuration file as shown below: + + + Disable security-enhanced (SE) Linux on servers and clients by including an entry in the bootloader configuration file as shown below: selinux=0 - d. Install the utilities/userspace packages. + + + + + Install the utilities/userspace packages. Use the rpm -ivh command to install the utilities packages. For example: $ rpm -ivh lustre-<ver> - e. Install the e2fsprogs package. + + + Install the e2fsprogs package. Use the rpm -ivh command to install the e2fsprogs package. For example: $ rpm -ivh e2fsprogs-<ver> @@ -320,29 +286,50 @@ - f. (Optional) To add optional packages to your Lustre file system, install them now. - Optional packages include file system creation and repair tools, debugging tools, test programs and scripts, Linux kernel and Lustre source code, and other packages. A complete list of optional packages for your platform is provided on the Lustre download site. - 4. Install the Lustre packages on the clients. - a. Refer to TABLE 8-1 to determine which Lustre packages are to be installed on clients for your platform and architecture. - b. Install the module packages for clients. + + + (Optional) To add optional packages to your Lustre file system, install them now. + Optional packages include file system creation and repair tools, debugging tools, test programs and scripts, Linux kernel and Lustre source code, and other packages. A complete list of optional packages for your platform is provided on the Whamcloud wiki. + + + + + Install the Lustre packages on the clients. + Refer to to determine which Lustre packages are to be installed on clients for your platform and architecture. + Install the module packages for clients. Use the rpm -ivh command to install the lustre-client and lustre-client-modules-<ver> packages. For example: $ rpm -ivh lustre-client-modules-<ver> kernel-ib-<ver> - c. Install the utilities/userspace packages for clients. + Install the utilities/userspace packages for clients. Use the rpm -ivh command to install the utilities packages. For example: $ rpm -ivh lustre-client - d. Update the bootloader (grub.conf or lilo.conf) configuration file as needed. - i. Verify that the bootloader configuration file has been updated with an entry for the patched kernel. + Update the bootloader (grub.conf or lilo.conf) configuration file as needed. + + + Verify that the bootloader configuration file has been updated with an entry for the patched kernel. Before you can boot to a new distribution or kernel, there must be an entry for it in the bootloader configuration file. Often this is added automatically when the kernel RPM is installed. - ii. Disable security-enhanced (SE) Linux on servers and clients by including an entry in the bootloader configuration file as shown below: + + + Disable security-enhanced (SE) Linux on servers and clients by including an entry in the bootloader configuration file as shown below: selinux=0 - 5. Reboot the patched clients and the servers. - a. If you applied the patched kernel to any clients, reboot them. + + + + + Reboot the patched clients and the servers. + + + If you applied the patched kernel to any clients, reboot them. Unpatched clients do not need to be rebooted. - b. Reboot the servers. - To configure LNET, go next to Chapter 9: Configuring Lustre Networking (LNET). If default settings will be used for LNET, go to Chapter 10: Configuring Lustre. + + + Reboot the servers. + + + To configure LNET, go next to . If default settings will be used for LNET, go to . + + - -- 1.8.3.1