This section covers the details involved in getting, installing, and running ONOS. Both single- and multi-instance cases are described.
ONOS and its test scripts are developed and tested on OS X (Mavericks and later) and Ubuntu (14.04 64-bit), with focus on the latter.
We recommend the following if a VM is used for running ONOS:
- Ubuntu Server 14.04 LTS 64-bit
- 2GB or more RAM
- 2 or more processors
In order to build and run ONOS the following are required:
- Java 8 JDK (Oracle Java recommended; OpenJDK is not as thoroughly tested)
- Apache Maven (3.0 and later)
- bash (for packaging & testing)
- Apache Karaf (3.0.2 and later)
Finally, to take full advantage of the ONOS test suite and various developer conveniences, it is also recommended that developers have the following tools available on their machines:
- IDE (IntelliJ, Eclipse, etc.)
- VirtualBox (or other VM hosting software)
Installation - Java, Maven, and Karaf
The ONOS install process relies on the environment variable JAVA_HOME being properly set. In other words, both
mvn --version and
java -version should report the same Java version:
The best way to prevent this version mismatch is to install Maven before Java 8.
Maven and Karaf
The binaries for both Maven and Karaf can be downloaded as tar archives, where installation entails extracting them to the desired location. For example, if your archives were downloaded to ~/Downloads, and you wish to install Maven and Karaf into ~/Applications:
Upgrading to Java 8
For OS X, the latest Oracle Java 8 SDK can be downloaded from Oracle.
For Ubuntu, the following steps will upgrade the installation to Java 8:
You will have to accept the Oracle binary license terms
If not set automatically during the Java 8 installation process, The JAVA_HOME environment variable should be set to the JRE installation location for Java 8. The process for verifying/setting the proper version varies with platform.
On OS X: The current JAVA_HOME may be verified with:
To set the version, either run or add the following to the shell profile:
On Ubuntu: To verify the JAVA_HOME:
If JAVA_HOME is not set or incorrect, either run or add the following to the shell profile:
To get the most from the tools and instructions discussed in the following sections, it is highly recommended that the ONOS_ROOT environment variable is exported in the shell profile (.bash_aliases, .profile, etc.) to refer to the top of the ONOS source tree. For example:
Adding Karaf related commands to PATH
To use karaf or onos command described in following sections, $KARAF_ROOT/bin needs be added to the PATH environment variable.
By default $ONOS_ROOT/tools/dev/bash_profile expects $KARAF_ROOT to be ~/Applications/apache-karaf-$KARAF_VERSION and add them to the PATH.
If you have installed Apache Karaf to a different path, define $KARAF_ROOT pointing to the correct path before including $ONOS_ROOT/tools/dev/bash_profile
ONOS uses Maven for managing the build process. To build the ONOS code-base from the top-most level, and from scratch, simply type the following:
This triggers a full build, complete with unit testing. This may take several minutes, depending on the compute resources of the machine used. When complete, there should be an output similar to the following:
ONOS may be run on the build machine directly, or packaged and launched on remote machines or VMs. This section describes both launching ONOS on the build machine (locally), and packaging and deploying on a remote (target) machine.
Karaf must first be configured to load the ONOS-related modules. Karaf's configuration file
$KARAF_ROOT/etc/org.apache.karaf.features.cfg . Edit the file:
Append the following to featuresRepositories:
Note: Above is an example when using ONOS version 1.1.0. When using snapshot version, etc. replace them with the version you intend to use e.g., 1.1.0-SNAPSHOT, etc.
Append the following to featuresBoot:
The above loads the trivial (single-instance) ONOS core, forwarding, and Web GUI applications.
Running locally on build machine
Blackbird (1.1.0) requires extra config files to run locally. We wrote a script named 'onos-setup-karaf' to copy those config files to the correct location. However, this script is only in master branch for now. We will soon back port it to the 1.1 branch. Before that, you should use the method described in the section 'Running remotely with onos-package and onos-install' to run ONOS.
After running maven as described in Building ONOS and making the above changes,
karaf can be used to start ONOS and attach to its CLI:
At this point, typing
help onos at the prompt should still bring up a list of available commands. Ctrl-D or
logout will exit the CLI.
Launching karaf may bring up the default karaf prompt, without the 'ONOS' ASCII art. This is purely cosmetic, and shouldn't affect functionality.
If the branding is desired, one can move the branding bundle created during the build process to karaf's lib directory:
And relaunch karaf.
Running remotely with
Remote installations are useful when one wishes to run ONOS on a remote machine (or a VM), or run multiple ONOS instances in a cluster. This section demonstrates remote installation on a single remote machine.
The ONOS build process produces a number of OSGi bundles, which are essentially Java jar files. These bundles can be deployed in any OSGi container, but this would require that such container be installed, properly configured, and that the bundles be collected and properly staged. The ONOS utility scripts,
onos-install, simplifies this task down to two steps:
onos-packagepackages the ONOS binaries into a distributable compressed tar. Then,
onos-installpushes the package created by
onos-packageonto the remote VM.
Some preparations are needed for using these scripts:
On the build machine:
- The Apache Karaf binaries (either .zip or .tar.gz format) are available in ~/Downloads
- The ONOS source has been built
The ONOS_FEATURES variable should be set to the list of modules Karaf should launch with ONOS:
On the target VM:
- The Oracle Java 8 JRE and Maven are installed
A user named sdn with pasword-less
sudoprivilege, or, on the build machine, the ONOS_USER environment variable is set to the preferred user for the VM.
To enable sudo without a password, edit the sudoers configuration. To do this, run
sudo visudowithin the VM, and add the following line:
onos-install relies on
ssh to deploy the package to the target machine. To make the process easier, password-less (e.g. key-based) login to the VM is recommended. The onos-push-keys utility can be used to transfer one's public keys to the VM:
This requires that the keys have been generated prior to using the utility. As shown above, it will ask for the password twice.
to produce a self-contained tar archive:
As seen above, the file has the naming convention "onos-1.1.0.<username>.tar.gz", and is created under the /tmp directory.
Deploy the binary by pointing
onos-installto the remote target to run ONOS on (192.168.56.20 in this example):If ONOS has been previously installed on a remote machine,
onos-install -f [target]will force a reinstall.
Once ONOS is running, the
onos utility can be used to attach to the remote instance's CLI:
Alternatively, pointing a browser at http://<onos-ip>:8181/onos/ui will display the ONOS Web GUI.
Handling multiple remote targets
For deploying ONOS on multiple remote machines (i.e., as a cluster), the behavior of the ONOS utilities can be configured by employing test cells. Test cells are discussed under Test Environment Setup in the Developer's Guide.
If Things go Wrong
Maven and Karaf
Both Maven and Karaf rely on network access for some of their functionality. One of the first points to check if a build fails is to check for connectivity, and rebuild the project once it is restored.
In Karaf, connectivity issues may manifest as bundles not loading (e.g. not being able to use any ONOS-related commands, or
help onos returning nothing). It may also take some time for ONOS to fully boot up, in which case some commands may not be available for the first minute or so.
Running in a VM
Make sure that the primary user in the VM (sdn) has superuser privilege, or is part of sudoers.
Also be sure that there is a .m2 directory in the user's home directory. Running Maven at least once in the VM will generate the directory.