Skip to content
Snippets Groups Projects
  1. Jun 26, 2015
  2. Jun 24, 2015
  3. Jun 23, 2015
    • Ryan Izard's avatar
      Clarified some log messages for negotiating OpenFlow versions. More... · 24066c8e
      Ryan Izard authored
      Clarified some log messages for negotiating OpenFlow versions. More importantly, included a patch to ignore all PORT_STATUS messages during the WaitFeaturesReplyState. OVS will periodically send such a message if it's connecting to the controller and being created (e.g. by mininet) at the same time. We will explicitly query the port status/configuration later, so ignoring this message now is fine.
      24066c8e
  4. Jun 22, 2015
    • Ryan Izard's avatar
      First go at implementing OpenFlow version bitmaps. Also, made it a lot easier... · 10476046
      Ryan Izard authored
      First go at implementing OpenFlow version bitmaps. Also, made it a lot easier to change your default OpenFlow versions via floodlightdefault.properties's net.floodlightcontroller.OFSwitchManager.supportedOpenFlowVersions variable. The variable searches any string for 1.0, 1.1, 1.2, 1.3, and 1.4 and saves those versions as possible OpenFlow versions to use during a handshake and used in our controller's version bitmap. We don't presently account for future versions that might be e.g. 1.10 (which 1.1 would match). We need to use regexs to make the string parsing more robust. What I also noticed in working on this commit was that there are no utilies for parsing OpenFlow versions from wire (at least that are exposed by Loxi). TODO Create an OFVersion.ofWireValue(int wireVal) function in Loxi that efficiently tries to locate an OpenFlow version from the wire value. Right now, there are getters for each defined version, but not a utility to go the other way. Also, it might be useful to include an OFVersion.ofString(String laypersonString) that takes e.g. '1.1' and tries to get the OFVersion enum value. Last thing: NEED TO FIX CONNECT, DISCONNECT, and RECONNECT BUG that only occurs when OVS connects to Floodlight after Floodlight has been running first. I think it has to do with how OVS starts up and ***might*** be an OVS issue and not a Floodlight issue. Furthermore, need to allow OVS to send a PORT_STATUS message before we query for the PORT_CONFIG in the handshake. It's okay, we'll just get the port info again when we query for it shortly. This causes us to disconnect OVS even though the handshake is okay.
      10476046
    • Controller's avatar
      fix race conditions in LinkDiscoveryManager · a25bf751
      Controller authored
      a25bf751
    • Controller's avatar
      b77d7519
    • Ryan Izard's avatar
      Merge pull request #563 from xuraylei/master · 51d3df66
      Ryan Izard authored
      fix data races in LoadBalancer module
      51d3df66
  5. Jun 19, 2015
  6. Jun 18, 2015
  7. Jun 12, 2015
  8. Jun 10, 2015
  9. Jun 09, 2015
  10. Jun 08, 2015
  11. Jun 06, 2015
  12. Jun 05, 2015
Loading