[ONOS-4530] Allow to specify appId when insert FlowRule through REST
- Augment FlowRuleCodec to encode FlowRule
- Add unit test for encode method of FlowRuleCodec
- Add getFlowByAppId and removeFlowByAppId methods in FlowsWebResource
- Add more unit tests for FlowWebResource
- Add FlowRules.json swagger doc
- Rename Flows.json to FlowEntries.json, correct FlowEntries.json
Change-Id: Ic3ec390c13a349e51ae4208adbc478564b6724ba
7 files changed
tree: 2beed3b28bbe2fecbafbf9d47afb215ecc8bd9f3
- .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