| 1 | [[PageOutline]] |
| 2 | |
| 3 | = Adopt-a-GENI Project Status Report = |
| 4 | |
| 5 | Period: Post GEC 22 Report |
| 6 | |
| 7 | == I. Major accomplishments == |
| 8 | |
| 9 | The following highlights our accomplishments during the last reporting period. |
| 10 | |
| 11 | === A. Milestones achieved === |
| 12 | |
| 13 | * Incorporate SDN resource allocation functions with Jacks, including whatever compute resources are available through Jacks. |
| 14 | |
| 15 | * Develop monitoring capability to verify correct connectivity and functioning of user-defined SDN-controlled path. |
| 16 | |
| 17 | === B. Deliverables made === |
| 18 | |
| 19 | * We integrated Jacks with the GENI Desktop so that users can allocate OVS nodes, together with other compute resources through the GENI Desktop. |
| 20 | |
| 21 | * We developed a flow monitoring module in the GENI Desktop that can monitor the user-defined path to verify its correctness. |
| 22 | |
| 23 | == II. Description of work performed during last quarter == |
| 24 | |
| 25 | The following provides a description of the progress made during the last reporting period. |
| 26 | |
| 27 | === A. Activities and findings === |
| 28 | |
| 29 | Our activities this last reporting period have been primarily focused on |
| 30 | integrating Jacks with the GENI Desktop and diveloping a flow monitoring module for |
| 31 | observing the performance of a selected flow in the SDN-controlled path. |
| 32 | |
| 33 | Jacks provided the function to allocate both OVS nodes and other compute |
| 34 | resources. As a joint effort with the GENI Desktop project, we integrated |
| 35 | Jacks with the GENI Desktop. We customized Jacks to create special icons, |
| 36 | including the AAG controller node and the AAG OVS node. Users can drag |
| 37 | the AAG controller into the experiment. It is a custom image we created that |
| 38 | includes OpenDaylight code and runs the OpenDaylight controller once the node is up. |
| 39 | The AAG OVS node contains a custom OVS image we created that includes the AAG |
| 40 | initialization script and related code. It can initialize and configure |
| 41 | the OVS node and point the OVS node to the AAG controller so that the controller |
| 42 | can issue OpenFlow commands to OVS nodes and control the behavior of the switches. |
| 43 | |
| 44 | We designed a Flow Monitoring Module (FMM) in the GENI Desktop to verify that |
| 45 | a flow is correctly installed and to monitor |
| 46 | the traffic that is part of the flow. |
| 47 | The user can pick a flow to monitor and determine at which node to collect the |
| 48 | traffic information about the flow. |
| 49 | |
| 50 | We can get the statistics about the number of packets (bytes) |
| 51 | matching a flow entry from the controller. However, they |
| 52 | are the cumulative counts since the flow entry was installed. |
| 53 | Therefore, it does not show the changes or trends of the flow of interest. |
| 54 | It is hard and time-consuming for an |
| 55 | experimenter to figure out the changes manually. |
| 56 | |
| 57 | The FMM |
| 58 | provides a live monitoring functionality by periodically querying |
| 59 | the controller to get these statistics over a period of time. |
| 60 | Luckily, the controller does not restrict the frequency with |
| 61 | which we can query statistics from it. The FMM transforms the |
| 62 | collected data into a dynamic time series plot that depicts the |
| 63 | flow’s performance over time since the data collection began. |
| 64 | The plot is updated in real time as more data are collected from |
| 65 | the controller. Therefore, it provides live monitoring of the |
| 66 | behavior of the flow. |
| 67 | |
| 68 | [[Image(15mins.png, 600)]] |
| 69 | |
| 70 | The figure shows an example output where |
| 71 | peaks can be easily identified by the experimenter. |
| 72 | The module allows the experimenter to decide the time interval covering the displayed data. |
| 73 | The user can either zoom in or |
| 74 | zoom out the chart for a more detailed or more general visualization of the flow performance. |
| 75 | |
| 76 | === B. Project participants === |
| 77 | |
| 78 | The following individuals are involved with the project in one way or another: |
| 79 | * Zongming Fei - Project PI (Kentucky) |
| 80 | * Jim Griffioen - Project Co-PI (Kentucky) |
| 81 | * Kobus van der Merwe - Project Co-PI (Utah) |
| 82 | * Rob Ricci - Project Co-PI (Utah) |
| 83 | * Hussamuddin Nasir - Technician/Programmer (Kentucky) |
| 84 | * Jonathon Duerig - Research Associate (Utah) |
| 85 | * Sergio Rivera Polanco - Ph.D. Student (Kentucky) |
| 86 | |
| 87 | === C. Publications (individual and organizational) === |
| 88 | |
| 89 | === D. Outreach activities === |
| 90 | |
| 91 | * We demonstrated the flow monitoring function at GEC 22. We |
| 92 | also demonstrated how to use Jacks integrated with the GENI Desktop |
| 93 | to allocate OVS nodes and other compute resources. |
| 94 | |
| 95 | === E. Collaborations === |
| 96 | |
| 97 | * Most of our collaborations have been between the Kentucky team and the |
| 98 | Utah team. |
| 99 | |
| 100 | === F. Other Contributions === |