175 lines
3.3 KiB
HTML
175 lines
3.3 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
|
<HTML
|
|
><HEAD
|
|
><TITLE
|
|
>Definitions</TITLE
|
|
><META
|
|
NAME="GENERATOR"
|
|
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
|
REL="HOME"
|
|
TITLE="The Beowulf HOWTO"
|
|
HREF="index.html"><LINK
|
|
REL="PREVIOUS"
|
|
TITLE="Introduction"
|
|
HREF="intro.html"><LINK
|
|
REL="NEXT"
|
|
TITLE="Requirements"
|
|
HREF="x58.html"></HEAD
|
|
><BODY
|
|
CLASS="sect1"
|
|
BGCOLOR="#FFFFFF"
|
|
TEXT="#000000"
|
|
LINK="#0000FF"
|
|
VLINK="#840084"
|
|
ALINK="#0000FF"
|
|
><DIV
|
|
CLASS="NAVHEADER"
|
|
><TABLE
|
|
SUMMARY="Header navigation table"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TH
|
|
COLSPAN="3"
|
|
ALIGN="center"
|
|
>The Beowulf HOWTO</TH
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="left"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="intro.html"
|
|
ACCESSKEY="P"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="80%"
|
|
ALIGN="center"
|
|
VALIGN="bottom"
|
|
></TD
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="right"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="x58.html"
|
|
ACCESSKEY="N"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"></DIV
|
|
><DIV
|
|
CLASS="sect1"
|
|
><H1
|
|
CLASS="sect1"
|
|
><A
|
|
NAME="AEN49"
|
|
></A
|
|
>2. Definitions</H1
|
|
><P
|
|
>What is a Beowulf cluster? The authors of the
|
|
<A
|
|
HREF="http://ibiblio.org/pub/Linux/docs/HOWTO/archive/Beowulf-HOWTO.html"
|
|
TARGET="_top"
|
|
>original
|
|
Beowulf HOWTO</A
|
|
>, Jacek Radajewski and Douglas Eadline,
|
|
provide a good definition in their document: "Beowulf is a
|
|
multi-computer architecture which can be used for parallel computations.
|
|
It is a system which usually consists of one server node, and one or more
|
|
client nodes connected together via Ethernet or some other network". The
|
|
site <A
|
|
HREF="http://beowulf.org"
|
|
TARGET="_top"
|
|
>beowulf.org</A
|
|
> lists many web
|
|
pages about Beowulf systems built by individuals and organizations. From
|
|
these two links, one can be exposed to a large number of perspectives on
|
|
the Beowulf architecture, and draw his / her own conclusions.</P
|
|
><P
|
|
>What's the difference between a true Beowulf cluster and a COW
|
|
[cluster of workstations]? Brahma gives a good definition:<A
|
|
HREF="http://www.phy.duke.edu/brahma/beowulf_book/node62.html"
|
|
TARGET="_top"
|
|
> http://www.phy.duke.edu/brahma/beowulf_book/node62.html</A
|
|
>.</P
|
|
><P
|
|
>If you are a "user" at your organization, and you have the use
|
|
of some nodes, you may still do the instructions shown here to create a cow.
|
|
But if you "own" the nodes, that is, if you have complete control of them,
|
|
and are able to completely erase and rebuild them, you may create a true
|
|
Beowulf cluster.</P
|
|
><P
|
|
>In Brahma's web page, he suggests you manually configure each box,
|
|
and then later on (after you get the feel of doing this whole "wolfing up"
|
|
procedure), you can set up new nodes automatically (which I will describe
|
|
in a later document).</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="NAVFOOTER"
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"><TABLE
|
|
SUMMARY="Footer navigation table"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="intro.html"
|
|
ACCESSKEY="P"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="index.html"
|
|
ACCESSKEY="H"
|
|
>Home</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="x58.html"
|
|
ACCESSKEY="N"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
>Introduction</TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
> </TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
>Requirements</TD
|
|
></TR
|
|
></TABLE
|
|
></DIV
|
|
></BODY
|
|
></HTML
|
|
> |