Skip to content
Snippets Groups Projects
  1. Dec 16, 2015
  2. Oct 06, 2015
  3. Apr 27, 2015
  4. Mar 09, 2015
  5. Feb 04, 2015
  6. Dec 30, 2014
    • Ryan Izard's avatar
      Just kidding. Went ahead and added a general try-catch in for actions and... · 71a2a16a
      Ryan Izard authored
      Just kidding. Went ahead and added a general try-catch in for actions and matches. In the next minor release, these messages will be returned as errors via the REST API so that partial flows cannot be inserted (based on the correct portions of the JSON-defined flow) and so that the log will not need to be inspected to find the root cause.
      71a2a16a
  7. Dec 22, 2014
  8. Dec 17, 2014
    • Ryan Izard's avatar
      Removed all deprecated FlowReconcileManager stuff from unit tests, which is... · 4ca163ce
      Ryan Izard authored
      Removed all deprecated FlowReconcileManager stuff from unit tests, which is just now showing up as a warning... Also clarified debug message in ActionUtils for actions that do not take the form 'key=value' e.g. 'pop_vlan'. It was phrased as if the action was bad, but it's okay for some that do not take a value.
      4ca163ce
  9. Dec 16, 2014
  10. Dec 15, 2014
  11. Dec 12, 2014
    • Ryan Izard's avatar
      Fixed SFP REST API. Forgot to add new flow's DPID to entry2dpid map, thus flow... · 0eda21fb
      Ryan Izard authored
      Fixed SFP REST API. Forgot to add new flow's DPID to entry2dpid map, thus flow removal never triggered a flow-del message to the switch. Also, added a serializer for OFFlowMod and for OFFlowModMap. The latter is for the double-map of switch-dpid --> map of flow-name --> OFFlowMod object. The former has been separated, since it a JSON serializer for OFFlowMod might come in handy in the future. A present limitation is that the JSON serializer does not use the same syntax as is used to insert a flow-mod via the SFP REST API. This might be confusing for people if they get different output than what they put in. It's a lot less work to implement the serializer as-is though. The next step will be to match the SFP syntax on a per-field basis in the OFFlowModSerializer class.
      0eda21fb
  12. Nov 21, 2014
  13. Nov 05, 2014
  14. Aug 14, 2014
    • Ryan Izard's avatar
      Fixed lots of compile errors in unit tests; mostly involved replacing longs... · 36810baf
      Ryan Izard authored
      Fixed lots of compile errors in unit tests; mostly involved replacing longs with DatapathIds, byte[]s with MacAddresses and Ipv4Addresses, and shorts with OFPorts and VlanVids; some refactoring of flow mod contruction was also done to align with loxi's builders. The static flow puser now supports IP TOS for OF1.0 and for OF1.1+ it supports match/rewrite to either ECN or DSCP bits.
      36810baf
  15. 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
  16. Aug 10, 2014
Loading