Changes between Version 22 and Version 23 of Tutorials/oMF/tut2


Ignore:
Timestamp:
05/04/15 22:31:25 (3 years ago)
Author:
seskar
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Tutorials/oMF/tut2

    v22 v23  
    1 = Exercise 2: Measuring Performance of a !MobilityFirst Router = 
     1== Exercise 2: Measuring Performance of a !MobilityFirst Router == 
    22 
    33[[TOC(Tutorials/oMF*, depth=2)]] 
    44 
    55 
    6 == !Design/Setup == 
    7  
    8 === Objective === 
     6=== !Design/Setup === 
     7 
     8==== Objective ==== 
    99 
    1010In this exercise, we will try to drive synthetic traffic through the router and measure key performance characteristics such as throughput and forwarding latency. Since !MobilityFirst presents a hop-by-hop block data transport, we can vary the unit size of the data block and observe it's impact on the performance. We will also try to visualize the performance results using OMF's result service by installing an OML-enabled monitor on the routers. 
    1111 
    12 === Pre-requisites === 
     12==== Pre-requisites ==== 
    1313 
    1414 * Experimenters are expected to have basic networking knowledge and familiarity with Linux OS and some of its tools (command line tools, ssh, etc.). 
     
    1616 * Some familiarity with the !MobilityFirst terminology. 
    1717 
    18 === Deploy the Network === 
     18==== Deploy the Network ==== 
    1919 
    2020This tutorial assumes that a 4 nodes topology has been already established in one of the Orbit sandboxes or the grid: 
     
    6666your nodes have been imaged correctly. 
    6767 
    68 === Deploy Network === 
     68==== Deploy Network ==== 
    6969 
    7070Software and experiment control in the ORBIT testbed can be automated greatly using the OMF framework. An OMF control script is written in Ruby and allows the experimenter to specify the set of nodes, their network configuration, to specify software components and arguments, and to control their execution on one or more nodes. We will use an OMF script to bring up 4 ORBIT nodes to host our topology, with the corresponding software components. 
     
    7272We will first introduce the main details of the scripts that will be run and then we will step to the execution process itself. 
    7373 
    74 ==== Software Component Specification ==== 
     74===== Software Component Specification ===== 
    7575 
    7676The following snippet shows the specification of the !MobilityFirst components along with the required arguments. A typical application will have at least a brief description, a path for the associated binary to execute and a list of properties that correspond to the parameters  that will be passed once starting the executable. 
     
    127127 * Most of the client settings are located in a configuration file pre-loaded on the ORBIT image in the folder ''/usr/local/src/mobilityfirst/eval/orbit/conf/''.  
    128128 
    129 ==== Setting up the Software Node Groups ==== 
     129===== Setting up the Software Node Groups ===== 
    130130 
    131131The following snippet shows how the node groups for the routers are setup in the OMF control scripts. Node groups allow experimenters to use single statements to set configuration (e.g. network interfaces) and execute commands across all nodes belonging to the group. 
     
    216216[[CollapsibleEnd]] 
    217217 
    218 ==== Setting up the 'OML enabled Monitor on Routers Application' ==== 
     218===== Setting up the 'OML enabled Monitor on Routers Application' ===== 
    219219 
    220220At this point, the network topology described and initialized in Exercise 1 is supposed to be ready and functional. In order to produce synthetic traffic, we will use mfping to send packets between the end hosts. In order to perform more advanced network measurements, other applications are also available, such as a modified version of the commonly used application ''iperf''. As per the goal of the exercise, we will use an OML-enabled statistics monitor for !MobilityFirst routers in order to collect usage statistics on the nodes.  
     
    266266After running the experiment which should be able to retrieve statistics on a per sample base divided among different groups, based on the analyzed layer (i.e. network layer, link layer, physical layer). 
    267267 
    268 == Execute == 
    269  
    270 ==== Running the Benchmark Application ==== 
     268=== Execute === 
     269 
     270===== Running the Benchmark Application ===== 
    271271 
    272272To generate the traffic that will be reported by the routers, we will use the same ''mfping'' application as in the previous exercise. 
     
    344344 
    345345 
    346 ==== Visualizing the Performance Data ==== 
     346===== Visualizing the Performance Data ===== 
    347347 
    348348'''Method 1:''' the OMF framework supports a result service that allows experimenters to query data stored using the OML measurement framework. The query is performed over the web and requires that you know the ''experiment ID'' associated with your experiment - this is obtained from the output following the execution of the control script. It should look something like this :  
     
    363363 
    364364 
    365 == Finish == 
     365=== Finish === 
    366366 
    367367Once the application has successfully completed its task, follow these steps to complete the experiments: 
     
    370370This will stop all the applications and will conclude the experiment. 
    371371 
    372 === References === 
     372==== References ==== 
    373373 
    374374For more information regarding the !MobilityFirst project, visit the project page: http://mobilityfirst.winlab.rutgers.edu/