Restricting mastership recheck when role NONE.
Avoids also log pollution.
Reason: This avoids one mastership recheck per instance every minute on unreachable AND unavailable device when role of instance is NONE.
Still treats the corner case where role is NONE and device is still available in the store.
Change-Id: I0bd0be5a9ed491a61cc1dc1e988dcf3a53e33993
1 file changed
tree: 8ceb9bb1fffbf3830cad6bac4a131dbc96649d25
- .buckconfig
- .dockerignore
- .gitignore
- .gitreview
- BUCK
- Dockerfile
- Jenkinsfile
- LICENSE.txt
- README.md
- apps/
- buck-tools/
- bucklets/
- cli/
- core/
- docs/
- drivers/
- features/
- incubator/
- lib/
- models/
- modules.defs
- onos.defs
- pipelines/
- 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 our website and our tools