||This article needs attention from an expert on the subject. (June 2011)|
|This article needs additional citations for verification. (June 2011) (Learn how and when to remove this template message)|
A Beowulf cluster is a computer cluster of what are normally identical, commodity-grade computers networked into a small local area network with libraries and programs installed which allow processing to be shared among them. The result is a high-performance parallel computing cluster from inexpensive personal computer hardware.
No particular piece of software defines a cluster as a Beowulf. Beowulf clusters normally run a Unix-like operating system, such as BSD, Linux, or Solaris, normally built from free and open source software. Commonly used parallel processing libraries include Message Passing Interface (MPI) and Parallel Virtual Machine (PVM). Both of these permit the programmer to divide a task among a group of networked computers, and collect the results of processing. Examples of MPI software include OpenMPI or MPICH. There are additional MPI implementations available.
A description of the Beowulf cluster, from the original "how-to", which was published by Jacek Radajewski and Douglas Eadline under the Linux Documentation Project in 1998.
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 via Ethernet or some other network. It is a system built using commodity hardware components, like any PC capable of running a Unix-like operating system, with standard Ethernet adapters, and switches. It does not contain any custom hardware components and is trivially reproducible. Beowulf also uses commodity software like the FreeBSD, Linux or Solaris operating system, Parallel Virtual Machine (PVM) and Message Passing Interface (MPI). The server node controls the whole cluster and serves files to the client nodes. It is also the cluster's console and gateway to the outside world. Large Beowulf machines might have more than one server node, and possibly other nodes dedicated to particular tasks, for example consoles or monitoring stations. In most cases client nodes in a Beowulf system are dumb, the dumber the better. Nodes are configured and controlled by the server node, and do only what they are told to do. In a disk-less client configuration, a client node doesn't even know its IP address or name until the server tells it.
One of the main differences between Beowulf and a Cluster of Workstations (COW) is that Beowulf behaves more like a single machine rather than many workstations. In most cases client nodes do not have keyboards or monitors, and are accessed only via remote login or possibly serial terminal. Beowulf nodes can be thought of as a CPU + memory package which can be plugged into the cluster, just like a CPU or memory module can be plugged into a motherboard.
Beowulf is not a special software package, new network topology, or the latest kernel hack. Beowulf is a technology of clustering computers to form a parallel, virtual supercomputer. Although there are many software packages such as kernel modifications, PVM and MPI libraries, and configuration tools which make the Beowulf architecture faster, easier to configure, and much more usable, one can build a Beowulf class machine using a standard Linux distribution without any additional software. If you have two networked computers which share at least the
/homefile system via NFS, and trust each other to execute remote shells (rsh), then it could be argued that you have a simple, two node Beowulf machine.
- MOSIX, geared toward computationally intensive, IO-low, applications
- ClusterKnoppix, based on Knoppix
- Rocks Cluster Distribution
- DragonFly BSD
- Quantian, a live DVD with scientific applications, based on Knoppix and ClusterKnoppix
- ABC GNU/Linux based on Ubuntu
- Kentucky Linux Athlon Testbed
- PelicanHPC, based on Debian Live
A cluster can be set up by using Knoppix bootable CDs in combination with OpenMosix. The computers will automatically link together, without need for complex configurations, to form a Beowulf cluster using all CPUs and RAM in the cluster. A Beowulf cluster is scalable to a nearly unlimited number of computers, limited only by the overhead of the network.
Provisioning of operating systems and other software for a Beowulf Cluster can be automated using software, Open Source Cluster Application Resources (OSCAR) for example. OSCAR installs on top of a standard installation of a supported Linux distribution on a cluster's head node. Also look at commercial software such at Bright Cluster Manager from Bright Computing.
- Aiyara cluster
- Alewife (multiprocessor)
- Apache Hadoop
- Condor High-Throughput Computing System
- Fastra II
- Grid computing
- Kentucky Linux Athlon Testbed
- Maui Cluster Scheduler
- Open Source Cluster Application Resources (OSCAR)
- Platform LSF
- Portable Batch System
- Simple Linux Utility for Resource Management
- Stone Soupercomputer
- Sun Grid Engine
- TORQUE Resource Manager
- Becker, Donald J and Sterling, Thomas and Savarese, Daniel and Dorband, John E and Ranawak, Udaya A and Packer, Charles V, "BEOWULF: A parallel workstation for scientific computation", in Proceedings, International Conference on Parallel Processing vol. 95, (1995). URL http://www.phy.duke.edu/~rgb/brahma/Resources/beowulf/papers/ICPP95/icpp95.html
- See Francis Barton Gummere's 1909 translation, reprinted (for example) in Beowulf. Francis B. Gummere (translator). Hayes Barton Press (published n.d.). 1909. p. 20. ISBN 9781593773700. Retrieved 2014-01-16. Check date values in:
- Beowulf Cluster Computing With Windows by Thomas Lawrence Sterling 2001 ISBN 0262692759 MIT Press
- Beowulf Cluster Computing With Linux by Thomas Lawrence Sterling 2001 ISBN 0262692740 MIT Press