Supercomputer - Revision history

J: /* Script Installation */

2009-12-05T16:27:06Z

‎Script Installation

J: /* Initialize Cluster */

2009-11-23T05:01:39Z

‎Initialize Cluster

J: /* Implementation Plan */

2009-11-23T04:47:21Z

‎Implementation Plan

J: /* Configure Kerrighed */

2009-11-23T04:10:49Z

‎Configure Kerrighed

J: /* Network Gateway */

2009-11-19T22:43:48Z

‎Network Gateway

J: /* Operating System for Cluster Nodes */

2009-11-19T22:38:08Z

‎Operating System for Cluster Nodes

J: /* Implementation Plan */

2009-11-19T22:29:48Z

‎Implementation Plan

J: /* Installation and Configuration */

2009-11-19T22:27:20Z

‎Installation and Configuration

J: /* Power Up */

2009-11-19T22:24:32Z

‎Power Up

J: /* Setup Overview and Network Configuration */

2009-11-19T22:09:41Z

‎Setup Overview and Network Configuration

@@ Line 412: / Line 412: @@
 <pre>chmod +x /etc/network/if-up.d/gateway</pre>
-Next time the network comes up, this script will run.  You can also run it manually.
+Next time the network comes up, this script will run.  You can run it manually to apply the changes immediately.
 ==Journal==

@@ Line 336: / Line 336: @@
 krgcapset -k $$ -d +CAN_MIGRATE
 krgcapset -d +USE_REMOTE_MEMORY
 </pre>

@@ Line 104: / Line 104: @@
 ==Implementation Plan==
-;Stage 1 - Proof of Concept (Started 14-Nov-2009)
+;Stage 1 - Proof of Concept (Started 14-Nov-2009, finished 22-Nov-2009)
 :This stage will use minimal hardware (1 storage node, 2 cluster nodes, 10/100 networking) to demonstrate that the solution can meet the requirements set forward.  An installation procedure and power up/down procedures will also be produced during this stage.
-;Stage 2 - Basic Implementation
+;Stage 2 - Basic Implementation (Started 22-Nov-2009)
 :This stage will use expanded hardware (maximum number of cluster nodes available - probably about 6, Gigabit networking) to demonstrate the full potential of the cluster.  This stage will start with the installation used in the Proof of Concept stage.  The setup created here will be expanded into the final implementation.  Procedures for managing processes throughout the cluster will be investigated and developed.  A benchmark procedure will be investigated, developed, and demonstrated.

@@ Line 301: / Line 301: @@
 #Make the Kerrighed kernel avaliable via TFTP
 #*<pre>cp /nfsroot/kerrighed/boot/vmlinuz-2.6.20-krg /var/lib/tftpboot/</pre>
 #Make sure the following line appears in '''/nfsroot/kerrighed/etc/default/kerrighed'''
 #*<pre>ENABLE=true</pre>

@@ Line 368: / Line 368: @@
 ===Script Installation===
 ====Network Gateway====
 Save this on the storage node in '''/etc/network/if-up.d/gateway''' (I didn't write this script<ref>http://www.debian-administration.org/articles/23</ref>, I just swapped the interfaces)
 <pre>
@@ Line 406: / Line 408: @@
 And allow execution, like so:
 <pre>chmod +x /etc/network/if-up.d/gateway</pre>
 ==Journal==

@@ Line 240: / Line 240: @@
 #Set the root password
 #*<pre>passwd</pre>
-#Get a ''/proc'' directory
+#Get a '''/proc''' directory
 #*<pre>mount -t proc none /proc</pre>
 #Avoid lots of annoying warnings
@@ Line 252: / Line 252: @@
 #Add a user so we can log in to the cluster nodes
 #*<pre>adduser</pre>
-#Configure the network by making ''/etc/network/interfaces'' look like this:
+#Configure the network by making '''/etc/network/interfaces''' look like this:
 <pre>
 auto lo

@@ Line 108: / Line 108: @@
 ;Stage 2 - Basic Implementation
-:This stage will use expanded hardware (maximum number of cluster nodes available - probably about 6, Gigabit networking) to demonstrate the full potential of the cluster.  This stage will start with a fresh install, using the procedure created in the Proof-of-concept.  The setup created here will be expanded into the final implementation.  Procedures for managing processes throughout the cluster will be investigated and developed.  A benchmark procedure will be investigated, developed, and demonstrated.  Virtual machine host installation and usage procedures will be investigated, developed, and demonstrated.
+:This stage will use expanded hardware (maximum number of cluster nodes available - probably about 6, Gigabit networking) to demonstrate the full potential of the cluster.  This stage will start with the installation used in the Proof of Concept stage.  The setup created here will be expanded into the final implementation.  Procedures for managing processes throughout the cluster will be investigated and developed.  A benchmark procedure will be investigated, developed, and demonstrated.
 ;Stage 3 - Expanded Implementation
-:This stage will build on the implementation from Stage 2 - no new computing hardware will be added.  The graphical environment will be installed and tested.  Multi-monitor support will be added.  Scripts will be created to automatically power up all nodes, to initialize the cluster, to shutdown all nodes, and for other tasks.
+:This stage will build on the implementation from the Basic Implementation stage - no new computing hardware will be added.  Virtual machine host installation and usage procedures will be investigated, developed, and demonstrated.  The graphical environment will be installed and tested.  Multi-monitor support will be added.  Scripts will be created to automatically power up all nodes, to initialize the cluster, to shutdown all nodes, and for other tasks.
 ;Stage 4 - Performance Evaluation

@@ Line 135: / Line 135: @@
 ===Installation and Configuration===
 There is quite a bit of assumed knowledge here.  Read all the directions before you start, and make sure you understand what is going on.
 ====Operating System for the Storage Node====

@@ Line 312: / Line 312: @@
 #If you just finished the installation procedure, either reboot, or set up the network and start all the servers - like this:
 #*<pre>ifconfig eth1 192.168.81.1</pre>
 #*<pre>/etc/init.d/tftpd-hpa start</pre>
 #*<pre>/etc/init.d/dhcp3-server start</pre>

@@ Line 122: / Line 122: @@
 ;Storage node
-:The storage node will not run a Kerrighed kernel.  Its responsibilities are only to provide the nodes with network addresses, the PXE boot image, and the shared file system.  This system will have 2 network cards - one connected to the ''external'' network, the other to the ''cluster'' network.  DHCP and PXE services will only be provided to the ''cluster'' network.  For my setup, the storage node will be named "frank".  Its IP address on the external network will be assigned by DHCP somewhere in the 192.168.80.0/24 subnet.  Its IP address on the cluster network will be 192.168.81.1.
+:The storage node will not run a Kerrighed kernel.  Its responsibilities are only to provide the nodes with network addresses, the PXE boot image, and the shared file system.  This system will have 2 network cards - one connected to the ''external'' network, the other to the ''cluster'' network.  DHCP and PXE services will only be provided to the ''cluster'' network.  For my setup, the storage node will be named "frank".  Its IP address on the external network will be assigned by DHCP somewhere in the 192.168.80.0/24 subnet.  The external network will be connected to the ''eth0'' network adapter.  The storage node's IP address on the cluster network will be 192.168.81.1.  The cluster network will be connected to the ''eth1'' network adapter.
 ;Cluster node