首页 oscar4.2-quick_install

oscar4.2-quick_install

举报
开通vip

oscar4.2-quick_install How to Install an OSCAR Cluster Quick Start Install Guide Software Version 4.2 Documentation Version 4.2 http://oscar.sourceforge.net/ oscar-users@lists.sourceforge.net The Open Cluster Group http://www.openclustergroup.org/ October 28, 2005 1 Cont...

oscar4.2-quick_install
How to Install an OSCAR Cluster Quick Start Install Guide Software Version 4.2 Documentation Version 4.2 http://oscar.sourceforge.net/ oscar-users@lists.sourceforge.net The Open Cluster Group http://www.openclustergroup.org/ October 28, 2005 1 Contents 1 Introduction 4 1.1 Latest Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.3 Supported Distributions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.4 Minimum System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.5 Document Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 2 Downloading an OSCAR Distribution Package 6 3 Release Notes 6 3.1 Release Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3.2 Notes for All Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3.3 Red Hat Enterprise Linux 4 & Fedora Core 3 SELinux Conflict . . . . . . . . . . . . . . . 9 3.4 Red Hat Enterprise Linux 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 3.5 CentOS 4 ia64 Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 3.6 Red Hat Enterprise Linux 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 3.7 Mandriva Linux (previously known as ”Mandrake Linux”) Notes . . . . . . . . . . . . . . . 10 3.8 Fedora Core 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 4 Quick Cluster Installation Procedure 12 4.1 Server Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 4.1.1 Install Linux on the server machine . . . . . . . . . . . . . . . . . . . . . . . . . . 12 4.1.2 Disk space and directory considerations . . . . . . . . . . . . . . . . . . . . . . . . 12 4.1.3 Download a copy of OSCAR and unpack on the server . . . . . . . . . . . . . . . . 12 4.1.4 Configure and Install OSCAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.1.5 Configure the ethernet adapter for the cluster . . . . . . . . . . . . . . . . . . . . . 13 4.1.6 Copy distribution installation RPMs to /tftpboot/rpm . . . . . . . . . . . . . . 14 4.2 Launching the OSCAR Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 4.3 Downloading Additional OSCAR Packages . . . . . . . . . . . . . . . . . . . . . . . . . . 14 4.4 Selecting Packages to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.5 Configuring OSCAR Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.5.1 Selecting a Default MPI Implementation . . . . . . . . . . . . . . . . . . . . . . . 15 4.6 Install OSCAR Server Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.7 Build OSCAR Client Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.8 Define OSCAR Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 4.9 Setup Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 4.10 Monitor Cluster Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 4.11 Client Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 4.11.1 Network boot the client nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 4.11.2 Check completion status of nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 4.11.3 Reboot the client nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 4.12 Complete the Cluster Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 4.13 Test Cluster Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 4.14 Congratulations! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 4.15 Adding and Deleting client nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 4.15.1 Adding OSCAR clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2 4.15.2 Deleting clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 4.16 Install/Uninstall OSCAR Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 4.16.1 Selecting the Right Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 4.16.2 Single Image Restriction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 4.16.3 Failures to Install and Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 4.16.4 More Debugging Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 4.17 Starting over – installing OSCAR again . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 3 1 Introduction OSCAR version 4.2 is a snapshot of the best known methods for building, programming, and using clusters. It consists of a fully integrated and easy to install software bundle designed for high performance cluster computing (HPC). Everything needed to install, build, maintain, and use a modest sized Linux cluster is included in the suite, making it unnecessary to download or even install any individual software packages on your cluster. OSCAR is the first project by the Open Cluster Group. For more information on the group and its projects, visit its website http://www.OpenClusterGroup.org/. This document provides a step-by-step installation guide for system administrators, as well as a detailed explanation of what is happening as you install. Note that this installation guide is specific to OSCAR version 4.2. 1.1 Latest Documentation Please be sure that you have the latest version of this document. It is possible (and probable!) that newer versions of this document were released on the main OSCAR web site after the software was released. You are strongly encouraged to check http://oscar.sourceforge.net/ for the latest version of these instructions before proceeding. Document versions can be compared by checking their version number and date on the cover page. 1.2 Terminology A common term used in this document is cluster, which refers to a group of individual computers bundled together using hardware and software in order to make them work as a single machine. Each individual machine of a cluster is referred to as a node. Within the OSCAR cluster to be installed, there are two types of nodes: server and client. A server node is responsible for servicing the requests of client nodes. A client node is dedicated to computation. An OSCAR cluster consists of one server node and one or more client nodes, where all the client nodes [currently] must have homogeneous hardware. The software contained within OSCAR does support doing multiple cluster installs from the same server, but that process is outside the scope of this guide. An OSCAR package is a set of files that is used to install a software package in an OSCAR cluster. An OSCAR package can be as simple as a single RPM file, or it can be more complex, perhaps including a mixture of RPM and other auxiliary configuration / installation files. OSCAR packages provide the majority of functionality in OSCAR clusters. OSCAR packages fall into one of three categories: • Core packages are required for the operation of OSCAR itself (mostly involved with the installer). • Included packages are shipped in the official OSCAR distribution. These are usually authored and/or packaged by OSCAR developers, and have some degree of official testing before release. • Third party packages are not included in the official OSCAR distribution; they are “add-ons” that can be unpacked in the OSCAR tree, and therefore installed using the OSCAR installation framework. 1.3 Supported Distributions OSCAR has been tested to work with several distributions. Table 1 lists each distribution and version and specifies the level of support for each. In order to ensure a successful installation, most users should stick to a distribution that is listed as Fully supported. 4 Administrator 高亮 Distribution and Release Architecture Status Red Hat Enterprise Linux 3 x86 Fully supported Red Hat Enterprise Linux 3 x86 64 Fully supported Red Hat Enterprise Linux 3 ia64 Fully supported Red Hat Enterprise Linux 4 x86 Fully supported Red Hat Enterprise Linux 4 x86 64 Fully supported Red Hat Enterprise Linux 4 ia64 Fully supported Fedora Core 2 x86 Fully supported Fedora Core 3 x86 Fully supported Mandriva Linux 10.0 x86 Fully supported Mandriva Linux 10.1 x86 Fully supported Table 1: OSCAR supported distributions Clones of supported distributions, especially open source rebuilds of RedHat Enterprise Linux such as CentOS and Scientific Linux, should work but are not officially tested. See the release notes (Section 3) for your distribution for known issues. 1.4 Minimum System Requirements The following is a list of minimum system requirements for the OSCAR server node: • CPU of i586 or above • A network interface card that supports a TCP/IP stack • If your OSCAR server node is going to be the router between a public network and the cluster nodes, you will need a second network interface card that supports a TCP/IP stack • At least 4GB total free space – 2GB under / and 2GB under /var • An installed version of Linux, preferably a Fully supported distribution from Table 1 The following is a list of minimum system requirements for the OSCAR client nodes: • CPU of i586 or above • A disk on each client node, at least 2GB in size (OSCAR will format the disks during the installation) • A network interface card that supports a TCP/IP stack1 • Same Linux distribution and version as the server node • All clients must have the same architecture (e.g., ia32 vs. ia64) • Monitors and keyboards may be helpful, but are not required • Floppy or PXE enabled BIOS 1Beware of certain models of 3COM cards – not all models of 3COM cards are supported by the installation Linux kernel that is shipped with OSCAR. See the OSCAR web site for more information. 5 1.5 Document Organization Due to the complicated nature of putting together a high-performance cluster, it is strongly suggested that even experienced administrators read this document through, without skipping any sections, and then use the detailed installation procedure to install your OSCAR cluster. Novice users will be comforted to know that anyone who has installed and used Linux can successfully navigate through the OSCAR cluster install. The rest of this document is organized as follows. First, Section 2 tells how to obtain an OSCAR version 4.2 distribution package. Next, the “Release Notes” section (Section 3) that applies to OSCAR version 4.2 contains some requirements and update issues that need to be resolved before the install. Section 4 details the cluster installation procedure (the level of detail lies somewhere between “the install will now update some files” and “the install will now replace the string ‘xyz’ with ‘abc’ in file some file.”) More information is available on the OSCAR web site and archives of the various OSCAR mailing lists. If you have a question that cannot be answered by this document (including answers to common installation problems), be sure to visit the OSCAR web site: http://oscar.sourceforge.net/ 2 Downloading an OSCAR Distribution Package The OSCAR distribution packages can be downloaded from: http://oscar.sourceforge.net/ Note that there are actually three flavors of distribution packages for OSCAR, depending on your band- width and installation/development needs: 1. “Regular”: All the OSCAR installation material that most users need to install and operate an OSCAR cluster. 2. “Extra Crispy”: Same as Regular, except that the SRPMs for most of the RPMs in OSCAR are also included. SRPMs are not required for installation or normal operation of an OSCAR cluster. This distribution package is significantly larger than Regular, and is not necessary for most users – only those who are interested in source RPMs need the Extra Crispy distribution. The SRPMs can be found under packages/*/SRPMS/ directories. 3. “Secret Sauce”: This distribution contains only the SRPMs for RPMs in OSCAR in the Regular and Extra Crispy distributions (it’s essentially (Extra Crispy - Regular)). It is intended only for those who initially downloaded the Regular distribution and later decided that they wanted the SRPMs as well. The Secret Sauce distribution is intended to be expanded over your Regular installation – it will create packages/*/SRPMS/ directories and populate them with the relevant .src.rpm files. All three distributions can be downloaded from the main OSCAR web page. 3 Release Notes The following release notes apply to OSCAR version 4.2. 6 3.1 Release Features • x86 64 support for Red Hat Enterprise Linux 3 & 4, • Fedora Core 3, Red Hat Enterprise Linux 4 and Mandriva Linux 10.1 support • New feature! “Monitor Cluster Deployment” in Wizard • Ganglia updated to v3.0.1 • PVM updated to v3.4.5+4 • Torque updated to v1.2.0p5 • SystemImager updated to v3.5.3 • MPICH updated to v1.2.7 • AutoInstallFloppy changed to AutoInstallCD due to large kernel images. • Replaced tftp-server with atftp-server for better scalability • Software RAIDs on cluster nodes are now supported 3.2 Notes for All Systems • The OSCAR installer GUI provides little protection for user mistakes. If the user executes steps out of order, or provides erroneous input, Bad Things may happen. Users are strongly encouraged to closely follow the instructions provided in this document. • Each package in OSCAR has its own installation and release notes. See the full Installation Guide for these notes. • All nodes must have a hostname other than “localhost” that does not contain any underscores (“ ”) or periods “.”. Some distributions complicate this by putting a line such as as the following in /etc/hosts: 127.0.0.1 localhost.localdomain localhost yourhostname.yourdomain yourhostname If this occurs the file should be separated as follows: 127.0.0.1 localhost.localdomain localhost 192.168.0.1 yourhostname.yourdomain yourhostname • A domain name must be specified for the client nodes when defining them. • Although OSCAR can be installed on pre-existing server nodes, it is typically easiest to use a machine that has a new, fresh install of a distribution listed in Table 1 with no updates installed. If the updates are installed, there may be conflicts in RPM requirements. It is recommended to install Red Hat updates after the initial OSCAR installation has completed. 7 • The “Development Tools” packages for are not default packages in all distributions and are required for installation. • The following benign warning messages will appear multiple times during the OSCAR installation process: awk: cmd. line:2: fatal: cannot open file ‘/etc/fstab’ for reading (No such file or directory) rsync_stub_dir: no such variable at ... Use of uninitialized value in pattern match (m//) at /usr/lib/perl5/site_perl/oda.pm ... It is safe to ignore these messages. • The OSCAR installer will install the MySQL package on the server node if it is not already installed. A random password will be automatically generated for the oscar user to access the oscar database. This password will be stored in the file /etc/odapw. It should not be needed by other users. • The OSCAR installer GUI currently does not support deleting a node and adding the same node back in the same session. If you wish to delete a node and then add it back, you must delete the node, close the OSCAR installer GUI, launch the OSCAR installer GUI again, and then add the node. • If ssh produces warnings when logging into the compute nodes from the OSCAR head node, the C3 tools (e.g., cexec) may experience difficulties. For example, if you use ssh to login in to the OSCAR head node from a terminal that does not support X windows and then try to run cexec, you might see a warning message in the cexec output: Warning: No xauth data; using fake authentication data for X11 forwarding. Although this is only a warning message from ssh, cexec may interpret it as a fatal error, and not run across all cluster nodes properly (e.g., the button will likely not work properly). Note that this is actually an ssh problem, not a C3 problem. As such, you need to eliminate any warning messages from ssh (more specifically, eliminate any output from stderr). In the example above, you can tell the C3 tools to use the “-x” switch to ssh in order to disable X forwarding: # export C3_RSH=’ssh -x’ # cexec uptime The warnings about xauth should no longer appear (and the button should work properly). • The SIS multicast facility (Flamethrower) is “experimentally” supported. If you are having problems with multicast and would like to experiment please check the oscar-users and/or sisuite-users mailing lists for tips. 8 • Due to some distribution portability issues, OSCAR currently installs a “compatibility” (python2- -compat-1.0-1) RPM to resolve the Python2 prerequisite that is slightly different across different Linux distributions. Also see the file packages/c3/RPMS/NOTE.python2. • FutureWarning message during APItests on Python2.3 based systems. The following is a warning message about the for the version of TwistedMatrix used by the APItest tool. It is only a warning and can be ignored. Running Installation tests for pvm /usr/lib/python2.3/site-packages/twisted/internet/defer.py:398: FutureWarning: hex()/oct() of negative int will return a signed string in Python 2.4 and up return "<%s at %s>" % (cname, hex(id(self))) • In some cases, the test window that is opened from the OSCAR wizard may close suddenly when there is a test failure. If this happens, run the test script, testing/test cluster, manually in a shell window to diagnose the problem. 3.3 Red Hat Enterprise Linux 4 & Fedora Core 3 SELinux Conflict • Due to issues with displaying graphs under Ganglia, and installing RPMs in a chroot environment (needed to build OSCAR images), SELinux should be disabled before installing OSCAR. During installation, it can be deactivated on the same screen as the firewall. If it is currently active it can be turned off in /etc/selinux/config by setting SELINUX to “disabled” and rebooting. 3.4 Red Hat Enterprise Linux 4 • On x86 systems using Red Hat Enterprise Linux 4, the pfilter package causes image deployment to freeze midway through, so it is necessary to uncheck the pfilter package during Step 1