openMosix Files

1. CONTENT OF THE PACKAGE

The openmosix-tools includes all the userspace-tools necessary to
utilise the power of openMosix. Since version 0.2.4 this also includes
the auto-discovery daemon omdiscd, which makes the map-file
/etc/openmosix.map obsolete. Since version 0.3 the package also
includes the mps-package, which has openMosix-aware versions of ps and
top (mps and mtop), showing which node each process is running on.

The package also includes a SysV init-script that can be used to start
and stop openMosix.



2. INSTALLATION OF PRECOMPILED RPM

When installing the openmosix-tools.rpm, the .rpm will automatically
make some changes to the system's configuration-files,
(e.g. /etc/inittab) that is necessary for openMosix to operate
properly. See the %post and %preun sections of openmosix-tools.spec
for details. The changes are undone if you decide to uninstall the
.rpm.

The automatic changes performed will prevent migration of any process
started from the system rc scripts and it's child processes, unless
specifically allowed to. The SSH daemon startup script is modified to
allow tasks started from an SSH session to migrate.

The only manual configuration needed is to edit /etc/openmosix.map to
add the machines in your cluster. Documentation and an example is
included in a skeleton /etc/openmosix.map. If you leave the map-file
without a valid configuration, the openMosix auto-discovery daemon
will be started instead. All nodes running this daemon will be
automatically configured and joined together in a common cluster.

The .rpms have been reported to work with both RedHat 7-8.x, SuSE and
Mandrake.



3. MANUAL COMPILATION

Edit the top-level file "configuration". You should only need to
change a few things, specifically:

OPENMOSIX: The full path to an openMosix kernel tree.
MONNAME: The "mon" userland tool use the same name as a commonly used
	 monitoring tool. This variable allows you to change the name
	 of the userland tool. The default (mosmon) is highly
	 recommended.

To compile everything, run "make all".

To install in the default location, run "make install". If you would
like to install somewhere else (e.g. for creating RPMs), run "make
install DESTDIR=/somewhere/else".

To create a tar-file for distribution, edit VERSION in the top-level
Makefile and run "make dist". The tarfile is placed one
directory-level above the userspace-tools tree.

To create an RPM, edit Version and Release in the top-level
openmosix-tools.spec and run "make rpm".

During the installation, a SysV-initialisation script
(scripts/openmosix) is copied to /etc/init.d. Run "chkconfig --add
openmosix" (or the equivalent for you distribution) to activate it.



4. MANUAL INSTALLATION

If you prefer to install the openMosix-tools without using the RPM,
you'll have to do some editing by yourself. Note: Even if you install
the tools with an RPM, you can still roll your own kernel, so even for
the developer there's no need to install the tools by hand. After
running "make install", you should perform the following steps:

- /etc/inittab:
  The lines that starts /etc/rc.d/rc*, /sbin/update and /sbin/shutdown
  should be changed so they're instead started with /bin/mosrun -h.
  Example:
    si::sysinit:/etc/rc.d/rc.sysinit
  should be changed to
    si::sysinit:/bin/mosrun -h /etc/rc.d/rc.sysinit

- /etc/rc.d/init.d/sshd
  Since now all daemons are locked from migration, all their children
  will be too. This makes all processes started from a ssh-login also
  being locked from migration. Solution: In the beginning of the
  start() function, put this line:
  test -f /proc/$$/lock && echo 0 > /proc/$$/lock

- /etc/cron.daily/slocate.cron
  You don't want slocate to look in the MFS-filesystem (if you choose
  to try that). Put mfs in there with nfs and the others.

- /etc/openmosix.map
  This file must be the same on all nodes, and tells openMosix which
  machines are part of the cluster. Each line should contain 3 fields,
  mapping IP addresses to openMosix node-numbers: 
  1) First openMosix node-number in range.
  2) IP address of the above node (or node-name from /etc/hosts).
  3) Number of nodes in this range.
  Example: 10 machines with IP 192.168.1.50 - 192.168.1.59
  1        192.168.1.50     10

- If you decide to use the auto-discovery daemon, the
  /etc/openmosix.map file is not needed. You can either remove it, or
  just comment out the configuration-lines. You can also force the use
  of the auto-discovery daemon by setting AUTODISC=1 in
  etc/openmosix/openmosix.config



Martin Høy (martin.hoy@pvv.ntnu.no)