|author||Carmelo Cascone <email@example.com>||Wed Jul 04 19:42:37 2018 +0200|
|committer||Andrea Campanella <firstname.lastname@example.org>||Fri Jul 06 08:13:44 2018 +0000|
More improvements and bugfixes in P4Runtime subsystem Most notably, we fix a bug in which some nodes were not able to find pipeconf-specific behaviors for a given device. The problem is not completelly solved but it's mitigated. There's a race condition caused by the fact that the GDP updates the cfg with the merged driver name before advertising the device to the core. Some nodes might receive the cfg update after the device has been advertised. We mitigate the problem by performing the pipeline deploy (slow operation) after the cfg update, giving more time for nodes to catch up. Perhaps we should listen for cfg update events before advertising the device to the core? Also: - NPE when getting P4Runtime client - Detect if a base driver is already merged in pipeconf manager - Longer timeouts in P4Runtime driver and protocol (for slow networks) - Configurable timeout in P4Runtime driver and GDP - NPE when adding/removing device agent listeners in P4Rtunime handshaker - Various exceptions due to race conditions in GDP when disconnecting devices (by serializing disconnect tasks per device) - NPE when cancelling polling tasks in GDP - Refactored PipeconfService to distinguish between driver merge, pipeconf map update, and cfg update (now performed in the GDP) - Fixed PipeconfManagerTest, not testing driver behaviours - Use Guava striped locks when possible (more memory-efficient than maps, and with strict atomicity guarantees w.r.t. to caches). Change-Id: I30f3887541ba0fd44439a86885e9821ac565b64c
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.
The following packages are reuqired:
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
$ git clone https://gerrit.onosproject.org/onos
$ cd onos $ cat << EOF >> ~/.bash_profile export ONOS_ROOT="`pwd`" source $ONOS_ROOT/tools/dev/bash_profile EOF $ . ~/.bash_profile
$ cd $ONOS_ROOT $ onos-buck build onos [--show-output]
ONOS currently uses a modified version of Buck (
onos-buck), which has been packaged with ONOS. Please use this version until our changes have been upstreamed and released as part of an official Buck release.
This will compile all source code assemble the installable onos.tar.gz, which is located in the buck-out directory. Note the --show-output option, which can be omitted, will display the path to this file.
To run ONOS locally on the development machine, simply run the following command:
$ onos-buck run onos-local [-- [clean] [debug]]
or simplier 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.
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
To run ONOS unit tests, including code Checkstyle validation, run the following command:
$ onos-buck test
Or more specific tests:
$ onos-buck test [buck-test-rule]
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!
For more information, please check out our wiki page or mailing lists:
ONOS (Open Network Operating System) is published under Apache License 2.0