Gitiles
Code Review Sign In
gerrit.onosproject.org / onos / 8d03f1896f5807104a3976b1b7d81ddc28c4974d
commit8d03f1896f5807104a3976b1b7d81ddc28c4974d[log] [tgz]
authorGamze Abaka <gamze.abaka@argela.com.tr>Thu Jul 20 15:09:24 2017 +0000
committerYuta HIGUCHI <y-higuchi@opennetworking.org>Tue Jul 25 23:13:54 2017 +0000
treebafa418cf4a37df4711f2463035040fda3dc6f6c
parent66d3e641efbc60da21d31f483b93c164e2aeb131 [diff]
ONOS controls the packet count field from flow statistics to check flow liveness, but some switches (such as Pica8) do not support packet count field of the flow statistics. Pica8 switch sends "-1" as the packet count. Even though packets match flow rules, when the idle-timeout time is up, ONOS deletes these rules based on the packet count field anyways. Therefore, just checking the packet count field is not enough for this situation. Pica8 sends byte count properly. If ONOS checks both packet and byte count, this problem will be solved. I would like to add byte count check to FlowRuleManager - checkRuleLiveness method.

Change-Id: I4ade01bcd17c4b0a7a59750bd1834b87e78f9972
1 file changed
tree: bafa418cf4a37df4711f2463035040fda3dc6f6c
  1. .buckconfig
  2. .dockerignore
  3. .gitignore
  4. .gitreview
  5. BUCK
  6. Dockerfile
  7. Jenkinsfile
  8. LICENSE.txt
  9. README.md
  10. apps/
  11. buck-tools/
  12. bucklets/
  13. cli/
  14. core/
  15. docs/
  16. drivers/
  17. features/
  18. incubator/
  19. lib/
  20. models/
  21. modules.defs
  22. onos.defs
  23. pom.xml
  24. protocols/
  25. providers/
  26. tools/
  27. utils/
  28. web/
README.md

ONOS : Open Network Operating System

What is ONOS?

ONOS is a new SDN network operating system designed for high availability, performance, scale-out.

Top-Level Features

  • High availability through clustering and distributed state management.
  • Scalability through clustering and sharding of network device control.
  • Performance that is good for a first release, and which has an architecture that will continue to support improvements.
  • Northbound abstractions for a global network view, network graph, and application intents.
  • Pluggable southbound for support of OpenFlow and new or legacy protocols.
  • Graphical user interface to view multi-layer topologies and inspect elements of the topology.
  • REST API for access to Northbound abstractions as well as CLI commands.
  • CLI for debugging.
  • Support for both proactive and reactive flow setup.
  • SDN-IP application to support interworking with traditional IP networks controlled by distributed routing protocols such as BGP.
  • IP-Optical use case demonstration.

Checkout our website and our tools