Version 1 (modified by, 7 years ago) (diff)


Adopt-a-GENI Project Status Report

Period: Post GEC 20 Report

I. Major accomplishments

The following highlights our accomplishments during the last reporting period.

A. Milestones achieved

  • Enhance the Adopt-A-GENI (AAG) Controller to install user-defined SDN-controlled paths.
  • Demonstrate the use of the AAG Controller for users to define SDN routes at GEC20.

B. Deliverables made

  • We developed code for installing user-defined paths at OVS nodes via the AAG controller.

II. Description of work performed during last quarter

The following provides a description of the progress made during the last reporting period.

A. Activities and findings

Our activities this last reporting period have been primarily focused on developing code for supporting user-defined SDN-controlled paths in user experiments.

Our initial AAG controller set up the default paths in all OVS nodes in the slice. The default paths are set based on the shortest path between any pair of source and destination nodes. However, the user in SDN networks may prefer a different path for various reasons, such as traffic engineering, special treatment of certain flows, or bypassing a firewall. To support this, we developed the code for the AAG Controller to install user-defined paths in SDN networks.

The user can simply specify the names of the nodes in the path from the source node to the destination node. All the details are then figured out by the AAG controller to install the appropriate rules on the OVS nodes along the path. The AAG controller first checks the legitimacy of the path itself. It needs to make sure that the path contains no loop and is from one end host (non-OVS node) to another end host (non-OVS node). It also checks that any two consecutive nodes specified in the parameter actually comprise an edge in the topology of the experiment.

To create the flow rules that need to be installed, the AAG controller uses the Manifest RSpec to get the specific MAC addresses and corresponding output ports at each OVS node needed to form the user-defined path. Once the flows are formed, they are installed at the OVS nodes using the REST interface of the OpenDaylight controller.

We demonstrated these features of the AAG project at the GEC 20 conference. The topology is shown in the Figure above. It includes five OVS nodes and four VMs. The user can select the path OVS1, OVS2, OVS3, and OVS4 for the traffic from A to B, instead of using the default path via OVS5. The AAG controller is then used to install the rules at these OVS nodes so that the traffic from A to B goes through the user-defined path.

B. Project participants

The following individuals are involved with the project in one way or another:

  • Zongming Fei - Project PI (Kentucky)
  • Jim Griffioen - Project Co-PI (Kentucky)
  • Kobus van der Merwe - Project Co-PI (Utah)
  • Rob Ricci - Project Co-PI (Utah)
  • Hussamuddin Nasir - Technician/Programmer (Kentucky)
  • Jonathon Duerig - Research Associate (Utah)
  • Navjeet Sandhu - M.S. Student (Kentucky)
  • Amrita Jyotiprada - M.S. Student (Kentucky)

C. Publications (individual and organizational)

D. Outreach activities

  • We presented during the demo session at GEC 20 showing the AAG controller that supports user-defined SDN-controlled paths.

E. Collaborations

  • Most of our collaborations have been between the Kentucky team and the Utah team. We continued our discussion on what needs to be done in Jacks now that Jacks is to the stage that it can be integrated into new contexts.

F. Other Contributions

Attachments (1)

Download all attachments as: .zip