Cluster Knoppix 3.6
No MPI
No gfortran
using apt-get gfortran doesn't seem to work either (kernel is 2.4)
No octave
Where to get the ISO: http://clusterknoppix.sw.be/
http://www.knoppix.net/wiki/Cheat_Codes
burn to a CD-R
reboot the windows computer
ctrl-alt-del (to bring up the windows prompt)
alt-s (to select "shutdown")
r (to reboot)
With external DHCP source and 1 CD:
boot to CD
at the boot: prompt, enter "knoppix 2" without quotes. this will put you in text mode
if you have sufficient RAM, use "knoppix toram"
wait until boot process is completed
To eject the CD, enter
umount -l /cdrom
eject /dev/cdrom
This will umount and eject the CD. You've setup your first node.
grab the CD out of the tray
repeat the above process for N-1 boxes
on the Nth box you will set up the head node
boot to CD without "knoppix 2" (you want the GUI probably)
once KDE has loaded, open terminal and determine your IP
ifconfig
reset the blank "knoppix" user password
passwd
now you can SSH into that IP
to set up a remote windows share as a linked folder, first ensure the port is open
sudo nmap -sT <IP> -p 139
If the port is open you'll be able to access shares on that windows box.
mkdir winshare
sudo mount -t smbfs -o username=<domain>\\<username>,password=<password> //<IP>/<sharename> /home/knoppix/winshare
If your password has special characters (like 12!45) then you'll need to pass it the string 12\!45
to mount remote linux directories from the Clusterknoppix master node, use
sudo shfsmount <username>@<IP>:/home/<user>/mounter /home/knoppix/rtest/
To mount usb drives, use
mkdir ~/usb
mount -t msdos /dev/sda1 ~/usb
terminal server PXE boot
(assuming no external DHCP)
boot the terminal server
knoppix
once started, run
knoppix-terminalopenmosixserver
This will start a DHCP/PXE server, so don't be connected to the regular network
If using virtual box, select "internal network" (which is basically all the boxes connected to a switch)
Since no IP is assigned via DHCP, the terminal server won't contribute to the openMosix machine count
-how to add openMosix node manually? (it doesn't get picked up by the other nodes, but it has an IP?)
Need to know the network card identifier. This may be acceptable in a homogeneous environment, but is not easy. In setting up the terminal server, checking all network card drivers takes space on the ramdisk.
$ lspci
enable necessary network card drivers
TURN OFF IP masquerading/forwarding
by default, I thought it copied the entire CD image, which means the nodes need to have sufficient RAM (1Gb). However, this is not the case; 500MB works fine on nodes.
integrates with CHAOS nodes? "boot clients with chaos initrd/kernel"
-would be good so that I don't need to have a huge image running in RAM
PXE boot the master node. If the terminal server is at run level 1, then the cluster master needs to be told to run level 5 in order to get a GUI
PXE boot the rest of the nodes (automatically run level 1).
to stop, use
/usr/sbin/knoppix-terminalopenmosixserver stop
http://www.firewall.cx/linux-openmosix-building-a-cluster.php
you get a single computer with as many CPU "cores" as you have single processor nodes. There is no MPI capabilities. Multi-core systems are useful for multiple single processor jobs, set up using a shell script. Alternatively, cisilia. Fortran compiler is not included by default, you'll need to download and install the compiler.
I have set this up previously on 31 nodes, but has only been able to run locally compiled files. (no fortran.)