Skip to content
Snippets Groups Projects
  1. May 15, 2017
  2. Apr 26, 2017
  3. Apr 17, 2017
  4. Apr 14, 2017
  5. Apr 06, 2017
  6. Mar 21, 2017
  7. Mar 20, 2017
  8. Feb 20, 2017
  9. Aug 19, 2016
  10. Jul 15, 2016
  11. Jul 14, 2016
  12. May 31, 2016
  13. May 16, 2016
    • Ryan Izard's avatar
      This is a huge commit. Lots of (good) stuff has been added and updated. First... · b9458ee4
      Ryan Izard authored
      This is a huge commit. Lots of (good) stuff has been added and updated. First and foremost, OpenFlow 1.5 is now supported (yay) via a major update to OpenFlowJ-Loxi. This update necessitated the update of the Static Flow Pusher module and MatchUtils, ActionUtils, and InstructionUtils to support the newly-added features. This prompted me to explore the SFP to see if there was anything that could be improved. First thing that came to mind was adding support to push OpenFlow groups in addition to flows, thus group support has been added to the SFP via JSON, which is the format that should have been used in the first place. Action lists will be updated in the near future to be JSON instead of one massive ',', '=', and '->' delimited string. Thus, the Static Flow Pusher has been renamed the StaticEntryPusher, since it now encompasses groups. While groups were being added to the SFP (ahem...SEP), a number of optimizations were made to the SEP code, greatly reducing its complexity (IMHO). The support for OpenFlow meters can now be added rather trivially in the future, if desired. Last thing to note about the SEP is the work-in-progress addition of a 'schema' API to allow northbound applications to get information about SEP syntax. This is not complete yet, but the skeleton code is in place. Next thing in this pull request is miscellaneous changes throughout the controller, primarily in (de)serializers and REST APIs to support OpenFlow 1.5. Next item of business is the removal of the DebugEventService. This is an artifact of days past and need not clutter the controller anymore. Same goes for the TestModule; now that we have better tutorials and documentation on the wiki, an example isn't necessary. And, last but not least, some old libraries that weren't being used have now been removed.
      b9458ee4
  14. Apr 26, 2016
  15. Dec 01, 2015
  16. Oct 08, 2015
  17. Sep 28, 2015
  18. Jun 18, 2015
  19. Jun 03, 2015
  20. Apr 13, 2015
  21. Apr 03, 2015
  22. Dec 18, 2014
  23. Nov 21, 2014
  24. Nov 10, 2014
  25. Oct 30, 2014
  26. Oct 27, 2014
  27. Oct 10, 2014
    • Ryan Izard's avatar
      Fixed some more unit tests. In the process, discovered some errors in more... · 5b0933bb
      Ryan Izard authored
      Fixed some more unit tests. In the process, discovered some errors in more overridden equals(). Also, discovered I had inadvertently commented out an important few lines the routing module uses to set the ingress port of flows used in the route. Those lines are now ported and use MatchUtils to copy the Match properly.
      5b0933bb
  28. Aug 12, 2014
    • Ryan Izard's avatar
      Static Flow Pusher supports all OF1.3 matches and most OF1.3 actions (with the... · 11aa1c29
      Ryan Izard authored
      Static Flow Pusher supports all OF1.3 matches and most OF1.3 actions (with the exception of masks). LoadBalancer corrected; OFFlowAdd used instead of OFFlowModify and OFPort.ZERO correct to OFPort.ANY. ActionUtils, MatchUtils, and InstructionUtils added to support static flow pusher. Strings defining flow fields *standardized* for Floodlight in the new utils classes. This means the REST API for the SFP will expect a sligthly different syntax than the current REST API (for master and 0.90). We can change the field names easily though in the utils files. These names are also referenced for the keys the SFP uses to store flow match fields and actions, just to be consistent.
      11aa1c29
  29. Aug 10, 2014
  30. Aug 08, 2014
  31. Aug 07, 2014
  32. Aug 05, 2014
  33. Jul 31, 2014
  34. Jul 28, 2014
Loading