PSAS Field Server
Overview
We'd like the ability to take our software and system development tools along with us when we go into the field - literally, as in a giant sage brush field in the middle of Oregon, or figuratively, as when we're in the middle of the dry lake bed of the Black Rock Desert. The PSAS field server provides these tools by mirroring our psas.pdx.edu server which we'll leave safely at PSU in case the field server crashes due to.... field conditions.
Requirements
- Provides a working TWiki mirror of psas.pdx.edu.
- Providers a working CVS mirror of psas.pdx.edu.
- Provides local networking (DHCP, DNS, etc) on a local wired network and to laptops via a WAP.
- Doesn't require other boxes to change configurations (e.g., a development laptop can still contact cvs.psas.pdx.edu).
- Has a Testing/Unstable(?) Debian repository (x86 only).
- Links to the rocket via a Lucent Orinoco card in a PCI-to-PC Card adapter board.
- If we're having a integration test day, it would be nice if the server acted as a gateway to the internet via a local DSL/Cable connection.
Minimums
The existing server has:
- 366MHz Celeron
- 128MB RAM
- 20GB UDMA/33 disk; 3.5GB UDMA/33 on unused disk. Important data sets:
- /var/local/cvs: 63MB
- /var/twiki: 1.3GB
- /var/www: 145MB
- /home: 803MB
- 10/100 ethernet
Thinkpad A30p Field Server
- The compact PCI Actiontec 802.11b card on the A30p uses two U.FL-R-SMT jacks with 1.13mm cable. One jack is called "main" and the other called "aux": we use the "aux" to go to ?LauchTowerComputer. The generic name for adapter cables tends to be the "U.FL" plug.
- We purchased three "UFLNFB12 U.FL to N-Female 12 inch Pigail" from Pasadena Networks LLC (http://www.wlanparts.com/ for $9 each on 6/14/2005.
- A small notch in the access door for the cPCI cards should be enough to thread out the adapter cable ("pigtail").