[ONOS-5069] OpenFlowControllerImpl: always cleanup on deactivate
Even if we don't have devices, the sockets/channels must be closed.
This is particularly harmful when onos is restarted to form a cluster
and the openflow channels are left open. On the next
activation it will try to open ports that were already open and it
fails
Change-Id: I768b9db0b71ffba2805fabf631adcb2039af89e4
1 file changed
tree: 21270e422f449367556197b312f4a0542147a0ab
- .buckconfig
- .gitignore
- .gitreview
- BUCK
- LICENSE.txt
- README.md
- apps/
- buck-tools/
- bucklets/
- cli/
- core/
- docs/
- drivers/
- features/
- incubator/
- lib/
- modules.defs
- onos.defs
- 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