INSTRUCTIONS FOR INITIATING CLUSTER v.2.0 ************************************************************************************************************************************************ *Note that 192.168.0.xx refers to the ip of a particular drone node and that the same number should be used in every step for a specific node. * *The number changes based on the drone node number, so the series goes 192.168.0.2, 192.168.0.3, 192.168.0.4, etc. * *You also need to make sure that you know the ip of the router. In the case of my silver belkin router, it is 192.168.0.1 . You can find this * *by trying to ping it. it is either 192.168.0.1 or 192.168.1.1 . * ************************************************************************************************************************************************ Editing files: There are 2 ways to edit system files in linux. If you are in the GUI, you can simply navigate to the desired folder and open the file with something like kwrite. If you are on a command line, then use the command "vi filename". this will open the file in the command line and let you edit it. To begin, hit the insert key and use the arrow keys to get to where you need to insert text. type it in and then press the escape key. Then, hold down shift and press "zz". This will exit and save your work. Note that "/" is the lowest directory so "/etc/hosts" is located in "/"->"/etc"->"/hosts". Notes: Anytime you see that means to type exactly what is in the < > and hit enter HEAD NODE ---------- **************************************************************************************************** *Before you initiate the networking, do this: * * * * * * * *then add this line somewhere, no quotes: *"cluster /mfs mfs odfsa=1 0 0" * *then continue to step 1 * * * **************************************************************************************************** 1. 2. 3. DRONE NODES ------------ 1. 2. 3. CORRECT /etc/openmosix.map FILE CONFIG --------------------------------- This should be the exact same on every node 1 192.168.0.2 1 2 192.168.0.3 1 3 192.168.0.x 1 and continue adding aditional ip's that corespond to step 1 of drone node config CORRECT /etc/hosts FILE CONFIG ------------------------------- this should be modified on every node also 192.168.0.x node2 localhost 127.0.0.1 localhost Note here that node2 should be replaced with that node's name, which should correspond to the list below: machine number node number machine name assigned ip 1 1 node1 192.168.0.2 2 2 node2 192.168.0.3 3 3 node3 192.168.0.4 To test if it worked, type and hit t. this will give you a graph of cluster activity and the number of availible cpu's.