Page tree

Have questions? Stuck? Please check our FAQ for some common questions and answers.

This wiki documents the current development version of ONOS (master). Refer to the Wiki Archives for documentation for all previous versions of ONOS.

Skip to end of metadata
Go to start of metadata

This Quick Start describes a simple "local" workflow where you build and run ONOS on a single development machine.

First of all, you should install software dependencies, starting with Java. You can download, extract, and install Oracle Java 8 on most platforms.  

On Ubuntu/Debian, you can do the following:

Java dependency
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

Some other dependencies are required as well. Use your package manager of choice to install these:

Other dependencies
unzip # CentOS installations only
python # Version 2.7 is required

ONOS is built with Buck, an open-source build tool created by Facebook and inspired by Google. It is also in use by number of well-known projects, including all Facebook’s mobile apps, Gerrit, etc. By relying on explicit dependencies between targets and SHA hashes of files (rather than on timestamps), Buck avoids unnecessary work by recognizing whether or not a target artifact requires a rebuild. This also helps to increase reproducibility of builds.

ONOS currently uses a modified version of 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. 

RedHat installations

Building with buck makes use of "shasum" for signatures. CentOS systems do not provide this command; but rather those for the direct algorithms. Just symlink the default algorithm (sha1sum) to the expected command:

sudo ln -s /usr/bin/sha1sum /usr/bin/shasum

To get the source code and build ONOS, all you need to do it run the following commands from Unix-like terminal (e.g. Linux, MacOS):

git clone
cd onos
export ONOS_ROOT=$(pwd)
tools/build/onos-buck build onos --show-output

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:

tools/build/onos-buck run onos-local -- 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 attach to the ONOS CLI console, run:

tools/test/bin/onos localhost

Once connected, you can run various ONOS CLI and Apache Karaf commands. For example, to start up OpenFlow and reactive forwarding, you could do the following:

onos> activate org.onosproject.openflow
onos> activate org.onosproject.fwd

To open your default browser on the ONOS GUI page, simply type:

tools/test/bin/onos-gui localhost

or alternatively visit http://localhost:8181/onos/ui 

To start up a Mininet network controlled by an ONOS instance that is already running on your development machine, you can use a command like:

sudo mn --controller remote,ip=<ONOS IP address> --topo torus,3,3

Note that you should replace <ONOS IP address> with the IP address of your development machine where ONOS is running.

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

tools/build/onos-buck test

If you want to import the project into IntelliJ, you can generate the hierarchical module structure via the following command:

tools/build/onos-buck project

Then simply open the onos directory from IntelliJ IDEA.

The above should be enough to get you started. If you like more detailed instructions for importing the ONOS project into an IDE or contributing your changes back to the ONOS project, please consult the Development Environment Setup section.

  • No labels