Difference between revisions of "Little-Fe PPC"

From Earlham CS Department
Jump to navigation Jump to search
(Server Configuration)
 
(4 intermediate revisions by one other user not shown)
Line 1: Line 1:
 
This is page contains information about the 4 node PPC (Pegasos) version of Little-Fe.
 
This is page contains information about the 4 node PPC (Pegasos) version of Little-Fe.
  
This version of Little-Fe PPC is based on a [http://www.debian.org Debian GNU/Linux] installation.  It employs [http://www.am-utils.org/project-unionfs.html UnionFS] to facilitate consolidation of system and cluster software on a single hard drive (attached to <code>lf0</code>).  All other nodes netboot from the master image by masking the server-specific files with a lightweight overlay.
+
This version of Little-Fe PPC is based on a [http://www.debian.org Debian GNU/Linux] installation.  It employs [http://www.am-utils.org/project-unionfs.html UnionFS] to facilitate consolidation of system and cluster software on a single hard drive (attached to <code>lf0</code>).  All other nodes netboot from the main image by masking the server-specific files with a lightweight overlay.
  
 
* <code>lf0</code> can be found at <code>lf-ppc.cluster.earlham.edu</code>
 
* <code>lf0</code> can be found at <code>lf-ppc.cluster.earlham.edu</code>
Line 7: Line 7:
 
==Documentation and bug reporting==
 
==Documentation and bug reporting==
  
* To report a bug, please use [https://www.cs.earlham.edu/bugzilla/enter_bug.cgi?product=lf-ppc Bugzilla]
+
* To report a bug, please use [http://cluster.earlham.edu/bugzilla/enter_bug.cgi?product=lf-ppc Bugzilla]
  
 
We are documenting the production of Little-Fe in two ways:  First, bugs are filed in bugzilla (and hopefully fixed).  Second, we're putting flesh on a set of instructions to build a replica of the original Little-Fe PPC.  The latter is probably (but not necessarily) based on the former.  The distinction is mainly that Bugzilla will show how things were done wrong, while the wiki-based instructions will show how to do things right the first time.
 
We are documenting the production of Little-Fe in two ways:  First, bugs are filed in bugzilla (and hopefully fixed).  Second, we're putting flesh on a set of instructions to build a replica of the original Little-Fe PPC.  The latter is probably (but not necessarily) based on the former.  The distinction is mainly that Bugzilla will show how things were done wrong, while the wiki-based instructions will show how to do things right the first time.
Line 24: Line 24:
 
setenv boot-file vmlinuz-2.6.15.6 init=/linuxrc root=/dev/nfs ip=dhcp console=ttyS1,115200n1
 
setenv boot-file vmlinuz-2.6.15.6 init=/linuxrc root=/dev/nfs ip=dhcp console=ttyS1,115200n1
 
</pre>
 
</pre>
After this is setup, type <code>setenv auto-boot? true</code> at the main firmware prompt (not in <code>nvedit</code>).
+
After this is setup, type <code>setenv auto-boot? true</code> at the main firmware prompt (not in <code>nvedit</code>).  Reboot to read in the new environment variables or set them manually and then type <code>boot</code>.
  
 
==Creating a new Little-Fe PPC==
 
==Creating a new Little-Fe PPC==
Line 31: Line 31:
  
 
==Related pages==
 
==Related pages==
*[[Pegasos|Pegasos PPC (ODW) notes]]
+
* [[Pegasos|Pegasos (ODW) notes]] - firmware info, including disk and net booting; serial console info; etc.

Latest revision as of 09:50, 24 March 2021

This is page contains information about the 4 node PPC (Pegasos) version of Little-Fe.

This version of Little-Fe PPC is based on a Debian GNU/Linux installation. It employs UnionFS to facilitate consolidation of system and cluster software on a single hard drive (attached to lf0). All other nodes netboot from the main image by masking the server-specific files with a lightweight overlay.

  • lf0 can be found at lf-ppc.cluster.earlham.edu

Documentation and bug reporting

We are documenting the production of Little-Fe in two ways: First, bugs are filed in bugzilla (and hopefully fixed). Second, we're putting flesh on a set of instructions to build a replica of the original Little-Fe PPC. The latter is probably (but not necessarily) based on the former. The distinction is mainly that Bugzilla will show how things were done wrong, while the wiki-based instructions will show how to do things right the first time.

Adding/Setting up a new node in the Debian Unified Root

These are current as of May 19, 2006.

Server Configuration

  • add MAC addresses for the 100Mbit and Gbit network interfaces to /etc/dhcp3/dhcpd.conf
  • restart dhcp with /etc/init.d/dhcp3-server restart

Client Firmware

These are the current client firmware settings necessary to boot lf[1-n] via the Debian unified root setup. These must be set on every single client node in order to netboot successfully. If they are not there already, add or correct the following lines in nvedit:

setenv boot-device eth:dhcp,0.0.0.0,,0.0.0.0
setenv boot-file vmlinuz-2.6.15.6 init=/linuxrc root=/dev/nfs ip=dhcp console=ttyS1,115200n1

After this is setup, type setenv auto-boot? true at the main firmware prompt (not in nvedit). Reboot to read in the new environment variables or set them manually and then type boot.

Creating a new Little-Fe PPC

Follow the instructions on the Diskless Cluster Setup page.

Related pages