Changes between Version 27 and Version 28 of Software


Ignore:
Timestamp:
Apr 22, 2015, 10:07:27 PM (10 years ago)
Author:
ssugrim
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Software

    v27 v28  
    4040There are two alternative methods for the user to interface their experimental applications with the '''OML Collection Clients''' and to define the requested measurement points and parameters. These methods and measurement definitions will be presented in details [wiki:Tutorial/CollectingMeasurements later] in this tutorial.
    4141
     42
    4243[[Image(OML-overview.png)]]
    4344[[BR]]Figure 5. OML component architecture.
    4445
    4546Finally, the ORBIT platform also provides the '''Libmac''' library. '''Libmac''' is a user-space C library that allows applications to inject and capture MAC layer frames, manipulate wireless interface parameters at both aggregate and per-frame levels, and communicate wireless interface parameters over the air on a per-frame level. Users can interface their experimental applications with '''Libmac''' to collect MAC layer measurements from their experiments. This [wiki:Documentation/Libmac other section] of the documentation provides more information on '''Libmac''' and its operations.
     47
     48=== Services ===
     49
     50The Orbit Framework is orchestrated via a collection of interdependent services. These services control the flow of of an experiment. Due to the distributed nature of the Testbed, the services can (and often do) live on physically distant machines. The following graph shows the inter-dependency of orbit services:
     51[[Image(Service Dependence - New Page.png​, 500px)]].
     52
     53As an example of the flow of an experiment, we can consider the process for imaging the nodes. All experiments are some variation of this process. Consider:
     54[[Image(Image Process - New Page.png​, 500px)]].[[BR]]
     55As we can see from this graph, different phases of the experiments occur in different parts of the infrastructure. Some operations (e.g. compute, communicate, overwrite disk) are done on the nodes them selves. Others are initiated from the console (they entry point of user commands). Much of the expirment orchestration happens withing the service infrastructure.