Gitiles
Code Review Sign In
gerrit.onosproject.org / onos / 3dcd286f3c1ac15faa687605ae851a78d81cc5a5
commit3dcd286f3c1ac15faa687605ae851a78d81cc5a5[log] [tgz]
authorYuta HIGUCHI <y-higuchi@ak.jp.nec.com>Thu Feb 02 15:22:12 2017 -0800
committerYuta HIGUCHI <y-higuchi@onlab.us>Wed Feb 08 01:19:32 2017 +0000
tree53cf419a348058a547782a9d7577875de727bd83
parent2af9eaaf219ceb606ea0d192a3ce947b3007fead [diff]
Option to use rsync pushing bits

Use rsync to push bits (ONOS tar contents), when
environment variable USE_RSYNC is set to true.
This enables sending only changed .jar, now whole ONOS tar ball.

+ Minor optimization to reuse build machine to remote host ssh session

push bits:
 1) unpackage ONOS tar to tmp stage dir
 2) rsync local stage to remote stage /tmp/$ONOS_BITS
 3) package ONOS tar equivalent at remote node

push bits via proxy:
 1) rsync: build <=> proxy
 2)  scp :           proxy => cell nodes (tar packaged at proxy)
 3) rsync: build <==========> cell nodes (almost no-op)

Known limitation:
- rsync at Step 3 is triggered since
  repackaging same content remotely result in
  tar ball with different hash value.
  (Probably due to directory timestamp/uid difference)
- automatically installing rsync
  only supported for debian/ubuntu

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