Fix for ONOS-4484 flows left behind after intent reroute
During the installation process, the list of flows to remove and
the list of flows to install were computed into the same variable,
so the list of adds overwrote the list of removes. The fix is to
put them all onto the same list.
Change-Id: I1f0c7f0a7b3c76f50afdb121dbba70010df79fab
(cherry picked from commit fd724409edb458be847b4d6e6f37ba41646a7e90)
1 file changed
tree: 27c5e0c2b43326d7e8210bd5d7c2dfc2f4e97d06
- .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