Knoppix

Clúster Knoppix
Master al disc dur
1. 2. 3. 4. 5. 6. 7. 8. 9. Arrancar LiveCD Term su knoppix-installer Crear partició de swap d’1 Gb i l’altre de ext3 Reiniciar Term su knoppix-terminalopenmosixserver a. Configuració DHCP b. No triar cap targeta

Client
1. 2. 3. 4. Arrancar CD Obrir un terminal netcardconfig Comprovar (ping)

Proves
Programa de test:
6

Annexhttp://www.ibm.com/developerworks/linux/library/l-clustknop/index.html

Building the cluster
For this I used two boxes. The master node was a Pentium™ III 1.7-GHz box with 384 MB RAM that it shares with the on-board graphics. The drone is a Pentium III 997-MHz machine with 256 MB dedicated RAM. Both have CD-ROM drives. They are connected through a standard crossed networking wire with RealTek 10/100 Mbps LAN cards onboth ends. If you have a home network setup with two (or more) computers with wires connecting them, then your setup is similar to mine. You will also need ClusterKnoppix (the latest version as of this writing is clusterKNOPPIX V3.4-2004-05-10-EN-cl). ClusterKnoppix has the ability to sniff out drones as they boot on the network, but you need special LAN cards and a BIOS that supports bootingover the network. Because the cost of replicating CDs is minimal and you want X running on all the nodes, it's easiest to use as many ClusterKnoppix CDs as there are nodes in the cluster. You can use the following network settings for the various nodes on the cluster:

IP address of Drone #1 -- 192.168.1.20 I won't go into detail on networking in Linux. There's a lot of information available; seeResources below. Back to top

● ● ● ● ●

Network -- 192.168.1.0 Netmask -- 255.255.255.0 Default Gateway -- 192.168.1.1 IP address of Master -- 192.168.1.10

Initializing the master node
openMosix doesn't require the first node initiated to be a master node, but just to keep things straight, set up the master node first. At the boot: prompt, press Enter. Give ClusterKnoppix time to detectyour hardware and boot. By default it boots into KDE.

1. 2. 1. 2.

Put the ClusterKnoppix CD in the drive and boot from it.

Once in, open a root shell. You'll find it inside the second item on the task bar. Now we need to configure the local network interface. First, give your network card, eth0, an IP address: ifconfig eth0 192.168.1.10.

3. Next, specify the route it must follow to thegateway: route add -net 0.0.0.0 gw 192.168.1.1. That sets up your network.
Last, announce this node as the master node in the cluster: tyd. Next, you'll initialize the drone node. Back to top

1. 2.

Next, initiate the openMosix system: tyd -f init.

Initializing the drone node
Setting up a drone is not very different from setting up a master. Repeat the first three steps above forinitializing the master node. Try configuring the network card on the drone yourself with the values mentioned previously (ifconfig eth0 192.168.1.20and ifconfig eth0 192.168.1.20). Last, insert this node into the cluster: tyd -m 192.168.1.10. That's it! Your cluster's up and running. Back to top

1. 2.

Now, initialize the openMosix system. Same as last time: tyd -f init.

Getting familiar withtracking tools
You'll need to check the status of the cluster; ClusterKnoppix packs the following tools for tracking status:

openMosixview
Bring up the utility by typing its name on the root shell. It will detect the number of nodes in the cluster and present you with a nice, geeky-looking interface. At a glance, you can see the efficiency of the cluster, the load on the cluster, the memoryavailable to the cluster, the percentage of memory used, and other information. You won't see much activity at this point, since the cluster is hardly being used. Spend some time familiarizing yourself with this application.

openMosixmigmon

This application shows the processes that have been migrated from the master node to the drone. Move your mouse over the square surrounding the circle in...