|author||Carmelo Cascone <email@example.com>||Tue Nov 12 10:34:05 2019 -0800|
|committer||Carmelo Cascone <firstname.lastname@example.org>||Fri Nov 15 03:47:40 2019 +0000|
Revamp support for building third-party apps via maven - Publish onos-dependencies (autogenerated from deps.json). With most 3rd-party dependencies listed as <dependencyManagement> to avoid version conflicts, and a minimal set listed as <dependencies> to simplify child poms. Similarly, we provide a number of plugins already configured as <pluginManagement> to support the whole life-cycle of apps (from build, to reporting and release). - Update Maven plugins to work with JDK 11 (checkstyle, pmd, etc.) - Publish onos-build-conf (with common checkstyle and pmd confs) - Removed unused checkstyle code - Fix OSGi version mismatch in deps.json to consistently depend on release 6 (the one supported by Karaf 4) - Update/simplify archetypes to use onos-dependencies as the parent pom Change-Id: Ic09b34e13fb49eb3d96df623b53a3617bbf7b7e4
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 required:
The minimum required Bazel version is 0.27.0
$ 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 $ bazel build onos
To run ONOS locally on the development machine, simply run the following command:
$ bazel run onos-local [-- [clean] [debug]]
Or simpler one, if you have added the ONOS developer environment to your bash profile:
$ ok [clean] [debug]
The above command will create a local installation from the ONOS tarbal (re-building 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, removing any state from previous executions. The
debug option means that the default debug port 5005 will be available for attaching a remote debugger.
To access ONOS UI, use a browser to open:
Or simpler, use the
onos-gui localhost command.
The default username and password is
To attach to the ONOS CLI console, run:
$ onos localhost
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:
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