Changes between Version 7 and Version 8 of AAG/aag_2nd_year_report


Ignore:
Timestamp:
08/07/15 16:12:52 (9 years ago)
Author:
fei@netlab.uky.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • AAG/aag_2nd_year_report

    v7 v8  
    1919 * Develop an approach for plugging a user-specified controller module into the AAG controller for controlling traffic flowing within an SDN-controlled slice.
    2020
    21  * Demonstrate the implemented functions at GEC21, GEC22 and GEC23. Prepare and present the Adopt-A-GENI tutorial at the summer camp 2015 held at University of Connecticut.
     21 * Demonstrate the implemented functions at GEC21, GEC22 and GEC23. Prepare and present the Adopt-A-GENI tutorial at the summer camp 2015 held at the University of Connecticut.
    2222
    2323=== B. Deliverables made ===
     
    5353The original AAG code obtained this information from the manifest, which
    5454was provided as a textual file in XML format. As a part of the GENI Desktop,
    55 the AAG module get the slice information from the parser of the GENI Desktop.
     55the AAG module gets the slice information from the parser of the GENI Desktop.
    5656The parser obtains the slice information from aggregates and provides the
    5757manifest as a JSON object. The AAG code was modified to accommodate this change.
     
    6464processes the information and installs the flows to the switches.
    6565
    66 [[Image(pathselected.png, 450)]]
     66[[Image(pathselected.png, 600)]]
    6767
    6868The above figure shows the AAG module developed. It provides three functions:
     
    8181including the AAG controller node and the AAG OVS node. Users can drag
    8282the AAG controller into the experiment. It is a custom image we created that
    83 includes OpenDaylight code and runs OpenDaylight controller once the node is up. 
     83includes OpenDaylight code and runs the OpenDaylight controller once the node is up. 
    8484The AAG OVS node contains a custom OVS image we created that includes the AAG
    8585initialization script and related code. It can initialize and configure
     
    9595
    9696We designed a Flow Monitoring Module (FMM) in the GENI Desktop to verify that
    97 a flow is correctly installed and monitor
     97a flow is correctly installed and to monitor
    9898the traffic that is part of the flow.
    9999The user can pick a flow to monitor and determine at which node to collect the
     
    102102We can get the statistics about the number of packets (bytes)
    103103matching a flow entry from the controller. However, they
    104 are the cumulative counts since the flow entry is installed.
    105 Therefore, it does not show the changes or trends of the
    106 interested flow. It will be hard and time-consuming for an
     104are the cumulative counts since the flow entry was installed.
     105Therefore, it does not show the changes or trends of the flow of interest.
     106It is hard and time-consuming for an
    107107experimenter to figure out the changes manually.
    108108
     
    115115flow’s performance over time since the data collection began.
    116116The plot is updated in real time as more data are collected from
    117 the controller. Therefore, it provides a live monitoring of the
     117the controller. Therefore, it provides live monitoring of the
    118118behavior of the flow.
    119119
     
    137137Several environments, such as eclipse, can be used for easy syntax completion.
    138138Once the module is written and successfully compiled,
    139 a .jar file representing the bundle will be created.
    140 The final step is to use Web GUI or OSGi console to install the bundle and start
     139a .jar file representing the bundle is created.
     140The final step is to use the Web GUI or the OSGi console to install the bundle and start
    141141it.
    142142
    143 We developed a sample module for port forwarding and demonstrated the approach.
     143We develop a sample module for port forwarding to demonstrate the approach.
    144144The module checks if the destination port is within the (user-defined) range 5000-6000.
    145145If so, flow entries are installed that forward such traffic to port 5050.
     
    153153We demonstrated the AAG path selection function at GEC 21, the monitoring
    154154of flow traffic at GEC 22, and user-specified sub-controller at GEC 23.
    155 We also give a tutorial of the Adopt-A-GENI project at the 2015 summer
     155We also gave a tutorial of the Adopt-A-GENI project at the 2015 summer
    156156camp held at the University of Connecticut.
    157157