Mascot Submission Architecture

This document reflects the current state of the Mascot Submission Architecture available in DEV as of 2005-06-03.

Software

We are currently running Mascot 2.0.4 in a 'cluster' configuration. This configuration has one head node which runs a web-frontend via Apache, and delegates the work out to 5 compute nodes. All nodes are running SUSE 9.2 64-bit with the 2.6.8-24.11-smp kernel. Mascot uses it's own 32-bit build of perl 5.8.6

Hardware

Each node is an HP DL145 armed with the following:

• 2 x 2.4GHz Opteron
• 800MHz Front-Side Bus
• 4GB ECC RAM
• 1 x 160GB 7200rpm
• 1 x 80GB 7200rpm

Master Node

The current master Mascot node is node 2. Nothing but Mascot and Apache is currently running on it. It's storage is configured as such:

• The 80GB disk and 80GB of the larger disk are in a software RAID stripe sitting on /opt/mascot/data for storing the mimefiles. This provides 160GB of combined storage dedicated to mimefiles.

• every 4 hours, "mascotjanitor" runs which compresses and relocates mimefiles older than 30 hours that have not been accessed in the last 2 hours to the raid on node 1 for long-term storage.

This configuration will be changing shortly. We will soon be using 4 SATA 7200rpm disks on a FC-AL array for mime storage.

Compute Nodes

The compute node simply has a 60GB partition on a 7200rpm SATA disk for /opt/mascot. This directory is only used for temporary storage while samples are being run.