[ONOS-4428] Fix the L3 dataflow bug when in same ternant but different
subnet with different routers, in the odler version of ONOS, in the same
ternant, different network with differnent routers, dataflows can be
send to each other successfully.
Change-Id: I6e50289023711eb0f6005efee0efd6f7ab9ec3ee
5 files changed
tree: d1fbd4b76ee9ff10d8c1fa78c7b55f011f3594e4
- .buckconfig
- .gitignore
- .gitreview
- BUCK
- LICENSE.txt
- README.md
- apps/
- buck-tools/
- bucklets/
- cli/
- core/
- docs/
- drivers/
- features/
- incubator/
- lib/
- pom.xml
- protocols/
- providers/
- tools/
- utils/
- 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 out our website and our tools