Gitiles
Code Review Sign In
gerrit.onosproject.org / onos / e00f6991336b6dc41a27db4ad99951302f56b5a7
commite00f6991336b6dc41a27db4ad99951302f56b5a7[log] [tgz]
authorCharles Chan <rascov@gmail.com>Mon Jan 07 19:59:10 2019 -0800
committerCharles Chan <charles@opennetworking.org>Wed Jan 09 06:52:12 2019 +0000
treef7ccedf628684ca29b5d7e94596cf9b2a1509600
parent68a0a00b4f332cb1cc518dc9c76e587d70cb4492 [diff]
Prevent objective context from being executed multiple times

Consider the following sequence:
1. Flow objective issued
2. Cache timeout since the objective is not processed in time.
   onError()() will be triggered with ObjectiveError.INSTALLATIONTIMEOUT
3. While 2 is still being processed, the objective actually completed.
   onSuccess() will be triggered and therefore the same objective will be dequeued and executed again

The unit test was also wrong.
One objective context should only be executed once no matter the objective succeeded or failed.

In addition, we also fix unit test.

The execution time was originally set to a value that is too close to
the timeout. Therefore, there is chance that it will actually make it
in time. The purpose of this patch is to further delayed the execution
time and therefore get a better chance to create a true timeout.

Change-Id: I2501903bebee6fd9eefb03a71042c4a06ba4c42f
2 files changed
tree: f7ccedf628684ca29b5d7e94596cf9b2a1509600
  1. .bazelrc
  2. .buckconfig
  3. .dockerignore
  4. .github/
  5. .gitignore
  6. .gitreview
  7. BUCK
  8. BUILD
  9. Dockerfile
  10. Jenkinsfile
  11. LICENSE.txt
  12. README.md
  13. WORKSPACE
  14. apps/
  15. buck-tools/
  16. bucklets/
  17. cli/
  18. core/
  19. docs/
  20. drivers/
  21. incubator/
  22. lib/
  23. models/
  24. modules.bzl
  25. modules.defs
  26. onos.defs
  27. pipelines/
  28. pom.xml
  29. protocols/
  30. providers/
  31. tools/
  32. utils/
  33. web/
README.md

ONOS : Open Network Operating System

What is ONOS?

ONOS is the only SDN controller platform that supports the transition from legacy “brown field” networks to SDN “green field” networks. This enables exciting new capabilities, and disruptive deployment and operational cost points for network operators.

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.

Getting started

Dependencies

The following packages are reuqired:

  • git
  • zip
  • curl
  • unzip
  • python2.7
  • Oracle JDK8

To install Oracle JDK8, use following commands (Ubuntu):

$ sudo apt-get install software-properties-common -y && \
  sudo add-apt-repository ppa:webupd8team/java -y && \
  sudo apt-get update && \
  echo "oracle-java8-installer shared/accepted-oracle-license-v1-1 select true" | sudo debconf-set-selections && \
  sudo apt-get install oracle-java8-installer oracle-java8-set-default -y

Build ONOS from source

ONOS is built with Bazel, an open-source build tool developed by Google. ONOS supports Bazel 0.15.2 You can download it from official website or package manager (e.g. apt, brew...)

  1. Clone the code from ONOS gerrit repository
$ git clone https://gerrit.onosproject.org/onos
  1. Add ONOS developer environment to your bash profile, no need to do this step again if you had done this before
$ cd onos
$ cat << EOF >> ~/.bash_profile
export ONOS_ROOT="`pwd`"
source $ONOS_ROOT/tools/dev/bash_profile
EOF
$ . ~/.bash_profile
  1. Build ONOS with Bazel
$ cd $ONOS_ROOT
$ bazel build onos

Start ONOS on local machine

To run ONOS locally on the development machine, simply run the following command:

$ bazel run onos-local [-- [clean] [debug]]

or simpler one:

$ ok [clean] [debug]

The above command will create a local installation from the onos.tar.gz file (re-building it if necessary) and will start the ONOS server in the background. In the foreground, it will display a continuous view of the ONOS (Apache Karaf) log file. Options following the double-dash (–) are passed through to the ONOS Apache Karaf and can be omitted. Here, the clean option forces a clean installation of ONOS and the debug option means that the default debug port 5005 will be available for attaching a remote debugger.

Interacting with ONOS

To access ONOS UI, use browser to open http://localhost:8181/onos/ui or use onos-gui localhost command

The default username and password is onos/rocks

To attach to the ONOS CLI console, run:

$ onos localhost

Unit Tests

To run ONOS unit tests, including code Checkstyle validation, run the following command:

$ bazel query 'tests(//...)' | xargs bazel test

Or better yet, to run code Checkstyle and all unit tests use the following convenience alias:

$ ot

Contributing

ONOS code is hosted and maintained using Gerrit.

Code on GitHub is only a mirror. The ONOS project does NOT accept code through pull requests on GitHub.

To contribute to ONOS, please refer to Sample Gerrit Workflow. It should includes most of the things you'll need to get your contribution started!

More information

For more information, please check out our wiki page or mailing lists:

License

ONOS (Open Network Operating System) is published under Apache License 2.0