Update and Remove some network-cfg.json sample

Remove network-cfg
    Each app has its own way to interpret the config.
    Therefore it doesn't make sense to keep a generic one
    In long term, each app should have a json schema that explain the meaning
Remove network-cfg-fabric4x4
    It does not provide more info than 2x2
Remove network-cfg-fabric2x2-default-route and network-cfg-fabric2x2-xconnect
    Keeping features in different configs doesn't help much but make people confused
    Also it's hard to maintain so many samples
Add network-cfg-fabric-2x2-all
    Full fabric config with readme
    The html documentation is just temporary. We will have a json schema
Rename/update network-cfg-fabric-2x2-min.json
    Minimum config required by the fabric

Change-Id: I93332d8166c264b9dbb7819b90099c2f19fcf3b5
8 files changed
tree: b6a4f233b9262800fac25fdcb80dfeee41e9560b
  1. .buckconfig
  2. .gitignore
  3. .gitreview
  4. BUCK
  5. LICENSE.txt
  6. README.md
  7. apps/
  8. buck-tools/
  9. bucklets/
  10. cli/
  11. core/
  12. docs/
  13. drivers/
  14. features/
  15. incubator/
  16. lib/
  17. pom.xml
  18. protocols/
  19. providers/
  20. tools/
  21. utils/
  22. 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