mirror of https://github.com/tLDP/LDP
337 lines
10 KiB
Plaintext
337 lines
10 KiB
Plaintext
<CHAPTER id="ClumpOS">
|
|
<TITLE>ClumpOS</TITLE>
|
|
|
|
<SECT1><TITLE>What is Clump/OS</TITLE>
|
|
<PARA>There is currently no openMosix version available of Clump/OS.
|
|
However according to the mailing list one is planned.
|
|
|
|
<programlisting>
|
|
From: Jean-David Marrow
|
|
Cc: clumpos-list
|
|
Subject: Re: [clumpos-list] clump/os and OpenMosix
|
|
Date: 29 Apr 2002 14:54:26 -0400
|
|
|
|
the OpenMosix-based release is on hold, for internal reasons, until
|
|
OpenMosix for 2.4.17 (or greater) kernel become available... and since i
|
|
don't have a release schedule for OpenMosix itself, I'm afraid that i
|
|
can't tell you exactly when that'll be... ;)
|
|
|
|
jdm
|
|
</programlisting>
|
|
|
|
|
|
|
|
</PARA> <PARA>
|
|
|
|
|
|
clump/os is a CD-based Linux /MOSIX mini-distribution designed to allow
|
|
users to quickly, or temporarily, add nodes to a MOSIX cluster; As I write
|
|
this in march 2002 the version (release 5.x) is a 5.3M ISO download.
|
|
</PARA><PARA>
|
|
This chapter has been contributed by Jean-David Marrow who is the main
|
|
author of Clump/OS.
|
|
|
|
</PARA>
|
|
</SECT1>
|
|
|
|
<SECT1><TITLE>How does it work </TITLE>
|
|
|
|
<para> At boot-time, clump/os will
|
|
auto-probe for network cards, and, if any are detected, try to configure
|
|
them via DHCP. If successful, it will create a mosix.map file based on the
|
|
assumption that all nodes are on local CLASS C networks, and configure
|
|
MOSIX using this information.
|
|
</para>
|
|
<para>
|
|
clump/os Release 4 best supports machines with a single connected network
|
|
adapter. The MOSIX map created in such cases will consist of a single
|
|
entry for the CLASS-C network detected, with the node number assigned
|
|
reflecting the IP address received from DHCP. (On the 192.168.1 network,
|
|
node #1 will be 192.168.1.1, etc.) If you use multiple network adapters
|
|
Expert mode is recommended as the assignment of node numbers is sensitive
|
|
to the order in which network adapters are detected. (Future releases will
|
|
support complex topologies and feature more intelligent MOSIX map
|
|
creation.)
|
|
</para>
|
|
<para>
|
|
|
|
clump/os will then display a simple SVGA
|
|
monitor (clumpview) indicating whether the node is configured, and, if it
|
|
is, showing the load on all active nodes on the network. When you've
|
|
finished using this node, simply press [ESC] to exit the interface and
|
|
shutdown. </para>
|
|
|
|
<PARA> Alternatively, or if auto-configuration doesn't work for you, then
|
|
you can use clump/os in Expert mode. Please note that clump/os is not a
|
|
complete distribution or a rescue disk; the functionality present is the
|
|
bare minimum required for a working MOSIX server node.
|
|
</PARA>
|
|
|
|
<PARA> It works for us, but may not work for you; if you experience
|
|
difficulties, please email us with as much information about your system
|
|
as possible -- after you have investigated the problem. (See Problems?
|
|
and Expert mode. You might also consider subscribing to the clump/os
|
|
mailing list.) </PARA>
|
|
|
|
</SECT1>
|
|
|
|
|
|
<SECT1><TITLE>Requirements
|
|
</TITLE>
|
|
<PARA>
|
|
|
|
|
|
As the purpose of clump/os is to add nodes to a cluster, it is assumed
|
|
that you already have a running MOSIX
|
|
cluster -- or perhaps only a single MOSIX node -- from which you will
|
|
be initiating jobs. All machines in the cluster
|
|
must conform to the following requirements:
|
|
|
|
</PARA>
|
|
<itemizedlist>
|
|
<listitem>
|
|
<para>
|
|
clump/os Machine(s) 586+ CPU,
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
|
|
bootable CD-ROM
|
|
</para>
|
|
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
NIC</para>
|
|
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
64M+ RAM (the system is loaded entirely into a ramdisk; this means that
|
|
you should have at least 64M of RAM (and likely more) to accommodate
|
|
the approx. 16M ramdisk, space needed for Linux itself, and space
|
|
for your work. This approach was chosen so that the same CD-ROM
|
|
can be used to configure multiple systems.)
|
|
</para>
|
|
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
|
|
Master Machine(s) Linux 2.4.17, MOSIX 1.5.7 (manually
|
|
configured)</para>
|
|
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
|
|
Network Environment Running DHCP server (f you don't, or won't, run DHCP,
|
|
you can still manually configure
|
|
your system; see Problems? and Expert Mode. Using DHCP is
|
|
highly recommended, however, and will greatly simplify your life in
|
|
the long run. )</para>
|
|
|
|
</listitem>
|
|
</itemizedlist>
|
|
<PARA>
|
|
|
|
|
|
|
|
|
|
The following network modules are present, although not all support
|
|
auto-probing; if you don't see support for your
|
|
card in this list, then clump/os will not work for you even in Expert
|
|
Mode.
|
|
</PARA>
|
|
<PARA>
|
|
<EMPHASIS>
|
|
|
|
|
|
|
|
3c501.o 3c503.o 3c505.o 3c507.o 3c509.o 3c515.o 3c59x.o 8139cp.o 8139too.o
|
|
82596.o 8390.o ac3200.o acenic.o at1700.o cs89x0.o de4x5.o depca.o dgrs.o
|
|
dl2k.o dmfe.o dummy.o e2100.o eepro.o eepro100.o eexpress.o epic100.o
|
|
eth16i.o ewrk3.o fealnx.o hamachi.o hp-plus.o hp.o hp100.o lance.o
|
|
lp486e.o natsemi.o ne.o ne2k-pci.o ni5010.o ni52.o ni65.o ns83820.o
|
|
pcnet32.o sis900.o sk98lin.o smc-ultra.o smc9194.o starfire.o sundance.o
|
|
sungem.o sunhme.o tlan.o tulip.o via-rhine.o wd.o winbond-840.o
|
|
yellowfin.o
|
|
</EMPHASIS>
|
|
</PARA>
|
|
|
|
|
|
|
|
<PARA>
|
|
Please also note that clump/os may not work on a laptop, definitely
|
|
doesn't support PCMCIA cards, and will
|
|
probably not configure MOSIX properly if your machine contains multiple
|
|
connected Ethernet adapters; see Note 1.
|
|
This is a temporary limitation of the configuration scripts, and the
|
|
Release 3/4 kernels which are compiled without
|
|
CONFIG_MOSIX_TOPOLOGY
|
|
</PARA>
|
|
</SECT1>
|
|
|
|
|
|
|
|
<SECT1><TITLE>Getting Started
|
|
</TITLE>
|
|
<PARA>
|
|
|
|
|
|
|
|
You can download the latest clump/os ISO under the terms of the
|
|
GPL, without warranty of any kind, from the clump os website.
|
|
Afterwards you have to burn the image to CD-ROM, insert the CD into
|
|
your drive, and reboot.
|
|
(More detailed instructions are in the works, but all the
|
|
information you need is somewhere on this page -- please read
|
|
the notes in the margin!)
|
|
</PARA>
|
|
</SECT1>
|
|
|
|
<SECT1><TITLE>Problems ?
|
|
</TITLE>
|
|
<PARA>
|
|
<ITEMIZEDLIST>
|
|
<LISTITEM><PARA><EMPHASIS>
|
|
The CD-ROM doesn't boot
|
|
</EMPHASIS>
|
|
</PARA>
|
|
<PARA>
|
|
|
|
Check your BIOS settings to make sure that your machine is configured
|
|
to boot from the CD-ROM drive; also make
|
|
sure that the CD-ROM is the first boot device.
|
|
</PARA>
|
|
</LISTITEM>
|
|
<LISTITEM>
|
|
<PARA><EMPHASIS>
|
|
The SVGA interface doesn't work, or the display is incorrect
|
|
</EMPHASIS></PARA>
|
|
<PARA>
|
|
Boot into Expert mode, and send us mail describing your video hardware
|
|
so that we can correct this in future
|
|
versions. (You won't be able to use clumpview for now.) If at all
|
|
possible, please send us a working libsvga
|
|
configuration file for the machine in question.
|
|
</PARA></LISTITEM>
|
|
<LISTITEM>
|
|
<PARA><EMPHASIS>
|
|
The network adapter isn't detected/autoconfigured (or no DHCP)
|
|
</EMPHASIS>
|
|
</PARA>
|
|
<PARA>
|
|
If you see a message (in clumpview) stating that no Ethernet devices
|
|
were configured, or that this node isn't
|
|
configured yet, then either your Ethernet card was not detected or the
|
|
system was not able to configure the card via
|
|
DHCP.
|
|
</PARA><PARA>
|
|
If you don't have a DHCP server configured and running on your local
|
|
network, clump/os will never autoconfigure;
|
|
if you have multiple connected network adapters, then clump/os may not
|
|
configure MOSIX properly. If
|
|
auto-probing for your network adapter doesn't work, or if you aren't
|
|
using DHCP, then you'll have to configure your
|
|
card manually in Expert mode -- using insmod, ifconfig, and route --
|
|
and then configure MOSIX via setpe.
|
|
</PARA><PARA>
|
|
|
|
If you do need to manually configure your network adapter, please
|
|
advise us. We'd like to solve this problem, if
|
|
possible, or at least document which network cards auto-probe correctly.
|
|
</PARA>
|
|
</LISTITEM>
|
|
<LISTITEM><PARA><EMPHASIS>
|
|
Migrating processes generate errors ("Network Unreachable")
|
|
</EMPHASIS>
|
|
</PARA>
|
|
<PARA>
|
|
|
|
This rare problem can be caused by conflicts resulting from differently
|
|
configured kernels -- even if you are using the
|
|
correct MOSIX and Linux kernel versions. If clump/os correctly detects
|
|
all your nodes, but migrating processes
|
|
generate errors, then please compare your master node's kernel
|
|
configuration file with the R4.x kernel .config.
|
|
</PARA></LISTITEM>
|
|
<LISTITEM><PARA><EMPHASIS>
|
|
|
|
Migrating processes generate errors ("Process migration failed:
|
|
incompatible topology")
|
|
</EMPHASIS>
|
|
</PARA>
|
|
<PARA>
|
|
|
|
You are likely using master nodes with CONFIG_MOSIX_TOPOLOGY defined,
|
|
which is not supported by clump/os
|
|
at this time. See Requirements, and compare your kernel configuration
|
|
as per the previous FAQ; you will need to
|
|
recompile your master node kernel(s).
|
|
</PARA>
|
|
</LISTITEM>
|
|
</ITEMIZEDLIST>
|
|
</PARA>
|
|
<PARA>
|
|
If you don't find your issue here, please consider posting to the
|
|
clump/os mailing list. (Please note that only subscribers are
|
|
permitted to post; click on the link for instructions.) You should also
|
|
make certain that you are using the latest versions of MOSIX and
|
|
clump/os, and that the versions -- clump/os R4.x and
|
|
MOSIX 1.5.2 at the time of this writing -- are in sync.
|
|
</PARA>
|
|
</SECT1>
|
|
|
|
|
|
<SECT1><TITLE>Expert Mode
|
|
</TITLE>
|
|
|
|
<PARA> If you hold down shift during the boot process, you have the option
|
|
of booting into Expert mode; this will cause clump/os to boot to a shell
|
|
rather than to the graphical interface. From this shell you can attempt
|
|
to insert the appropriate module for your network adapter (if autoprobing
|
|
failed), and/or configure your network and MOSIX manually. Type "halt" to
|
|
shut down the system. (Note that since the system resides in RAM you can't
|
|
hurt yourself too badly by rebooting the hard way if you have to -- unless
|
|
you have manually mounted any partitions rw, that is, and we don't
|
|
recommend doing so at this point.) </PARA>
|
|
|
|
|
|
<PARA>
|
|
If you want to run clumpview, execute:
|
|
<PROGRAMLISTING>
|
|
open -s -w -- clumpview --drone --svgalib
|
|
</PROGRAMLISTING>
|
|
|
|
|
|
This will force the node into 'drone' mode (local processes will not
|
|
migrate), and will force clumpview to use SVGALIB;
|
|
the open command will ensure that a separate vt is used.
|
|
</PARA><PARA>
|
|
Please be advised that the environment provided was initially
|
|
intentionally minimalistic; if you require additional files, or wish to
|
|
copy files from the system to another machine, your only option is
|
|
nc (netcat -- a great little utility, btw), or mfs if MOSIX is
|
|
configured. From version R5.4 on size is no longer a primary
|
|
consideration.
|
|
|
|
</PARA><PARA> Expert mode (and clump/os for that matter) is 'single-user';
|
|
this is one of the reasons that utilities such as ssh are not included.
|
|
These and other similar decisions were made in order to keep clump/os
|
|
relatively small, and do not affect cluster operation. </PARA> <PARA>
|
|
|
|
|
|
From version R5.4, if you experience problems in Expert Mode, you
|
|
can boot into Safe Mode; in Safe Mode no
|
|
attempt is made at autoconfiguration.
|
|
</PARA>
|
|
</SECT1>
|
|
|
|
|
|
|
|
|
|
</CHAPTER>
|
|
|