1. 25 Apr, 2016 6 commits
  2. 23 Apr, 2016 1 commit
    • - Change name: McastEventHandler -> McastHandler
      - Separate HostHandler from SRManager
      - Move storekeys to a dedicated package
      - Replace SRObjevtiveContext and BridgeTableObjectiveContext with DefaultObjectiveContext
      
      Change-Id: Iab25529487004759105e5ba60c1d2a3852ac45e6
      Charles Chan authored
  3. 22 Apr, 2016 7 commits
    • Change-Id: I60215d1715f2220bfa2a23ea94434aca4c1f6e1b
      Brian O'Connor authored
    • Change-Id: Ie2f9a382c6a5dac25403ebe65efb921fabc6e374
      Brian O'Connor authored
    • Stream processes by Lambda queries in collection objects has a known performance bottleneck. For each create and update link data operations, this  kind of queries are frequently used and this causes inefficient topology discovery operation. For to solve that problem i analize thread dump during discovery process and i saw that especially getAllProviders method uses high cpu. than i change the provider search operation with additional map data which holds linkkey and its providers. by this way provider search operation not only gets faster but also uses minimum resource. Before that change, i can discover only 4XX number of switches at one controller, but later number grows to 15XX switches
      
      Change-Id: I65ed71b7f295917c818b2f9227d0fc070aa4a29b
      kircaali authored
    • Change-Id: Idc39a1c81d6a597b0c55885e4e93d5b8ead62650
      Jonathan Hart authored
    • Change-Id: Ifef1c6eafd7cc79ed99be51f7faa26d97aeb2f67
      Jian Li authored
    • Change-Id: Ic229c9bc78e4bfce20842717ae46a0b8acff0b76
      Claudine Chiu authored
    • - Do not handle packet in messages inside ControllerImpl class
      
      Change-Id: Idcb26b277b790125bd6b3ba8f10bb4c60e2a3c58
      Jian Li authored
  4. 21 Apr, 2016 8 commits
  5. 20 Apr, 2016 8 commits
  6. 19 Apr, 2016 10 commits
    •  - Do not include known peers in heartbeat message and instead each node relies on cluster metadata to add/remove nodes from inventory
       - Ignore heartbeats from nodes that are removed
      
      Change-Id: Ia20ce84ad88aa6c723a21af1fe7f6899821181ed
      Madan Jampani authored
    • Change-Id: I8c189584dde590842075bea7e03c4c8ecf8d72c2
      Madan Jampani authored
    • Change-Id: I0b98de095a03a7baedc884f913d42db386dcb163
      Aaron Kruglikov authored
    • Change-Id: I6cc23cd567954daaee59271123a07040853e695b
      Ray Milkey authored
    • Change-Id: I3cd3632e29ff8c5eaf8328a7fdf77ead0b2d9093
      Aaron Kruglikov authored
    • Change-Id: I1aa9c40bf2a925c885a845e6861880c321afd1c7
      Thomas Vachuska authored
    • Change-Id: Ib960a15398a3b9f529f9ad28402d5bac539fb525
      Bharat saraswal authored
    • - Use execute instead of submit so that uncaught Exception will
        be dealt and logged by ExecutorService's handler.
      - Use component's own logger
      
      Change-Id: I761264aea00748980929b5048e111756776dd2f6
      HIGUCHI Yuta authored
    • Remove network-cfg
          Each app has its own way to interpret the config.
          Therefore it doesn't make sense to keep a generic one
          In long term, each app should have a json schema that explain the meaning
      Remove network-cfg-fabric4x4
          It does not provide more info than 2x2
      Remove network-cfg-fabric2x2-default-route and network-cfg-fabric2x2-xconnect
          Keeping features in different configs doesn't help much but make people confused
          Also it's hard to maintain so many samples
      Add network-cfg-fabric-2x2-all
          Full fabric config with readme
          The html documentation is just temporary. We will have a json schema
      Rename/update network-cfg-fabric-2x2-min.json
          Minimum config required by the fabric
      
      Change-Id: I93332d8166c264b9dbb7819b90099c2f19fcf3b5
      Charles Chan authored
    • Change-Id: I4cdd4a4811ec0ab0aba51d7d8085a3eac9b34b2c
      mohamed rahil authored