Changes between Version 10 and Version 11 of Software


Ignore:
Timestamp:
Nov 22, 2007, 11:37:50 PM (16 years ago)
Author:
thierry
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Software

    v10 v11  
    1111[[BR]]Figure 1. Experiment Support Architecture
    1212
    13 
    14 == Hardware Components ==
     13[[BR]]
     14== 1. Hardware Components ==
    1515
    1616The Orbit grid as illustrated in Figure 2 consists of a multiply interconnected, 20-by-20 grid of '''ORBIT Radio Nodes''', some non-grid nodes to control R/F spectrum measurements and interference sources, and front-end, application and back-end servers.  These servers support various ORBIT services.
    … …  
    2424[[BR]]Figure 3. Orbit node.
    2525
    26 == Software components ==
     26[[BR]]
     27== 2. Software components ==
    2728
     29=== 2.1. Experiment Control ===
    2830
    2931The main component of the Experiment Management Service is the '''Node Handler''' that functions as an Experiment Controller.  It multicasts commands to the nodes at the appropriate time and keeps track of their execution.  The '''Node Agent''' software component resides on each node and listens to commands from the '''Node Handler''' and reports information back to the '''Node Handler'''.  The combination of these two components controls the testbed and enables the automated collection of experimental results.  Because the '''Node Handler''' uses a rule-based approach to monitoring and controlling experiments, occasional feedback from experimenters may be required to fine tune its operation.
     32The disk-loading '''Frisbee''' server is designed to quickly load hard disk images onto the nodes using a scalable multicast protocol.  It allows different groups of nodes to run different OS images.
    3033
    31 The disk-loading '''Frisbee''' server is designed to quickly load hard disk images onto the nodes using a scalable multicast protocol.  It allows different groups of nodes to run different OS images.
     34=== 2.2 Measurement & Result Collection ===
    3235
    3336The '''Collection Server''' collects experimental results.  There is one instance of the '''Collection Server''' per experiment.  The Berkeley database is used for scalability, and an SQL database is used for persistent data archiving.  One multicast channel per experiment is used for logical segregation of data and for scalability.